[
https://issues.apache.org/jira/browse/FLINK-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15439346#comment-15439346
]
ASF GitHub Bot commented on FLINK-4488:
---------------------------------------
Github user mxm commented on the issue:
https://github.com/apache/flink/pull/2419
Our currents tests make it difficult to test such behavior. Added a check
to the `YarnTestBase`. Basically, I'm skipping the cluster shutdown to check if
the JobManager is still alive and hasn't been shutdown through other means.
> 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)
