[YARN-5338] Fix ContainerId fromString to correctly parse remotely allocated container Ids

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Fix Version/s: 2.9.0, 3.0.0
• Component/s: yarn
• Labels: oct16-easy
• Assignee: Arun Suresh
• Reporter: Arun Suresh
• Created: 08/Jul/16 16:22
• Updated: 06/Nov/17 22:28
• Resolved: 27/Oct/16 21:41

Description

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