Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-3629

NodeID is always printed as "null" in node manager initialization log.

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.8.0, 3.0.0-alpha1
    • Component/s: None
    • Labels:
      None
    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      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.

        Attachments

          Activity

            People

            • Assignee:
              nijel nijel
              Reporter:
              nijel nijel
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: