You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2017/08/17 22:06:00 UTC

[jira] [Resolved] (KAFKA-5730) Consumer should ensure consistent ordering between sync and async offset commits

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

Jason Gustafson resolved KAFKA-5730.
------------------------------------
    Resolution: Fixed

Issue resolved by pull request 3666
[https://github.com/apache/kafka/pull/3666]

> Consumer should ensure consistent ordering between sync and async offset commits
> --------------------------------------------------------------------------------
>
>                 Key: KAFKA-5730
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5730
>             Project: Kafka
>          Issue Type: Bug
>          Components: consumer
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>             Fix For: 1.0.0
>
>
> If {{commitSync}} is called with an async offset commit in-flight, it is possible (even likely) for it to return prior to the invocation of the async callback even though the OffsetCommit request for the latter will have actually completed first. In this case, the async callback is not invoked until the next call to {{poll}}, which can lead to very confusing behavior since the client is led to think that the async commit happened second.



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