Hi, I've just realized there is a difference in configuration of alternatives functionality between Datanodes and the NameNode. NameNode: alternatives --display hadoop-conf hadoop-conf - status is auto. link currently points to /etc/hadoop/conf.cloudera.hdfs /etc/hadoop/conf.cloudera.hdfs - priority 90 /opt/cloudera/parcels/CDH-5.7.0-1.cdh5.7.0.p0.45/etc/hadoop/conf.empty - priority 10 Current `best' version is /etc/hadoop/conf.cloudera.hdfs. DataNode: alternatives --display hadoop-conf hadoop-conf - status is auto. link currently points to /etc/hadoop/conf.cloudera.yarn /opt/cloudera/parcels/CDH-5.7.0-1.cdh5.7.0.p0.45/etc/hadoop/conf.empty - priority 10 /etc/hadoop/conf.cloudera.yarn - priority 92 /etc/hadoop/conf.cloudera.hdfs - priority 90 Current `best' version is /etc/hadoop/conf.cloudera.yarn On NameNode I see directory /etc/hadoop/conf.cloudera.yarn but it seems to be unused. For example, even though yarn.resourcemanager.address is set correctly in /etc/hadoop/conf.cloudera.yarn/yarn-site.xml I receive: INFO client.RMProxy: Connecting to ResourceManager at /0.0.0.0:8032 INFO ipc.Client: Retrying connect to server: 0.0.0.0/0.0.0.0:8032. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) INFO ipc.Client: Retrying connect to server: 0.0.0.0/0.0.0.0:8032. Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1000 MILLISECONDS) when I try 'yarn application -list' from NameNode, and correct results when I try from DataNodes. Is it expected behaviour? Has anybody hit this problem before?
... View more
