hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5447) Consider including allocationRequestId in NMContainerStatus to allow recovery in case of RM failover
Date Tue, 24 Oct 2017 23:09:00 GMT

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

Jian He commented on YARN-5447:
-------------------------------

[~asuresh], in yarn service we are rely on allocateRequestId as a mapping from allocateId
-> component.
However, this failed in recovery, because the allocateRequestId is not recovered and break
the client logic, see YARN-7371

We need to re-consider this ?

> Consider including allocationRequestId in NMContainerStatus to allow recovery in case
of RM failover
> ----------------------------------------------------------------------------------------------------
>
>                 Key: YARN-5447
>                 URL: https://issues.apache.org/jira/browse/YARN-5447
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: applications, resourcemanager
>            Reporter: Subru Krishnan
>            Assignee: Subru Krishnan
>
> We have added a mapping of the allocated container to the original request through YARN-4887/YARN-4888.
There is a corner case in which the mapping will be lost, i.e. if RM fails over before notifying
the AM about newly allocated container(s). This JIRA tracks the changes required to include
the allocationRequestId in NMContainerStatus to allow recovery in case of RM failover.



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

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