[
https://issues.apache.org/jira/browse/FLINK-21029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-21029:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> 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.20.1#820001)
