[
https://issues.apache.org/jira/browse/STORM-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288100#comment-15288100
]
ASF GitHub Bot commented on STORM-1838:
---------------------------------------
Github user flisky commented on the pull request:
https://github.com/apache/storm/pull/1419#issuecomment-219907956
Sorry, I didn't say it clearly, but this patch still applies.
Ｗhen a consumer re-balance occurs and
**FirstPollOffsetStrategy#EARLIEST/LATEST**, the retained partition wouldn't
use the committed offset to resume but use the -2 / -1 offset, as I observed,
so this is reason why the comment (`leave the acked offsets as they were to
resume where it left off`) doesn't apply.
> [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)
