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 "Junping Du (JIRA)" <ji...@apache.org> on 2015/04/06 20:45:13 UTC
[jira] [Resolved] (YARN-3449) Recover appTokenKeepAliveMap upon
nodemanager restart
[ https://issues.apache.org/jira/browse/YARN-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Junping Du resolved YARN-3449.
------------------------------
Resolution: Invalid
Assignee: (was: Junping Du)
> Recover appTokenKeepAliveMap upon nodemanager restart
> -----------------------------------------------------
>
> Key: YARN-3449
> URL: https://issues.apache.org/jira/browse/YARN-3449
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager
> Affects Versions: 2.6.0, 2.7.0
> Reporter: Junping Du
>
> appTokenKeepAliveMap in NodeStatusUpdaterImpl is used to keep application alive after application is finished but NM still need app token to do log aggregation (when enable security and log aggregation).
> The applications are only inserted into this map when receiving getApplicationsToCleanup() from RM heartbeat response. And RM only send this info one time in RMNodeImpl.updateNodeHeartbeatResponseForCleanup(). NM restart work preserving should put appTokenKeepAliveMap into NMStateStore and get recovered after restart. Without doing this, RM could terminate application earlier, so log aggregation could be failed if security is enabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)