Database Reference
In-Depth Information
These logs record the messages and failures during service startup, if there are any. They also record the ID
number of the process spawned when a service starts. Following is a sample
namenode.trace.log
file. It shows the
content after a name node service startup.
HadoopServiceTraceSource Information: 0 : Tracing successfully initialized
DateTime=2013-12-10T02:46:57.6055000Z
Timestamp=3981555628
HadoopServiceTraceSource Information: 0 : Loading service xml: c:\apps\dist\hadoop-1.2.0.1.3.1.0-06\
bin\namenode.xml
DateTime=2013-12-10T02:46:57.6055000Z
Timestamp=3981598144
HadoopServiceTraceSource Information: 0 : Successfully parsed service xml for service namenode
DateTime=2013-12-10T02:46:57.6211250Z
Timestamp=3981610465
HadoopServiceTraceSource Information: 0 : Command line: c:\apps\dist\java\bin\java -server
-Xmx4096m -Dhadoop.log.dir=c:\apps\dist\hadoop-1.2.0.1.3.1.0-06\logs -Dhadoop.log.file=hadoop-
namenode-RD00155D67172B.log -Dhadoop.home.dir=c:\apps\dist\hadoop-1.2.0.1.3.1.0-06 -Dhadoop.root.
logger=INFO,console,DRFA,ETW,FilterLog -Djava.library.path=;c:\apps\dist\hadoop-1.2.0.1.3.1.0-06\
lib\native\Windows_NT-amd64-64;c:\apps\dist\hadoop-1.2.0.1.3.1.0-06\lib\native -Dhadoop.
policy.file=hadoop-policy.xml -Dcom.sun.management.jmxremote -Detwlogger.component=namenode
-Dwhitelist.filename=core-whitelist.res -classpath c:\apps\dist\hadoop-1.2.0.1.3.1.0-06\
conf;c:\apps\dist\java\lib\tools.jar;c:\apps\dist\hadoop-1.2.0.1.3.1.0-06;c:\apps\dist\
hadoop-1.2.0.1.3.1.0-06\hadoop-ant-1.2.0.1.3.1.0-06.jar;c:\apps\dist\hadoop-1.2.0.1.3.1.0-06\hadoop-
client-1.2.0.1.3.1.0-06.jar;c:\apps\dist\hadoop-1.2.0.1.3.1.0-06\hadoop-core-1.2.0.1.3.1.0-06.
jar;c:\apps\dist\hadoop-1.2.0.1.3.1.0-06\hadoop-core.jar;c:\apps\dist\hadoop-1.2.0.1.3.1.0-06\
hadoop-examples-1.2.0.1.3.1.0-06.jar;c:\apps\dist\hadoop-1.2.0.1.3.1.0-06\hadoop-examples.
jar;c:\apps\dist\hadoop-1.2.0.1.3.1.0-06\hadoop-minicluster-1.2.0.1.3.1.0-06.jar;c:\apps\dist\
hadoop-1.2.0.1.3.1.0-06\hadoop-test-1.2.0.1.3.1.0-06.jar;c:\apps\dist\hadoop-1.2.0.1.3.1.0-06\
hadoop-test.jar;c:\apps\dist\hadoop-1.2.0.1.3.1.0-06\hadoop-tools-1.2.0.1.3.1.0-06.jar;c:\apps\dist\
hadoop-1.2.0.1.3.1.0-06\hadoop-tools.jar;c:\apps\dist\hadoop-1.2.0.1.3.1.0-06\lib\*;c:\apps\dist\
hadoop-1.2.0.1.3.1.0-06\lib\jsp-2.1\*;c:\apps\dist\log4jetwappender\microsoft-log4j-etwappender-
1.0.jar; org.apache.hadoop.hdfs.server.namenode.NameNode
DateTime=2013-12-10T02:46:57.6211250Z
Timestamp=3981611043
HadoopServiceTraceSource Information: 0 : ServiceHost#OnStart
DateTime=2013-12-10T02:46:57.6211250Z
Timestamp=3981662789
HadoopServiceTraceSource Information: 0 : Child process started, PID: 3720
DateTime=2013-12-10T02:46:57.6211250Z
Timestamp=3981707399
These logs record very low-level service startup messages. Most likely, the information in them is external to the
Hadoop system. For example, in a network failure scenario, you might see an entry similar to the following in your
namenode.trace.log
file:
Session Terminated, Killing shell....
It is very rare that these log files get populated with anything else apart from the service startup messages. For
example, they might be populated in the case of a network heartbeat failure between the name node and the data
nodes. Still, they can be helpful at times in figuring out why your DataNode, NameNode, or Secondary NameNode
service isn't starting up or is sporadically shutting down.
