Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

The property 'dfs.namenode.secondary.http-address' is associated with the component 'SECONDARY_NAMENODE' which isn't mapped to any host group

Highlighted

The property 'dfs.namenode.secondary.http-address' is associated with the component 'SECONDARY_NAMENODE' which isn't mapped to any host group

New Contributor

Hello all,

I am getting this warning and cluster formation is waiting at ' Logical Request: Provision Cluster ' state.

WARN [pool-20-thread-1] BlueprintConfigurationProcessor:1546 - The property 'dfs.namenode.secondary.http-address' is associated with the component 'SECONDARY_NAMENODE' which isn't mapped to any host group. This may affect configuration topology resolution.

Although the error looks self-explanatory, I am surprised to see it since I don't have any 'SECONDARY_NAMENODE' as component in my blueprint and also the configuration in blueprint doesn't show any property 'dfs.namenode.secondary.http-address'

Can anyone explain what is happening and how I can correct it?


            {                 "hdfs-site": {                     "dfs.client.failover.proxy.provider.testcluster": "org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider",                      "dfs.datanode.data.dir": "/tmp/datanode",                      "dfs.datanode.failed.volumes.tolerated": "0",                      "dfs.ha.automatic-failover.enabled": "true",                      "dfs.ha.fencing.methods": "shell(/bin/true)",                      "dfs.ha.namenodes.testcluster": "nn1,nn2",                      "dfs.namenode.checkpoint.dir": "/tmp/hdfs/namesecondary",                      "dfs.namenode.http-address.testcluster.nn1": "%HOSTGROUP::ec2-xx-xx-xx-xx.us-west-2.compute.amazonaws.com%:50070",                      "dfs.namenode.http-address.testcluster.nn2": "%HOSTGROUP::ec2-yy-yy-yy-yy.us-west-2.compute.amazonaws.com%:50070",                      "dfs.namenode.https-address.testcluster.nn1": "%HOSTGROUP::ec2-xx-xx-xx-xx.us-west-2.compute.amazonaws.com%:50470",                      "dfs.namenode.https-address.testcluster.nn2": "%HOSTGROUP::ec2-yy-yy-yy-yy.us-west-2.compute.amazonaws.com%:50470",                      "dfs.namenode.name.dir": "/tmp/namenode",                      "dfs.namenode.rpc-address.testcluster.nn1": "%HOSTGROUP::ec2-xx-xx-xx-xx.us-west-2.compute.amazonaws.com%:8020",                      "dfs.namenode.rpc-address.testcluster.nn2": "%HOSTGROUP::ec2-yy-yy-yy-yy.us-west-2.compute.amazonaws.com%:8020",                      "dfs.namenode.shared.edits.dir": "qjournal://%HOSTGROUP::master%:8485/testcluster",                      "dfs.nameservices": "abhardwaj-test-enterprise1",                      "dfs.replication": "1"         }