{ 8 } Troubleshooting - GemaAlbiach/Bicing-RealTime-Occupancy-estimation GitHub Wiki

To run that topology in cluster mode, you have to provide an argument. Otherwise it runs it in local mode. Take a look at the code to see what I mean. So try this:

/opt/apache-storm-0.9.2-incubating/bin/storm jar bicingtopology-0.0.1-SNAPSHOT.jar storm.ebd.bicingTopology demo

(https://groups.google.com/forum/#!topic/storm-user/KhmLg9_FcqI)

#Not all supervisors appear in Storm UI

Symptoms:

• Some supervisor processes are missing from the Storm UI

• List of supervisors in Storm UI changes on refreshes

Solutions:

• Make sure the supervisor local dirs are independent (e.g., not sharing a local dir over NFS)

• Try deleting the local dirs for the supervisors and restarting the daemons. Supervisors create a unique id for themselves and store it locally. When that id is copied to other nodes, Storm gets confused.

see also http://storm.incubator.apache.org/documentation/Troubleshooting.html

Solved the problem. I read though the error information

Node 192.168.1.128:50010 is expected to serve this storage

and found that when I copy the set up from one server to another, I also copied the local data dir for HDFS (dfs.data.dir). And this created conflicts. Once I clean the all the data inside the local dfs.data.dir, the DataNode started without any issue.

(http://stackoverflow.com/questions/17975144/only-one-datanode-can-run-in-a-multinode-hadoop-setup)