XComp opened a new pull request, #24382: URL: https://github.com/apache/flink/pull/24382
## What is the purpose of the change See [comment in FLINK-34518](https://issues.apache.org/jira/browse/FLINK-34518?focusedCommentId=17820679&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17820679) for more details. ## Brief change log * Overwrites the `ExecutionGraph`'s state when suspending the job in the `Restarting` phase: The actually state might be `CANCELLED` which can result in a HA data cleanup because it's a globally-terminal state which we don't want when restarting the job. The cancellation of the `ExecutionGraph` is more like an implementation detail of the `Restarting` state and shouldn't be exposed. ## Verifying this change * Added unit test to cover this scenario ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): no - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: no - The serializers: no - The runtime per-record code paths (performance sensitive): no - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: yes - The S3 file system connector: no ## Documentation - Does this pull request introduce a new feature? no - If yes, how is the feature documented? not applicable -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
