In 2.x the local mode cluster API is much more robust giving you lots of control over building exactly the cluster you want.
https://github.com/apache/storm/blob/master/storm-server/src/main/java/org/apache/storm/LocalCluster.java We do a lot of that for testing, but you can use it for other things too. In previous versions of storm all of that same functionality is available but it is all exposed through clojure. https://github.com/apache/storm/blob/1.x-branch/storm-core/src/clj/org/apache/storm/testing.clj Sadly in 1.x there is no easy way to set configs for a local mode cluster with just java. You have to use clojure to do it. - Bobby On Sat, Mar 31, 2018 at 12:33 PM Roshan Naik <[email protected]> wrote: > Have you tried increasing the > > supervisor.slots.ports ? > > I suspect you are getting limited by it. > > - Roshan > > > Sent from Yahoo Mail for iPhone > <https://overview.mail.yahoo.com/?.src=iOS> > > > On Saturday, March 31, 2018, 10:11 AM, Boaz Rosenan <[email protected]> > wrote: > > Hi everyone, > > I developed a prototype of a platform that uses Apache Storm behinds the > scenes. My platform's "developer mode", which is currently the only one > supported, uses Storm in its local mode. > > For small applications, that only had up to ~3 simple topologies, this > worked great. However, for slightly larger systems (~5 topologies) I find > that some of the topologies are not executed. I suspect that the local > cluster is configured with a small number of executors, so when the number > of bolts and spouts I'm using (with p=1) exceeds the number of executors, > no further topologies are scheduled. > > I know the "real" solution to this problem is to use a real cluster, but > using local mode is very convenient for development. > > Is there a config I can set to tune up the number of executors (or > alternatively, is my understanding of the problem correct)? > > Thanks, > Boaz. > >
