Thanks Maatthias. One more question - I was scouring the logs to see the buffer capacity and populations and they appear very intermittently in the logs. Would you know what makes them appear? :) The topology is at DEBUG and have enabled logback to DEBUG as well.
On Thu, Jul 23, 2015 at 12:21 AM, Matthias J. Sax < [email protected]> wrote: > It's the ID of the task that emitted the tuple. > > > On 07/23/2015 12:08 AM, Kashyap Mhaisekar wrote: > > Hi, > > > > What does the number 3 in the text highlighted indicate - > > --------------- > > backtype.storm.daemon.executor - Processing received message > > source:* f**etchoffercount:3*, stream: defaul > > --------------------- > > 2015-07-22 16:47:20 [Thread-19-aggregates] INFO > > backtype.storm.daemon.executor - Processing received message source: > > evaluateoffers:2, stream: default, id: {}, [JVMmain-1437601637443-01, > > OFF:289:Qualified, 100] > > 2015-07-22 16:47:20 [Thread-14-redisspout] INFO > > backtype.storm.daemon.task - Emitting: redisspout default > > [JVMmain-1437601637444-01, Kashyap] > > 2015-07-22 16:47:20 [Thread-14-redisspout] INFO > > backtype.storm.daemon.executor - Acking message ack > > 2015-07-22 16:47:20 [Thread-10-evbolt] INFO > > backtype.storm.daemon.executor - Processing received message > > source:*f**etchoffercount:3*, stream: default, id: {}, > > [JVMmain-1437601637444-01, Kashyap, 100] > > > > thanks > > kashyap > >
