You are correct. Rebalance updates the state so when mk-assignments is called the scheduler does not see any workers associated with that topology. It then will proceeded to reschedule it wherever the scheduler thinks is best. Storm does not do any dynamic rebalancing yet. But if you have a killer algorithm for it I would be happy to help update it so that it could.
―Bobby On 3/21/14, 1:18 AM, "hilfi alkaff" <[email protected]> wrote: >Walk me through if I'm understanding the code correctly. I'm still very >new >to clojure. In cluster.clj, update-storm! just change the internal state >variables, but it has not actually changed the state of the cluster? The >actual changes happen at mk-assignments when it calls assignSlots? > >Additionally, storm does not perform any dynamic rebalancing in the fly >correct? Or has there been a plan to do that? Thanks. > > >On Wed, Mar 19, 2014 at 12:18 AM, 杨晓青 <[email protected]> wrote: > >> in file /storm-core/src/clj/backtype/storm/cluster.clj >> >> >> 2014-03-19 11:42 GMT+08:00 hilfi alkaff <[email protected]>: >> >> > Hi, >> > >> > I would like to know how does Storm currently perform rebalance. I >>see in >> > *./storm-core/src/clj/backtype/storm/daemon/nimbus.clj* there's a >> > *do-rebalance* method that will call *update-storm!* (Which I assume >> > changes the state of Storm) but I don't see where the method >> > *update-storm!*is being defined. >> > >> > Thanks, >> > >> > -- >> > Hilfi M. Alkaff >> > >> >> >> >> -- >> ------------------------------------------- >> best regards >> >> 杨晓青 >> > > > >-- >~Hilfi Alkaff~
