[
https://issues.apache.org/jira/browse/YARN-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030966#comment-14030966
]
Vinod Kumar Vavilapalli commented on YARN-2052:
-----------------------------------------------
bq. e.g. container_XXX_1000 after epoch 1.
This scheme won't work with a single reserved digit for epochs and a large
number of restarts over time.
Here's my summary of what I think we should do:
The current ContainerID format is
{code}
ContainerID {
applicationAttemptID
containerIDInt
}
{code}
Let's just add a new field
{code}
+ rmIdentifier
{code}
Old code (state-store, history-server etc) will not read it and that's fine.
The only problem is users who are interpreting container_ID strings themselves.
That is NOT supported. We should modify ConverterUtils to support the
new-field, and that should do.
Thoughts?
> 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)
