Tsuyoshi OZAWA commented on YARN-2052:

The only problem is users who are interpreting container_ID strings themselves. 
That is NOT supported. 

Yeah, I think it is difficult to avoid the problem. But the interpreting logic 
itself doesn't change drastically with our approach because we doesn't change 
the order of attributes. IMHO, it's acceptable approach.

BTW, I found that ConverterUtils is marked as {{@Pivate}}. Should we make the 
class {{@Public}}?

public class ConverterUtils {

> 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

Reply via email to