Github user hmcl commented on the pull request:
https://github.com/apache/storm/pull/1419#issuecomment-220102668
@flisky can you please provide specific examples or a code snippet that I
can use to test what you are saying. Can you also post the logs (perhaps on
JIRA) that show the cases that are failing? What do you mean by `offset out of
range`?
As for your first comment, please keep in mind that the
`FirstPollOffsetStrategy`, as the name indicates, it's only for the first poll,
i.e., the first time a `KafkaSpout` polls from Kafka. It does not apply to
consumer rebalance. Quoting the [javadoc](https://goo.gl/PyR7Cm) of "The offset
used by the Kafka spout in the first poll to Kafka broker." Therefore, the
`LATEST/EARLIEST` strategies only apply in the first poll, not on every
consumer rebalance. Furthermore, if a consumer rebalance occurs, but the same
partition is assigned to this spout, and some offsets have already been emitted
and acked, we wan to keep those, and only process the ones that haven't yet
been acked because they have have failed and waiting to be retried (according
to exponential backoff) or may be on the "wire".
What do you mean by -2 , -1? Can you please give specific examples. Thanks.
---
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.
---
