AnsweredAssumed Answered

NODE_ALARM_INCORRECT_TOPOLOGY_ALARM; Cluster: CLUSTER; Node: nodeB; Message: Node with CLDB is in incorrect topology /mapr-rack1/nodeB, while CLDB volume (mapr.cldb.internal) is in topology /data

Question asked by achyuthp on Mar 4, 2015
Hi,
Im currently deploying a 3 node cluster with M7 license ,have set the rack topology file name in cldb.conf
"net.topology.table.file.name=/opt/mapr/hadoop/hadoop-0.20.2/rack_topology.txt"  ,  but incorrect topology alarm is been raised ,

would like to know what I am missing here, and how to avoid this alarm during install
(have chnaged teh hostenames to nodeA, nodeB,nodeC-- nodeA and nodeB are CLDB enabled )

the cldb log indicates that Fileserver registration is based on the rack topology , but /data is getting assigned to default rack 

cldb.log:2015-03-04 10:51:38,287 INFO CLDB [main]: CLDB Properties from configuration file: cldb.web.port=7221cldb.zookeeper.servers=192.168.x.xx:5181,192.168.x.xxx:5181,192.168.x.xx:5181cldb.numthreads=10cldb.web.https.port=7443hadoop.version=2.4.1net.topology.table.file.name=/opt/mapr/hadoop/hadoop-0.20.2/rack_topology.txtcldb.port=7222cldb.min.fileservers=1cldb.detect.dup.hostid.enabled=falsenum.volmirror.threads=1cldb.jmxremote.port=7220
cldb.log:2015-03-04 10:51:59,423 INFO CLDBServer [RPC-10]: FSRegister: Registered FileServer: 192.168.0.151- at topology /mapr-rack2/nodeA
cldb.log:2015-03-04 10:52:04,477 INFO CLDBServer [RPC-9]: FSRegister: Registered FileServer: 192.168.0.16- at topology /mapr-rack1/nodeB
cldb.log:2015-03-04 10:52:05,988 INFO CLDBServer [RPC-7]: FSRegister: Registered FileServer: 192.168.0.15- at topology /mapr-rack3/nodeC

 Topology [Thread-3]: Registered fileserver 192.168.x.xxx- is at topology /data/default-rack/nodeA

thanks
achyuth

Outcomes