Hi! AFAIK, "setup-tick!" is called from start of executor (which schedules tick timer for each executor), and tick tuples will be emitted unless worker is going to be shutdown.
In short, your fellow is correct. Thanks! Jungtaek Lim (HeartSaVioR) 2015-06-08 21:52 GMT+09:00 Dan Blanchard <[email protected]>: > > As part of the development of streamparse > <https://github.com/Parsely/streamparse/>, we have a BatchingBolt that > processes tuples in batches. It's intended for use with things like > databases that are more performant when you send things in batches. > > I've recently proposed switching our BatchingBolt implementation over from > using a timer/thread approach to using tick tuples; however, one of my > fellow devs pointed out that with our current approach the final batch will > definitely get processed when a topology is shutdown (and it's in the > inactive state), whereas that won’t happen if tick tuples aren’t arriving > to trigger batch processing. Unfortunately, whether or not tick tuples > keep getting sent when I topology is inactive isn't explicitly documented > anywhere I can find. > > Therefore, my question is this: does Storm continue sending tick tuples to > bolts after a kill/deactivate has been issued, while it is in the > waiting/inactive period? The topology lifecycle docs > <http://storm.apache.org/documentation/Lifecycle-of-a-topology.html> don't > make it clear. > > Thanks, > > Dan > > PS: I also posted this as a StackOverflow question > <http://stackoverflow.com/questions/30538252/does-storm-keep-sending-tick-tuples-to-bolts-when-a-topology-is-deactivated>, > if you want to respond there. > > -- Name : 임 정택 Blog : http://www.heartsavior.net / http://dev.heartsavior.net Twitter : http://twitter.com/heartsavior LinkedIn : http://www.linkedin.com/in/heartsavior
