hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Suresh (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (YARN-5447) Consider including allocationRequestId in NMContainerStatus to allow recovery in case of RM failover
Date Fri, 29 Sep 2017 20:42:00 GMT

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

Arun Suresh resolved YARN-5447.
-------------------------------
    Resolution: Won't Fix

Today, this is a problem even when a user does not specify an allocate required Id.
Since the AMRMClient sends all outstanding requests to the RM after a failover, it should
not be that big of an issue.

> 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