[
https://issues.apache.org/jira/browse/STORM-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15335876#comment-15335876
]
ASF GitHub Bot commented on STORM-822:
--------------------------------------
Github user jianbzhou commented on the issue:
https://github.com/apache/storm/pull/1131
@hmcl, just fyi, we found one new issue:
when rebalance happened, in method
onPartitionsAssigned->initialize(Collection<TopicPartition> partitions)
we can see below two lines:
**final OffsetAndMetadata committedOffset = kafkaConsumer.committed(tp);
final long fetchOffset = doSeek(tp, committedOffset);**
If the committedOffset is out of range(say kafka log file removed), the
when the poll() method is called, the offset will reset as the property
auto.offset.reset. This will cause the newly polled message has bigger offset,
so there is a break between committed offset and the acked offset, no
continuous offset will be found.
We will apply a quick fix for this.
> Kafka Spout New Consumer API
> ----------------------------
>
> Key: STORM-822
> URL: https://issues.apache.org/jira/browse/STORM-822
> Project: Apache Storm
> Issue Type: Story
> Components: storm-kafka
> Reporter: Thomas Becker
> Assignee: Hugo Louro
> Fix For: 1.0.0, 2.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
