Jian He commented on YARN-2052:

Seems more problem with the randomId approach if user wants to the kill the 
container,  user has to be aware of the random ID..

Had an offline discussion with Vinod.  Maybe it's still better to persist  some 
sequence number to indicate the number of RM restarts when RM starts up. Today 
containerId#id is int (32 bits), we reserve some bits in the front for the 
number of RM restarts. e.g. 32bits divided as 8bits for the number of RM 
restarts and 24 bits for the number of containers. Each time RM restarts, we 
increase the RM sequence number. Also, We should have a followup jira to change 
the containerId/appId from integer to long and deprecate the old one.  
[~ozawa],  do you agree?

> 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

Reply via email to