You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@storm.apache.org by "zhangbiao (JIRA)" <ji...@apache.org> on 2017/08/19 02:29:00 UTC

[jira] [Updated] (STORM-2696) storm-kafka-client doesn't emit tuple when numUncommittedOffsets - readyMessageCount >= maxUncommittedOffsets

     [ https://issues.apache.org/jira/browse/STORM-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

zhangbiao updated STORM-2696:
-----------------------------
    Summary: storm-kafka-client doesn't emit tuple when numUncommittedOffsets - readyMessageCount >= maxUncommittedOffsets  (was: storm-kafka-client doesn't emit tuple when numUncommittedOffsets - readyMessageCount > maxUncommittedOffsets)

> storm-kafka-client doesn't emit tuple when numUncommittedOffsets - readyMessageCount >= maxUncommittedOffsets
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: STORM-2696
>                 URL: https://issues.apache.org/jira/browse/STORM-2696
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-kafka-client
>            Reporter: zhangbiao
>
> for example, when set maxUncommittedOffsets = 10, at first kafka-comsumer fetech 500 messges from remote, with 490 messages failed and 10 messgaes acked. at this condititon the 
>  `waitingToEmit` is empty, and `numUncommittedOffsets - readyMessageCount  = 10 >= maxUncommittedOffsets` , the client will never meet the condition to poll again



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)