Is there a clean way to stop storm without killing it with "kill XXX" where XXX is the PID?
I run "storm kill topology-name" to kill the topology, but after that, is there a clean way to shutdown workers, nimbus, supervisor and ui?
I didn't find any command which corresponds to this from the documentation: https://github.com/nathanmarz/storm/wiki/Command-line-client
Seek shelter immediately either in an enclosed building or a hard-topped vehicle. There is no safe place outside in a thunderstorm. If caught outside far from a safe location, stay away from tall objects, such as trees, poles, wires and fences. Take shelter in a low lying area.
Command to kill a topology (as you rightly mentioned):
storm kill topology-name
To shutdown the cluster you need to run the following command on each node:
sudo service supervisord stop
Note: give supervisord
a few seconds to shutdown all processes. Note that trying to run supervisorctl
when supervisord itself is stopped will result in an error message (this appears to be a known user interface issue in supervisord 2.x)
From this documentation
How to kill ALL Storm processes including worker processes? Any worker threads (launched by the Supervisor daemons on the slave nodes) that happen to be running when you are stopping the cluster will continue to run. This is a deliberate design decision of Storm because it means that crashing/restarting Nimbus and Supervisor daemons will not affect any running topologies in Storm. The downside is that you have to put some extra effort into fully stopping all Storm-related processes in a cluster.
If you want to kill ALL processes follow this procedure on the slave nodes:
$ sudo supervisorctl stop storm-supervisor
$ sudo pkill -TERM -u storm -f 'backtype.storm.daemon.worker'
From the page that you linked to:
kill
Syntax: storm kill topology-name [-w wait-time-secs]
Kills the topology with the name topology-name. Storm will first deactivate the topology's spouts for the duration of the topology's message timeout to allow all messages currently being processed to finish processing. Storm will then shutdown the workers and clean up their state. You can override the length of time Storm waits between deactivation and shutdown with the -w flag.
As you can see, this is designed to give you a "clean" shutdown. The kill command shuts down the workers.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With