Tsuyoshi OZAWA commented on YARN-2052:

Updated patch to address the comments by Bikas, Jian, and Vinod. We agreed that 
this JIRA doesn't include the changes of {{toString()}} format and container id 
length from int to long. Therefore, the latest patch includes following changes:

* Added getEpoch()/setEpoch() APIs to ContainerId.
* Changed setContainerId() to ignore upper 8bits for the number of RM restarts.
* Updated ContainerIdProto to include epoch(int32 value) for the future changes.

[~jianhe], [~bikassaha], [~vinodkv] could you take a look?

> 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, 
> YARN-2052.4.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

Reply via email to