You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Arun Suresh (JIRA)" <ji...@apache.org> on 2016/07/08 16:25:10 UTC

[jira] [Updated] (YARN-5338) Fix ContainerId fromString to correctly parse remotely allocated container Ids

     [ https://issues.apache.org/jira/browse/YARN-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arun Suresh updated YARN-5338:
------------------------------
    Attachment: YARN-5338.001.patch

Attaching trivial patch.

> Fix ContainerId fromString to correctly parse remotely allocated container Ids
> ------------------------------------------------------------------------------
>
>                 Key: YARN-5338
>                 URL: https://issues.apache.org/jira/browse/YARN-5338
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Arun Suresh
>            Assignee: Arun Suresh
>             Fix For: 2.9.0
>
>         Attachments: YARN-5338.001.patch
>
>
> ContainerIds generated by the Local Scheduler on the NM monotonically decrements from 0 to distinguish them from incrementing containerIds generated by the RM.
> Since only the last 40 bits of the ContainerId are actually used, This patch ensures that -1 containerId maps to 2 ^40 -1 and the toString and fromString correctly parses these containerId.
> One implication of this is patch is that the containerId space is divided into 2. The top half will be used by remotely allocated containers and the bottom half by those allocated by the RM



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org