[jira] [Commented] (STORM-1595) 'Fail' messages get stuck somewhere

["Abhishek Agarwal (JIRA)" <ji...@apache.org>]

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

Abhishek Agarwal commented on STORM-1595:
-----------------------------------------

can you tell us the following configurations in your topology
 - topology.message.timeout.secs
- topology.tick.tuple.freq.secs
- async flag and batch size for kafka bolt

My hunch is that with kafka bolt fails a tuple in a callback which takes some time. In this time, init entry is timed out from acker bolt. when fail entry comes to the acker bolt, it will also get timed out eventually. Tuple will be marked failed after `topology.message.timeout.secs` even though the bolt fails it earlier. Though this hypothesis may be invalid if you are not overriding the topology.tick.tuple.freq.secs.

> 'Fail' messages get stuck somewhere 
> ------------------------------------
>
>                 Key: STORM-1595
>                 URL: https://issues.apache.org/jira/browse/STORM-1595
>             Project: Apache Storm
>          Issue Type: Bug
>    Affects Versions: 1.0.0, 2.0.0
>            Reporter: Kyle Nusbaum
>         Attachments: screenshot-1.png
>
>
> 'Fail' acks seem to be getting stuck somewhere between the acker and the spout. 
> After a long time - sometimes multiple minutes - the fails show up in the spout.
> I tested this on master and 1.x-branch and it occurs in both places.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)