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 "Varun Saxena (JIRA)" <ji...@apache.org> on 2017/10/21 06:06:55 UTC
[jira] [Updated] (YARN-5638) Introduce a collector timestamp to
uniquely identify collectors creation order in collector discovery
[ https://issues.apache.org/jira/browse/YARN-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Varun Saxena updated YARN-5638:
-------------------------------
Fix Version/s: 2.9.0
> Introduce a collector timestamp to uniquely identify collectors creation order in collector discovery
> -----------------------------------------------------------------------------------------------------
>
> Key: YARN-5638
> URL: https://issues.apache.org/jira/browse/YARN-5638
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Li Lu
> Assignee: Li Lu
> Fix For: 2.9.0, YARN-5355, 3.0.0-beta1
>
> Attachments: YARN-5638-YARN-5355.v4.patch, YARN-5638-YARN-5355.v5.patch, YARN-5638-trunk.v1.patch, YARN-5638-trunk.v2.patch, YARN-5638-trunk.v3.patch
>
>
> As discussed in YARN-3359, we need to further identify timeline collectors' creation order to rebuild collector discovery data in the RM. This JIRA proposes to use <rm_timestamp, logical_version_number> to order collectors for each application in the RM. This timestamp can then be used when a standby RM becomes active and rebuild collector discovery data.
--
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