[
https://issues.apache.org/jira/browse/YARN-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030971#comment-14030971
]
Vinod Kumar Vavilapalli commented on YARN-2052:
-----------------------------------------------
I forgot to add one more note that I myself ran into in an offline discussion
with [~jianhe]. The new field can be RMIdentifier which today is backed by the
start-timestamp. But two RMs (active/standby) started at the same time can
potentially clash w.r.t time-stamps. We can chose this to be
timestamp+host-name etc or simply a UUID..
> ContainerId creation after work preserving restart is broken
> ------------------------------------------------------------
>
> Key: YARN-2052
> URL: https://issues.apache.org/jira/browse/YARN-2052
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Tsuyoshi OZAWA
> Assignee: Tsuyoshi OZAWA
>
> Container ids are made unique by using the app identifier and appending a
> monotonically increasing sequence number to it. Since container creation is a
> high churn activity the RM does not store the sequence number per app. So
> after restart it does not know what the new sequence number should be for new
> allocations.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
