As long the workers and tasks in machine A are healthy and sending hearbeats to Nimbus, they will keep running there. A redeployment of the topologies or a a rebalance command (you can use Storm UI for this), may send tasks to be executed in machine B.
On Fri, Feb 21, 2020, 22:14 Zainal Arifin (BLOOMBERG/ 731 LEX) < [email protected]> wrote: > Hi, > We run Storm on 2 machines (let's call it machine A and B), and everything > works fine. > Then I want to test the machine being reboot, so basically when the > machine being brought down, it'll call my script to stop Storm, and when > the machine back up, it called my script to start Storm. > > From my testing to reboot 1 machine (let say B), after the machine is back > online, I notice Storm runs fine there, but I see all spout/bolt tasks are > running on machine A. I waited for a few minutes (now it's already 1 hour), > and all tasks are still running on machine A. > > I'd expect some of the tasks will be automatically distributed (rebalance) > to machine B, is that not the case? Or is there something I need to > configure? Thanks! >
