Related question on this, what’s a more preferable deployment pattern - use lots of ports like the one mentioned below on a super powerful physical machine - V.S. maybe, one port per node, but have lots of less powerful VM to run each node
Thanks, Hefeng > On Dec 4, 2014, at 9:13 AM, Kushan Maskey > <[email protected]> wrote: > > Thanks Parth for your response. That issue has been resolved. > > Harsh, I have bunch of topologies running in a server. I set the > supervisor.slots.ports in the storm.yaml file as > > supervisor.slots.ports: > 6700,6701,6702,6703,6704,6705,6706,6707,6708,6709,6710,6711,6712,6713,6714,6715,6716,6717,6718,6719,6720,6721,6722,6723,6724,6725,6726,6727,6728 > > All my topologies write logs to the work-6700.log and so on which is making > it difficult to debug any exception. So I was thinking I will set it up in > the topology to write it on a specific logfile based on the port. for > example, i wanna write the logs in the series of 7000, 7001 ... for the > topoligy 1 and then 6000, 6001 for topology 2 and so on. > Is this not possible? > > Thanks. > > -- > Kushan Maskey > 817.403.7500 > M. Miller & Associates <http://mmillerassociates.com/> > [email protected] > <mailto:[email protected]> > On Thu, Dec 4, 2014 at 11:03 AM, Harsha <[email protected] > <mailto:[email protected]>> wrote: > Kushan, > You won't be able to modify supervisor_slots_ports from the topology > config. Any reason for doing this in topology as you can define this in > storm.yaml. > -Harsha > > > On Thu, Dec 4, 2014, at 08:58 AM, Kushan Maskey wrote: >> Is there a way I can set supervisor_slots_port in the config in the topology >> class? I tried to set it up like below >> >> config.put(Config.SUPERVISOR_SLOTS_PORTS, 7000); >> >> but I get error as below. >> InvalidTopologyException(msg:Field supervisor.slots.ports must be an >> Iterable of java.lang.Number >> >> Thanks. >> >> -- >> Kushan Maskey >> 817.403.7500 <tel:817.403.7500> >> M. Miller & Associates <http://mmillerassociates.com/> >> [email protected] >> <mailto:[email protected]> > >
