Mailing-List: contact issues-help@flink.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.incubator.apache.org
Date: Sat, 11 Oct 2014 17:06:33 +0000 (UTC)
From: "Robert Metzger (JIRA)" <jira@apache.org>
To: issues@flink.incubator.apache.org
Message-ID: <JIRA.12747515.1413042268000.246565.1413047193628@Atlassian.JIRA>
In-Reply-To: <JIRA.12747515.1413042268000@Atlassian.JIRA>
References: <JIRA.12747515.1413042268000@Atlassian.JIRA>
 <JIRA.12747515.1413042268514@arcas>
Subject: [jira] [Commented] (FLINK-1153) Yarn container does not terminate
 if Flink's yarn client is terminated before the application master is
 completely started
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FLINK-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168259#comment-14168259 ] 

Robert Metzger commented on FLINK-1153:
---------------------------------------

The old RPC service seems to have a method "Server.getNumOpenConnections()". The AM could destroy itself and all the containers after 30 seconds without a connection from the Client?
Do you think this is a good solution? (I assume that we can handle this more elegantly with the Akka rewrite)

> Yarn container does not terminate if Flink's yarn client is terminated before the application master is completely started
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-1153
>                 URL: https://issues.apache.org/jira/browse/FLINK-1153
>             Project: Flink
>          Issue Type: Bug
>          Components: YARN Client
>            Reporter: Till Rohrmann
>
> The yarn application master container does not terminate if the yarn client is terminated after the container request is issued but before the application master is completely started.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)