[
https://issues.apache.org/jira/browse/FLINK-23563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17390556#comment-17390556
]
Yun Tang commented on FLINK-23563:
----------------------------------
[~AlexYinHan] I have assigned this ticket to you, and you could prepare a PR fo
this.
> Sometimes ‘Stop’ cannot stop the job
> ------------------------------------
>
> Key: FLINK-23563
> URL: https://issues.apache.org/jira/browse/FLINK-23563
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Checkpointing
> Reporter: Han Yin
> Assignee: Han Yin
> Priority: Minor
>
> Sometimes the 'Stop' command do not stop the job after the savepoint is
> finished.
> This is because currently we set _syncSavepointId_ to null whenever we
> abort/complete a checkpoint, even if the aborted/completed checkpoint is not
> the latest one.
> In some rare cases, it is possible that during a 'Stop' process, we trigger a
> savepoint, and then the _syncSavepointId_ is set to null due to the abortion
> of a previous checkpoint. As a result, the subtasks are not stopped after
> completing the savepoint.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
