[ https://issues.apache.org/jira/browse/FLINK-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437113#comment-15437113 ]
ASF GitHub Bot commented on FLINK-4488: --------------------------------------- Github user StephanEwen commented on the issue: https://github.com/apache/flink/pull/2419 That makes sense, +1 to merge this for 1.1.2 and 1.2 Wondering if we can guard this via a test, so that the FLIP-6 refactoring does not re-introduce the bug. > Prevent cluster shutdown after job execution for non-detached jobs > ------------------------------------------------------------------ > > Key: FLINK-4488 > URL: https://issues.apache.org/jira/browse/FLINK-4488 > Project: Flink > Issue Type: Bug > Components: YARN Client > Affects Versions: 1.2.0, 1.1.1 > Reporter: Maximilian Michels > Assignee: Maximilian Michels > Priority: Minor > Fix For: 1.2.0, 1.1.2 > > > In per-job mode, the Yarn cluster currently shuts down after the first > interactively executed job. Users may want to execute multiple jobs in one > Jar. I would suggest to use this mechanism only for jobs which run detached. > For interactive jobs, shutdown of the cluster is additionally handled by the > CLI which should be sufficient to ensure cluster shutdown. Cluster shutdown > could only become a problem in case of a network partition to the cluster or > outage of the CLI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)