hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2182) Update ContainerId#toString() to avoid conflicts before and after RM restart
Date Sat, 23 Aug 2014 07:29:12 GMT

    [ https://issues.apache.org/jira/browse/YARN-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107916#comment-14107916
] 

Jian He commented on YARN-2182:
-------------------------------

- We may just hard code these in toString()? as these anyways will be changed later.
{code}
private final int ID_BIT_MASK = 0x003fffff;
  private final int EPOCH_BIT_SHIFT = 22;
{code}
- Use appAttemptIdFormat format to show Epoch?  as I think minimum 2 digits is more appropriate
to show epoch number. And rename appAttemptIdFormat to attemptIdAndEpochFormat
- If epoch is 0, let’s not append anything to keep consistent with current behavior.

> Update ContainerId#toString() to avoid conflicts before and after RM restart
> ----------------------------------------------------------------------------
>
>                 Key: YARN-2182
>                 URL: https://issues.apache.org/jira/browse/YARN-2182
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Tsuyoshi OZAWA
>            Assignee: Tsuyoshi OZAWA
>         Attachments: YARN-2182.1.patch
>
>
> ContainerId#toString() doesn't include any information about current cluster id. This
leads conflict between container ids. We can avoid the conflicts without breaking backward
compatibility by using epoch introduced on YARN-2052.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message