You only have 4 worker slots all of which are taken by the 2 topologies, increase number of worker slots or increase number of supervisors by adding more hosts.
What version of python are you running on worker hosts? On Dec 15, 2014, at 2:31 PM, Sa Li <[email protected]> wrote: > Hi, all > > We've setup the production STORM cluster, 1 nimbus + 3 supervisor node. I > test the cluster by running the storm-starter topologies. I found only > exclamation and wordcount topologies are assigned workers, see the attached > screenshots. > > 1. Why ReachTopology and RollingTopWords are not assigned workers? > > 2. I run WordCount topology on localcluster, I am having such error: > 6110 [Thread-14-split] ERROR backtype.storm.util - Async loop died! > java.lang.RuntimeException: java.lang.RuntimeException: > java.lang.RuntimeException: pid:13896, name:split exitCode:0, errorString: > ..... > Brandon Bradley says "WordCountTopology confirmed working in > v0.9.2-incubating. Since v0.9.3 has non-backwards-compatible multilang > changes, WordCountTopology needs to be updated as such." in > https://issues.apache.org/jira/browse/STORM-531. I thought I can get around > it by submit to storm cluster, but I got error as > > > Mon, 15 Dec 2014 11:05:01 -08:00 complicated-laugh.master 6703 > java.lang.RuntimeException: backtype.storm.multilang.NoOutputException: Pipe > to subprocess seems to be broken! No output read. Serializer Exception: at > backtype.storm.utils.ShellProcess.readShellMsg(ShellProcess.java:101) at > backtype.storm.task.ShellBolt$BoltReaderRunnable.run(ShellBolt.java:318) at > java.lang.Thread.run(Thread.java:745) > > > WordCountTopology will be updated? or We need to do something? > > > 3. Are there any existing script to make performance test for storm cluster? > > > thanks > > Alec > > > <productionTopologies.jpg> > > <Exclamation.jpg> > > > <WordCount.jpg> > > <wordCountError.jpg> > > > > > > > > > -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
