You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Maximilian Michels (JIRA)" <ji...@apache.org> on 2016/08/29 16:21:21 UTC

[jira] [Closed] (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:all-tabpanel ]

Maximilian Michels closed FLINK-4488.
-------------------------------------
    Resolution: Fixed

master: 87114cd2aaf78de2114d1ea4ab7bd2b57494d716
release-1.1: 28da995494ad21223f6911f27eb46187294f311a

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