Does Storm keep sending tick tuples to bolts when a topology is deactivated? -


as part of development of streamparse, have batchingbolt processes tuples in batches. it's intended use things databases more performant when send things in batches.

i've proposed switching our batchingbolt implementation on using timer/thread approach using tick tuples; however, 1 of fellow devs pointed out our current approach final batch processed when topology shutdown (and it's in inactive state), whereas isn't explicitly documented anywhere tick tuples.

therefore, question this: storm continue sending tick tuples bolts after kill/deactivate has been issued, while in waiting/inactive period? topology lifecycle docs don't make clear.

http://mail-archives.apache.org/mod_mbox/storm-user/201506.mbox/%3ccaf5108ijgpdmeax1lakq1mg6mszqf=ym=vo8aacmn0ruinfnkq@mail.gmail.com%3e

afaik, "setup-tick!" called start of executor (which schedules tick timer each executor), , tick tuples emitted unless worker going shutdown.

in short, fellow correct.


Comments

Popular posts from this blog

Java 3D LWJGL collision -

spring - SubProtocolWebSocketHandler - No handlers -

methods - python can't use function in submodule -