[
https://issues.apache.org/jira/browse/STORM-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim updated STORM-2087:
--------------------------------
Added to 1.1.0 epic since it's a major bug and patch is available (PR against
master is merged.)
> Storm-kafka-client: Failed tuples are not always replayed
> ----------------------------------------------------------
>
> Key: STORM-2087
> URL: https://issues.apache.org/jira/browse/STORM-2087
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-kafka-client
> Affects Versions: 2.0.0, 1.0.2
> Reporter: Jeff Fenchel
> Assignee: Jeff Fenchel
> Fix For: 2.0.0
>
> Time Spent: 10h
> Remaining Estimate: 0h
>
> I am working with kafka 10 and the storm-kafka-client from master. It appears
> that tuples are not always being replayed when they are failed.
> With a topology that randomly fails tuples a small percentage of the time I
> found that the committed kafka offset would get stuck and eventually
> processing would stop even though the committed offset was no where near the
> end of the topic.
> I have also replicated the issue in unit tests with this PR:
> https://github.com/apache/storm/pull/1679
> It seems that increasing the number of times I call nextTuple for the in
> order case will make it work, but it doesn't seem to help the case where
> tuples are failed out of order from which they were emitted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
