both of them have a scheduled
> maintenance, which the infra team has procedure which it'll call our stop
> script before machine reboot, and call our start script after reboot.
> In our stop script, it kills following components: nimbus, supervisor and
> ui, then in start script,
efore
machine reboot, and call our start script after reboot.
In our stop script, it kills following components: nimbus, supervisor and ui,
then in start script, it launches: nimbus, supervisor and ui.
Right now I don't have script to check if topology is running yet, as I am
still experime
, what would be the command or API?
>
> From: rui.ab...@gmail.com At: 02/21/20 16:48:53
> To: Zainal Arifin (BLOOMBERG/ 731 LEX ) ,
> user@storm.apache.org
> Subject: Re: machine reboot
>
> As long the workers and tasks in machine A are healthy and sending
> hearbeats to Nimbu
) , user@storm.apache.org
Subject: Re: machine reboot
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
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 (BL
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 m
