hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Saxena (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-6114) RM will report an unacquired containers to AM if they are KILLED before being ACQUIRED
Date Mon, 23 Jan 2017 11:26:27 GMT

     [ 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 an unacquired containers to AM if they are KILLED before being
ACQUIRED  (was: RM will report an unacquired container to AM if it is KILLED before being
ACQUIRED)

> RM will report an 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


Mime
View raw message