You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Varun Saxena (JIRA)" <ji...@apache.org> on 2017/02/06 08:54:42 UTC

[jira] [Commented] (YARN-6147) Blacklisting nodes not happening for AM containers

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

Varun Saxena commented on YARN-6147:
------------------------------------

This happens when NM is down but RM hasn't yet found out that it is down i.e. NM expiry hasn't happened?

> Blacklisting nodes not happening for AM containers
> --------------------------------------------------
>
>                 Key: YARN-6147
>                 URL: https://issues.apache.org/jira/browse/YARN-6147
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>            Reporter: Naganarasimha G R
>            Assignee: Naganarasimha G R
>
> Black Listing of nodes are not happening in the following scenarios
> 1. RMAppattempt is in ALLOCATED and LAUNCH_FAILED event comes when NM is down.
> 2. RMAppattempt is in LAUNCHED and EXPIRE event comes when NM is down.
> In both these cases AppAttempt goes to *FINAL_SAVING* and eventually to *FINAL* state before *CONTAINER_FINISHED* event is triggered by {{RMContainerImpl}} and in the {{FINAL}} state {{CONTAINER_FINISHED}} event is ignored.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org