YARN-3629. NodeID is always printed as "null" in node manager

initialization log. Contributed by nijel.

(cherry picked from commit 5c2f05cd9b)
This commit is contained in:
Devaraj K 2015-05-12 22:20:25 +05:30
parent fb5b0ebb45
commit 5fceebd696
2 changed files with 5 additions and 1 deletions

View File

@ -349,6 +349,9 @@ Release 2.8.0 - UNRELEASED
YARN-3602. TestResourceLocalizationService.testPublicResourceInitializesLocalDir
fails Intermittently due to IOException from cleanup. (zhihai xu via xgong)
YARN-3629. NodeID is always printed as "null" in node manager initialization log.
(nijel via devaraj)
Release 2.7.1 - UNRELEASED
INCOMPATIBLE CHANGES

View File

@ -199,7 +199,7 @@ public class NodeStatusUpdaterImpl extends AbstractService implements
+ durationToTrackStoppedContainers);
}
super.serviceInit(conf);
LOG.info("Initialized nodemanager for " + nodeId + ":" +
LOG.info("Initialized nodemanager with :" +
" physical-memory=" + memoryMb + " virtual-memory=" + virtualMemoryMb +
" virtual-cores=" + virtualCores);
@ -213,6 +213,7 @@ public class NodeStatusUpdaterImpl extends AbstractService implements
// NodeManager is the last service to start, so NodeId is available.
this.nodeId = this.context.getNodeId();
LOG.info("Node ID assigned is : " + this.nodeId);
this.httpPort = this.context.getHttpPort();
this.nodeManagerVersionId = YarnVersionInfo.getVersion();
try {