[jira] [Commented] (STORM-2087) Storm-kafka-client: Failed tuples are not always replayed

["Stig Rohde Døssing (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/STORM-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15749093#comment-15749093 ] 

Stig Rohde Døssing commented on STORM-2087:
-------------------------------------------

[~asmaier] Yes, as far as I can tell. 

> 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.x
>            Reporter: Jeff Fenchel
>          Time Spent: 9h 10m
>  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)