[
https://issues.apache.org/jira/browse/FLINK-21029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17268045#comment-17268045
]
Theo Diefenthal commented on FLINK-21029:
-----------------------------------------
Ah you are right again. I ghought for a moment that savepoint path is part of
the job config but that's checkpoint path of course. Yeah as the savepoint path
is part of the stop command, the job really shouldn't stop if the path is
invalid.
> Failure of shutdown lead to restart of (connected) pipeline
> -----------------------------------------------------------
>
> Key: FLINK-21029
> URL: https://issues.apache.org/jira/browse/FLINK-21029
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.11.2
> Reporter: Theo Diefenthal
> Priority: Major
> Fix For: 1.13.0, 1.11.4, 1.12.2
>
>
> This bug happened in combination with
> https://issues.apache.org/jira/browse/FLINK-21028 .
> When I wanted to stop a job via CLI "flink stop..." with disjoint job graph
> (independent pipelines in the graph), one task wan't able to stop properly
> (Reported in mentioned bug). This lead to restarting the job. I think, this
> is a wrong behavior in general and a separated bug:
> If any crash occurs on (trying) to stop a job, Flink shouldn't try to restart
> but continue stopping the job.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
