You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2017/07/31 12:35:00 UTC

[jira] [Assigned] (FLINK-6213) When number of failed containers exceeds maximum failed containers and application is stopped, the AM container will be released 10 minutes later

     [ https://issues.apache.org/jira/browse/FLINK-6213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann reassigned FLINK-6213:
------------------------------------

    Assignee: Yelei Feng

> When number of failed containers exceeds maximum failed containers and application is stopped, the AM container will be released 10 minutes later 
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-6213
>                 URL: https://issues.apache.org/jira/browse/FLINK-6213
>             Project: Flink
>          Issue Type: Bug
>          Components: YARN
>    Affects Versions: 1.2.0, 1.3.0
>            Reporter: Yelei Feng
>            Assignee: Yelei Feng
>             Fix For: 1.4.0
>
>
> When number of failed containers exceeds maximum failed containers and application is stopped, the AM container will be released 10 minutes later. I checked yarn log and found out after invoking {{unregisterApplicationMaster}}, the AM container is not released. After 10 minutes, the release is triggered by RM ping check timeout.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)