Installing the Storm Client - Getting Started with Storm - page 88

path-to-topology-jar is the complete path to the compiled jar where your topology code
and all your libraries are. The class-with-the-main will be the main place where the
StormSubmitter is executed and the rest of arguments will be the params that receive
our main method.
With Storm you have the capability to suspend or disable a running topology, deacti-
vating the topology spouts, so when we deactivate the topology, all emitted tuples will
be processed, but the nextTuple method of the topology spouts will not be called.
To disable a topology, run:
storm deactivate topology-name
If you want re-activate a disabled topology, run:
storm activate topology-name
If you want to destroy a topology, you can use the kill command. This will destroy
the topology in a secure fashion, disabling the topology first and waiting for the dura-
tion of the topology's message, allowing the topology to finish the process of the current
streams.
To kill a topology, run:
storm kill topology-name
You can change the waiting time after the topology is deactivated using
the -w [time-in-sec] parameter when you run the Storm kill command.
Rebalance enables you to redistribute the tasks through all worker tasks into a cluster.
This is a powerful command when you have not balanced your tasks. For example,
when you add nodes to a running cluster. The rebalance command will deactivate the
topology for the duration of message timeout and redistribute the workers so Storm
will re-activate the topology.
To rebalance a topology, run:
storm rebalance topology-name
If you want to use another deactivation duration, you could use the -w parameter to set
it:
storm rebalance topology-name -w other-time
You can see the complete list of Storm commands by running the Storm
client without parameters. The complete description of these com-
mands can be found at https://github.com/nathanmarz/storm/wiki/Com
mand-line-client .