[ https://issues.apache.org/jira/browse/YARN-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14034474#comment-14034474 ]
Tsuyoshi OZAWA commented on YARN-2052: -------------------------------------- Vinod, OK. I'll create new JIRA to address it. {quote} Another question is how are we going to show the containerId string? specifically the toString() method. If we just say "original containerId string+UUID", it'll be inconvenient for debugging as the UUID has no meaning. {quote} >From developer's point of view, you're right. One idea is showing RM_ID >instead of UUID. Validating RM_ID and confirming not to include underscore at >startup time. One concern of this approach is that we'll break backward >compatibility of yarn-site.xml. If we can accept it, it's better approach. > 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 > Attachments: YARN-2052.1.patch, YARN-2052.2.patch, YARN-2052.3.patch > > > 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)