You can perform following steps : Deactivate Topology and give a reasonable amount of time for deactivation This will internally stops spout to produce tuples and let bolts finish consuming tuples which are already in the queue. If you don’t want topology to be present when storm restarted then kill the topology kill all the storm processes
> On 28-Feb-2017, at 12:36 PM, shawn.du <shawn...@neulion.com.cn> wrote: > > Hi, > > how to shutdown storm cluster gracefully? like persist bolt finish writing. > I add workerhook for topology. > for workerhook, what's cluster status when calling hook's shutdown method? > I meant,for example, kafkaspout already stopped consuming message from kafka? > if not, how can I manually stop spouts/bolts. for stateful bolts, how to make > sure the state already persist? > > Thanks > Shawn
