[
https://issues.apache.org/jira/browse/KAFKA-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036089#comment-16036089
]
Apurva Mehta commented on KAFKA-5347:
-------------------------------------
I think this can be punted to a bug fix release. This is a minor improvement
which would make the producer failure modes more consistent and make the user
experience a little better once there is an OutOfOrderSequence error (which
should really never happen).
But I think our current priority for the 0.11.0.0 release should be getting the
transactions system tests fully stable on streams and core, and I think we
still have a lot of work to do there.
> 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.3.15#6346)
