[
https://issues.apache.org/jira/browse/FLINK-26683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513358#comment-17513358
]
Piotr Nowojski commented on FLINK-26683:
----------------------------------------
I think in both cases we can restart/restore only to commit side effects.
Basically just initialize operators, but never process any records (or in case
of legacy {{SourceFunction}} never call {{#run()}}).
Regardless, even when doing just that, we can encounter the same problem, for
example a disk error when committing some transactions. So we might end up in
the infinite restarting loop (subject to restart strategy?), that user will
have to terminate manually.
> Terminate the job anyway if savepoint finished when stop-with-savepoint
> -----------------------------------------------------------------------
>
> 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)
