[ https://issues.apache.org/jira/browse/YARN-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sangjin Lee updated YARN-5638: ------------------------------ Hadoop Flags: Reviewed > 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: YARN-5355 > > 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.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org