kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Damian Guy (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-5870) Idempotent producer: a producerId reset causes undesirable behavior for inflight batches to other partitions
Date Thu, 01 Feb 2018 11:58:08 GMT

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

Damian Guy updated KAFKA-5870:
------------------------------
    Fix Version/s:     (was: 1.1.0)
                   1.2.0

> Idempotent producer: a producerId reset causes undesirable behavior for inflight batches
to other partitions
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-5870
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5870
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.11.0.0
>            Reporter: Apurva Mehta
>            Assignee: Apurva Mehta
>            Priority: Major
>              Labels: exactly-once
>             Fix For: 1.2.0
>
>
> Currently, if we have to reset the producer id for any reason (for instance if batches
to a partition get expired, if we get an {{OutOfOrderSequenceException}}, etc) we could cause
batches to other --healthy-- partitions to fail with a spurious {{OutOfOrderSequenceException}}.
> This is detailed in this PR discussion: https://github.com/apache/kafka/pull/3743#discussion_r137907630
> Ideally, we would want all inflight batches to be handled to completion rather than potentially
failing them prematurely. Further, since we want to tighten up the semantics of the {{OutOfOrderSequenceException}},
at the very least we should raise another exception in this case, because there is no data
loss on the broker when the client gives up. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message