[
https://issues.apache.org/jira/browse/YARN-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Li Lu updated YARN-5638:
------------------------
Description: 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. (was: As
discussed in YARN-3359, we need to further identify timeline collectors and
their creation order for better service discovery and resource isolation. This
JIRA proposes to use <app, attempt, timestamp> to accurately identify each
timeline collector. )
> 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
>
> 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
