eemario commented on code in PR #27818: URL: https://github.com/apache/flink/pull/27818#discussion_r3049427286
########## docs/content/docs/deployment/ha/overview.md: ########## @@ -29,7 +29,16 @@ under the License. # High Availability JobManager High Availability (HA) hardens a Flink cluster against JobManager failures. -This feature ensures that a Flink cluster will always continue executing your submitted jobs. +This feature ensures that a Flink cluster will always re-execute your submitted applications that were running at the time of a failure. Review Comment: My understanding is that you're asking about the checkpoints of jobs within a re-executed application. When an application is re-executed in HA mode, what happens to its running jobs is determined by the application's own logic in the main method: - Resumption: If the logic in the main method re-submits the job, it will automatically resume from its latest checkpoint. - Abandonment: If the application's logic does not re-submit the job, it is considered abandoned. The job will be moved to a FAILED state, and its resources, including all checkpoints, are properly cleaned up. I've added some explanation to the documentation to make the behavior clear. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
