You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/05/16 18:15:13 UTC

[jira] [Commented] (STORM-1838) [storm-kafka-client] the resumed OffsetEntry goes different

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

ASF GitHub Bot commented on STORM-1838:
---------------------------------------

Github user ptgoetz commented on the pull request:

    https://github.com/apache/storm/pull/1419#issuecomment-219501512
  
    another JIRA integration test. Ignore.


> [storm-kafka-client] the resumed OffsetEntry goes different
> -----------------------------------------------------------
>
>                 Key: STORM-1838
>                 URL: https://issues.apache.org/jira/browse/STORM-1838
>             Project: Apache Storm
>          Issue Type: Bug
>            Reporter: Jifeng Yin
>             Fix For: 1.0.1
>
>
> There are no more new messages after consumer rejoins the group. And it turns out the old OffsetEntry instance kept commitOffsetsForAckedTuples failing.
> the comment "leave the acked offsets as they were to resume where it left off" doesn't work for me, but the ackedMsgs goes different.



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