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 2017/07/31 09:36:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16107040#comment-16107040 ] 

ASF GitHub Bot commented on FLINK-6213:
---------------------------------------

Github user tillrohrmann commented on a diff in the pull request:

    https://github.com/apache/flink/pull/3640#discussion_r130309444
  
    --- Diff: flink-yarn/src/main/java/org/apache/flink/yarn/YarnFlinkResourceManager.java ---
    @@ -300,6 +301,8 @@ protected void shutdownApplication(ApplicationStatus finalStatus, String optiona
     		} catch (Throwable t) {
     			LOG.error("Could not cleanly shut down the Node Manager Client", t);
     		}
    +
    +		self().tell(decorateMessage(PoisonPill.getInstance()), self());
    --- End diff --
    
    I would directly call `getContext().system().stop(self())`, because that way we will stop immediately processing any further messages.


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