Github user srdo commented on the issue:
https://github.com/apache/storm/pull/1919
@HeartSaVioR That's pretty much my understanding of this as well. I'm not
sure what order the ack/emit happens in when ackers=0, but if it's ack followed
by emit, then it should be enough to put a `KafkaConsumer.commitSync` call in
`KafkaSpout.ack`. `commitSync` guarantees that the committed offset is properly
committed when it returns.
I agree that this is how it should work for case 3.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
