kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ismael Juma (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-5347) OutOfSequence error should be fatal
Date Tue, 27 Jun 2017 14:50:00 GMT

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

Ismael Juma updated KAFKA-5347:
-------------------------------
    Parent Issue: KAFKA-5527  (was: KAFKA-4815)

> OutOfSequence error should be fatal
> -----------------------------------
>
>                 Key: KAFKA-5347
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5347
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Jason Gustafson
>            Assignee: Apurva Mehta
>              Labels: exactly-once
>             Fix For: 0.11.0.1
>
>
> If the producer sees an OutOfSequence error for a given partition, we currently treat
it as an abortable error. This makes some sense because OutOfSequence won't prevent us from
being able to send the EndTxn to abort the transaction. The problem is that the producer,
even after aborting, still won't be able to send to the topic with an OutOfSequence. One way
to deal with this is to ask the user to call {{initTransactions()}} again to bump the epoch,
but this is a bit difficult to explain and could be dangerous since it renders zombie checking
less effective. Probably we should just consider OutOfSequence fatal for the transactional
producer.



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

Mime
View raw message