hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nijel (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-3629) NodeID is always printed as "null" in node manager initialization log.
Date Tue, 12 May 2015 06:24:00 GMT
nijel created YARN-3629:

             Summary: NodeID is always printed as "null" in node manager initialization log.
                 Key: YARN-3629
                 URL: https://issues.apache.org/jira/browse/YARN-3629
             Project: Hadoop YARN
          Issue Type: Bug
            Reporter: nijel
            Assignee: nijel

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. 

This message was sent by Atlassian JIRA

View raw message