[YARN-3629] NodeID is always printed as "null" in node manager initialization log.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Target Version/s: 2.8.0
• Hadoop Flags: Reviewed
• Assignee: nijel
• Reporter: nijel
• Created: 12/May/15 06:23
• Updated: 30/Aug/16 01:22
• Resolved: 12/May/15 16:56

Description

In Node manager log during startup the following logs is printed

2015-05-12 11:20:02,347 INFO org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl: Initialized nodemanager for null : physical-memory=4096 virtual-memory=8602 virtual-cores=8

This line is printed from NodeStatusUpdaterImpl.serviceInit.
But the nodeid assignment is happening only in NodeStatusUpdaterImpl.serviceStart

  protected void serviceStart() throws Exception {

    // NodeManager is the last service to start, so NodeId is available.
    this.nodeId = this.context.getNodeId();

Assigning the node id in serviceinit is not feasible since it is generated by ContainerManagerImpl.serviceStart.

The log can be moved to service start to give right information to user.