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/01/23 11:26:27 UTC

[jira] [Updated] (YARN-6114) RM will report unacquired containers to AM if they are KILLED before being ACQUIRED

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

Varun Saxena updated YARN-6114:
-------------------------------
    Summary: RM will report unacquired containers to AM if they are KILLED before being ACQUIRED  (was: RM will report unacquired containers to AM if they are KILLED before being ACQUIRE)

> RM will report unacquired containers to AM if they are KILLED before being ACQUIRED
> -----------------------------------------------------------------------------------
>
>                 Key: YARN-6114
>                 URL: https://issues.apache.org/jira/browse/YARN-6114
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>            Reporter: Varun Saxena
>            Assignee: Varun Saxena
>
> RM will report an unacquired container to AM if it is KILLED (due to node becoming unhealthy or reconnecting, etc.).
> This is because we report all containers whether they have been acquired or not to RMAppAttempt and they are further added to the list of just finished containers.
> These containers are then reported on next AM heartbeat even though they have not been acquired by the AM, which is unnecessary.
> In case of Spark AM, this leads to the AM re-requesting these containers again from RM.



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

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