Thanks! It was something like that... there were settings overriding my delay in another place. Storm contrib is such treasure chest :)
-A From: Michael Rose [mailto:[email protected]] Sent: December-23-13 10:02 AM To: [email protected] Subject: RE: Tick Tuple The issue is you've multiplied ticktuplems by 1000 vs dividing. So you're probably not waiting long enough ;) If you need an alternate spout, see storm contrib. There's a halfway decent one. On Dec 23, 2013 7:58 AM, "Adrian Mocanu" <[email protected]<mailto:[email protected]>> wrote: If anyone is interested, I've decided to make my own Tick Spout. From: Adrian Mocanu [mailto:[email protected]<mailto:[email protected]>] Sent: December-20-13 4:39 PM To: [email protected]<mailto:[email protected]> Subject: Tick Tuple Hi everybody, I'm trying to have sent tick tuples to a bolt I have. In the bolt I have these methods def execute(tuple: Tuple){ isTickTuple(tuple) match { case true => println("TICK TUPLE FOUND") case false => println("regular TUPLE FOUND") } } override def getComponentConfiguration(): java.util.Map[String,AnyRef] = { val conf = new Config() val tickFrequencyInSeconds = sendPeriodMs * 1000 conf.put(Config.TOPOLOGY_TICK_TUPLE_FREQ_SECS, Long.box(tickFrequencyInSeconds)) conf } def isTickTuple(tuple:Tuple):Boolean = { tuple.getSourceComponent().equals(Constants.SYSTEM_COMPONENT_ID) && tuple.getSourceStreamId().equals(Constants.SYSTEM_TICK_STREAM_ID) } The code never prints "TICK TUPLE FOUND" but in the log I do see that a tick tuple was received executor [INFO] Processing received message source: __system:-1, stream: __tick, id: {}, [30] Why can't I find these tick tuples when running, but they appear in the log? Do tick tuples have some special logic which makes them transparent to the bolt? I use storm 0.8.X -Adrian
