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/11 23:02:00 UTC

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

Jason Gustafson created KAFKA-5730:
--------------------------------------

             Summary: 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)