You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/08/25 13:43:21 UTC
[jira] [Commented] (FLINK-4488) Prevent cluster shutdown after job
execution for non-detached jobs
[ https://issues.apache.org/jira/browse/FLINK-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15436876#comment-15436876 ]
ASF GitHub Bot commented on FLINK-4488:
---------------------------------------
GitHub user mxm opened a pull request:
https://github.com/apache/flink/pull/2419
[FLINK-4488] only automatically shutdown clusters for detached jobs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mxm/flink FLINK-4488
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2419.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2419
----
commit 8623083bc0147d89ce433da677ff2d4ed6ecd768
Author: Maximilian Michels <mx...@apache.org>
Date: 2016-08-25T13:41:12Z
[FLINK-4488] only automatically shutdown clusters for detached jobs
----
> 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)