[ 
https://issues.apache.org/jira/browse/FLINK-21029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konstantin Knauf updated FLINK-21029:
-------------------------------------
    Fix Version/s:     (was: 1.12.4)
                       (was: 1.14.0)
                       (was: 1.11.4)

> 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
>
> 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)

Reply via email to