Re: Stateful bolts and acking

Hi Arun, I'm extending from BaseStatefulBolt, only empty impls and I'm anchoring in the spout emit. And I'm running in LocalCluster. I also tried with premade spouts to assure that I didn't make a mistake there. Which branch should I try? Is head of the 1.x-branch

Re: Stateful bolts and acking

Hi Alexander, The simple topology like the one you have mentioned with a single spout and a stateful bolt with an empty execute works for me. I assume you are anchoring the tuple in the spout’s emit. For a stateful topology, the acking doesn’t work if a bolt extends from BaseBasicBolt or if

Re: Stateful bolts and acking

Hi Arun, Thank you for your reply. I have tried both manual and automatic acking, and neither works. Or rather, the acker is running but my spout is still receiving failure callbacks after the message timeout. I have a simple topology with a single spout reading from a file and a single empty

Re: How to emit the values in a for-each loop

Since you are declaring that you emit two values you need to emit two values any time you call emit. If you want to emit two totally different things at different times (ids and nms) you should set up the bolt to emit on two different channels. You should also only "ack" your tuple once, at

Stateful bolts and acking

Hello! I'm on the 1.x-branch and trying to use the stateful bolts. But I cannot get it to work with acking. No matter what I try acking simply doesn't seem to have any effect. I see acking tasks suceeding in the logs (ack tuples forwarded to the acker, acker runs successfully), but still acking

storm-hdfs - hdfs bolt failing after 24hrs

Hi, My storm topology which reads from kafka and writes to hadoop hdfs is failing exactly after 24hrs!! I suspect the problem is, topology was not able to renew the tokens/not finding the keytabs to renew. Please share your thoughts and help me fix the issue. Please find the code used to