Hi guys,

In the discussions I found regarding changing scale of the topology (how many 
bolts and spout tasks we should have in given topology) I found recommendation 
to do swapping instead of trying to change topology definition dynamically.

For that it is recommended to deploy new topology in deactivated state, pause 
consumption in spouts of old topology and then after message timeout - activate 
consumption in new topology.


1.      Is this recommendation correct?

2.      How topology can be deployed in deactivated state?

3.      Is there standard way to pause consumption in spouts of old topology?

Thanks,
Alex

Reply via email to