Github user XuMingmin commented on the issue:
https://github.com/apache/storm/pull/1919
Good point to document the impact, is preparing an update PR.
According to my understand, there's no replay for AT-MOST-ONCE mode in
storm. We use this mode when data missing is not a concern, and want to remove
the overhead of tuple tracking.
With auto-commit enabled, the consumer's offset will be periodically
committed in the background by Kafka consumer, so no need to track commit
offset status with emitted/numUncommittedOffsets manually.
---
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.
---
