The topology.debug is set to true, please storm.yaml. Disable that and try putting log statements before and after emit calls and take it from there. Initially try send a single message to check if the topology behaves as expected.
Thanks and Regards, Devang On 15 Nov 2014 11:07, "Minqi Jiang" <[email protected]> wrote: > Hi all, > > I've written some python code for a spout that emits tuple values based on > user's Twitter timelines. In order to emit the proper tuple values, I > iterate through the user's timeline of historical tweets. However, I find > that if I include the code to iterate through a user's timeline in my > nextTuple method, the spout does not properly emit tuples. Instead, I see > the following debug message printed out whenever a tuple should be emitted: > > 66861 [Thread-14-counter] INFO backtype.storm.daemon.task - Emitting: > counter __metrics [#<TaskInfo > backtype.storm.metric.api.IMetricsConsumer$TaskInfo@457cb2f7> > [#<DataPoint [__ack-count = {}]> #<DataPoint [__sendqueue = {capacity=1024, > write_pos=0, read_pos=0, population=0}]> #<DataPoint [__receive = > {capacity=1024, write_pos=3, read_pos=2, population=1}]> #<DataPoint > [__process-latency = {}]> #<DataPoint [__transfer-count = {}]> #<DataPoint > [__execute-latency = {}]> #<DataPoint [__fail-count = {}]> #<DataPoint > [__emit-count = {}]> #<DataPoint [__execute-count = {}]>]] > > It's not clear to me what is going wrong. Any pointers on how to debug > this would be much appreciated. > > Thanks! > > >
