[
https://issues.apache.org/jira/browse/FLINK-26683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514708#comment-17514708
]
Liu commented on FLINK-26683:
-----------------------------
I see that [FLINK-26783|https://issues.apache.org/jira/browse/FLINK-26783]
notifies the users to decide what to do in this case. This is helpful under
special circumstances but it may put more operational pressure on users. This
may be not the perfect solution. For example, as previous discussion, flink can
restart automatically to only commit side effects for some times before
notifying users.
Besides, we have another case in which all the commits are done but some tasks
fail for some reason before exiting. I am thinking that whether we can
recognize this case and terminate the job instead of restarting.
> Commit side effects if stop-with-savepoint failed while finishing
> -----------------------------------------------------------------
>
> Key: FLINK-26683
> URL: https://issues.apache.org/jira/browse/FLINK-26683
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Checkpointing, Runtime / Coordination
> Affects Versions: 1.15.0, 1.14.4
> Reporter: Liu
> Priority: Major
> Fix For: 1.16.0
>
>
> When we stop with savepoint, the savepoint finishes. But some tasks failover
> for some reason and restart to running. In the end, some tasks are finished
> and some tasks are running. In this case, I think that we should terminate
> all the tasks anyway instead of restarting since the savepoint is finished
> and the job stops consuming data. What do you think?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
