Never mind, I found this page which is sufficient for now. Would like to know how storm is scaled in aws though.
On Thu, Jun 18, 2015 at 5:29 PM, Dillian Murphey <[email protected]> wrote: > I discovered my problem. Since I cloned a machine from which to add more > nodes to the cluster, I didn't clean out the /mnt/storm directory and my > new worker was using the same ID string as the previous worker. > > Deleted everything in the storm dir and restarted my worker and now it's > back. > > So indirectly, creating an image of my server kind of bit me in the rear. > Must take an image with a cleaned out directory. > > On Thu, Jun 18, 2015 at 5:09 PM, Dillian Murphey <[email protected]> > wrote: > >> I had a standalone storm server running nimbus, supervisor, and the ui. >> The nimbus server was set to localhost since it was running locally. >> >> I spun up a new server and configured just the supervisor process, >> pointing to the nimbus server above. >> >> I am not seeing two supervisors. They have connectivity. I also only see >> 1 entry in zookeeper under supervisors. >> >> Am I not allowed to run supervisor on the nimbus server in a cluster >> scenerio? >> >> thanks for any ideas. >> > >
