[
https://issues.apache.org/jira/browse/YARN-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16056648#comment-16056648
]
Arun Suresh commented on YARN-6127:
-----------------------------------
Based on our offline discussions, I think I am OK with pushing the refactoring
of the state to a separate JIRA - Since we have yet to fully hash out the
implication of allowing Interceptors to access another Interceptor's stored
state, since the recoveredDataMap will contain all interceptors' state for a
particular application. We can fix that when we get to it.
One minor nit though:
* Instead of forcing the interceptor to call {{getRecoveredDataMap()}} from
inside the {{recover()}} method, the map should probably be passed into the
recover() method as an argument.
> Add support for work preserving NM restart when AMRMProxy is enabled
> --------------------------------------------------------------------
>
> Key: YARN-6127
> URL: https://issues.apache.org/jira/browse/YARN-6127
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: amrmproxy, nodemanager
> Reporter: Subru Krishnan
> Assignee: Botong Huang
> Attachments: YARN-6127.v1.patch, YARN-6127.v2.patch
>
>
> YARN-1336 added the ability to restart NM without loosing any running
> containers. In a Federated YARN environment, there's additional state in the
> {{AMRMProxy}} to allow for spanning across multiple sub-clusters, so we need
> to enhance {{AMRMProxy}} to support work-preserving restart.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
