You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Rohith Sharma K S (Jira)" <ji...@apache.org> on 2019/08/30 05:46:00 UTC
[jira] [Resolved] (YARN-3115) [Collector wireup] Work-preserving
restarting of per-node timeline collector
[ https://issues.apache.org/jira/browse/YARN-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rohith Sharma K S resolved YARN-3115.
-------------------------------------
Resolution: Won't Fix
As part of ATSv2 JIRA clean up as discussed in weekly call, closing the JIRA as Won't Fix. Feel free to reopen if still same design approach exists.
> [Collector wireup] Work-preserving restarting of per-node timeline collector
> ----------------------------------------------------------------------------
>
> Key: YARN-3115
> URL: https://issues.apache.org/jira/browse/YARN-3115
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Zhijie Shen
> Assignee: Junping Du
> Priority: Major
> Labels: YARN-5355
>
> YARN-3030 makes the per-node aggregator work as the aux service of a NM. It contains the states of the per-app aggregators corresponding to the running AM containers on this NM. While NM is restarted in work-preserving mode, this information of per-node aggregator needs to be carried on over restarting too.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org