I had updated the supervisor log of slave node in below: http://stackoverflow.com/questions/30022525/unable-to-use-remote-slave-node-in-apache-storm-cluster
As mentioned, the supervisor of slave node didn't register itself to the zookeeper of the master node, instead, it register itself at its own, 127.0.0.1:2181. aAlthough I had remove the zookeeper and also the storm.yaml for the slave node, the same problem arise as if there is a default storm.yaml running when there is no storm.yaml in storm/conf.
