Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Information Provided
-
Affects Version/s: CDH 5.4.8
-
Fix Version/s: None
-
Component/s: MapReduce
-
Labels:None
Description
CM neglects to configure the client configuration with the follow parameter when the yarn.log-aggregation-enable is enabled. the NodeManager configuration correctly gets the following set, but the client configuration is missing it.
<property>
<name>yarn.nodemanager.remote-app-log-dir</name>
<value>/var/mapred/nm/logs</value>
</property>
With the above value missing from the client configuration, we get the following behavior:
$ yarn logs -appOwner imhotep -applicationId application_1452195702108_96718 | head 16/02/24 20:44:47 INFO client.ConfiguredRMFailoverProxyProvider: Failing over to rm715 /tmp/logs/hcoyote/logs/application_1452195702108_96718does not exist. Log aggregation has not completed or is not enabled.
With the value set to what the server-side is, we get valid log output.
$ yarn logs -appOwner hcoyote -applicationId application_1452195702108_96718 | head
16/02/24 20:45:36 INFO client.ConfiguredRMFailoverProxyProvider: Failing over to rm715
Container: container_e68_1452195702108_96718_01_000628 on nm1.example.net_8041
===============================================================================================
LogType:stderr
Log Upload Time:Wed Feb 24 13:10:47 -0600 2016
LogLength:773
Log Contents:
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/opt/cloudera/parcels/CDH-5.4.9-1.cdh5.4.9.p0.19/jars/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]