Do not add hosts with duplicate short host names to Cloudera Manager

0 votes
asked Aug 30, 2017 in Hadoop by admin (4,410 points)
SummaryHosts with duplicate short hostnames can cause issues and should not be added to Cloudera Manager
Applies To
  • Cluster contains hosts from multiple subdomains
  • Cluster short host names are not unique
  • Error messages in the SERVICEMONITOR logs:
    • 2016-12-06 20:10:55,110 WARN com.cloudera.cmon.kaiser.IpAndHostnameKeyedStore: (29 skipped) Massaged hostname collision:
      2016-12-06 20:10:55,197 WARN com.cloudera.cmon.firehose.polling.CdhTask: (14 skipped) Exception in doWork for task: yarn_YARN_SERVICE_STATE_TASK
              at com.cloudera.cmon.firehose.polling.yarn.YarnServiceState.updateResourceManagers(
              at com.cloudera.cmon.firehose.polling.yarn.YarnServiceStateFetcher.doWork(
              at com.cloudera.cmon.firehose.polling.yarn.YarnServiceStateFetcher.doWork(
              at com.cloudera.cmon.firehose.polling.CdhTask$InstrumentedWork.doWork(
              at com.cloudera.cmf.cdhclient.CdhExecutor$
              at java.util.concurrent.ThreadPoolExecutor.runWorker(
              at java.util.concurrent.ThreadPoolExecutor$


Cloudera Manager is designed to be resilient to minor name resolution misconfigurations, where the same host may be a member of multiple subdomains but all names resolve to the same physical host.  This means that all short (i.e. unqualified) host names must be unique when added to Cloudera Manager.

Thus, the following hosts should not be added to the same Cloudera Manager managed cluster: (IP: (IP:


Do not add hosts to Cloudera Manager with duplicate short host names.

Please log in or register to answer this question.