Github user srdo commented on the issue:
https://github.com/apache/storm/pull/1924
Sorry to keep changing this. I hope these are the last few changes. The
spout should now seek to the lowest retriable offset for each partition when
retrying tuples, instead of seeking back to the last committed offset. This
means there's not as far as I can see any reason to worry about maxPollRecords
being set too low compared to maxUncommittedOffsets, so I've reverted that part
of KafkaSpoutConfig.
---
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.
---
