> Can someone explain to me how one would update a live topology?
This was always problematic for our topology, but this is how we did
it. I make no claims about it being optimal or even the best way to do
it. It worked for us after we figured out all the kinks.
For topology changes that are back
Hi,
Storm topology usually gets killed after the tuple timeout (storm kill [-w
timeout_in_seconds] topology_name) assuming that the timeout_in_seconds is
not passed as a parameter. Once the topology kill command is fired, the
spout will not invoke the nextTuple() anymore, but it will wait to recei
Hello,
Can someone explain to me how one would update a live topology?I assume one
would run a new topology with the updated code, and switch off the old one, but
how to make the transition in terms of the data flow?
How to tell the topology to stop pulling data from the queue when the new
topo
