> I'm a bit confused by your email, since you state "the tuples just keep > coming" and "I'm not seeing retries". I guess this means: other tuples are > still flowing, but not the ones you expected to be retried.
That’s correct. My expectation is that with topology.max.spout.pending=1, emitting a tuple but not acking it will halt processing until the emitted tuple times out. That isn’t happening, instead the rest of the messages from the Kafka queue continue to be emitted. > Do you have ackers enabled for your storm topology? i.e., what is the > topology.acker.executors config value? > Storm spouts will automatically ack tuples if you have 0 for this value. I had never bothered setting this before for LocalCluster, and it’s never been a problem before with our custom spouts; I’ve only ever seen this behavior with the KafkaSpout. But I went ahead and set it to 1 and the behavior is the same. Thanks
