Srinath, Thanks for your reply. I guess the builtin ticks are not for me. I'll have to implement my own approach....
Cheers, Jeyendran On Sun, Jul 5, 2015 at 5:04 PM, Srinath C <[email protected]> wrote: > Hi Jayendran, > > You can configure specific bolts (like SummingBolt, HBaseBolt) to receive > tick tuples and by doing so each instance of that bolt will receive the > tick tuple. > I don't think it is possible to configure ticks to be received on exactly > one of a bolt's instances. > I guess that answers all you questions. > > Regards, > Srinath. > > > On Mon, Jul 6, 2015 at 1:01 AM, Jeyendran Balakrishnan < > [email protected]> wrote: > >> I have some questions about ticks: >> 1. If ticks are setup, are they broadcast to all instances of all active >> bolts in the topology? >> 2. If not, how can we setup ticks to be sent ONLY to active bolts of a >> certain type, eg., HBaseBolt, SummingBolt, etc? >> 3. Going further, can we setup ticks to be sent to different bolts at >> different frequencies, eg., 1 minute for HBaseBolt, and 5 minutes for >> SummingBolt, etc, and none to other bolts in the topology? >> 4. Finally, are ticks sent to ALL instances (tasks) of each active bolt, >> or any one instance will get the tick? ie., if I setup SummingBolt with >> parallelism of 10, will each of the 10 tasks/instances of SummingBolt get >> each tick? Or will each tick be sent to exactly one of these instances >> (maybe the receiving task/instance will vary for each received tick)? >> >> Basically, I want to ensure that if ticks are turned on, they don't flood >> the networks and load up all the bolts that don't need ticks, >> that ticks can be sent only to subscribing bolts at their chosen >> frequencies, and that ticks are not sent to all parallelly running >> instances of each subscribing bolt but only to one of these instances. >> >> Thanks, >> Jeyendran >> >> >
