[jira] [Commented] (KAFKA-5347) OutOfSequence error should be fatal
[
https://issues.apache.org/jira/browse/KAFKA-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770555#comment-16770555
]
Matthias J. Sax commented on KAFKA-5347:
Moving all major/minor/trivial tickets that are not merged yet out of 2.2
release.
> 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
>Priority: Major
> Labels: exactly-once
> Fix For: 2.2.0
>
>
> 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
(v7.6.3#76005)
[jira] [Commented] (KAFKA-5347) OutOfSequence error should be fatal
[
https://issues.apache.org/jira/browse/KAFKA-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636544#comment-16636544
]
Dong Lin commented on KAFKA-5347:
-
Moving this to 2.2.0 since there is no PR ready.
> 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
>Priority: Major
> Labels: exactly-once
> Fix For: 2.2.0
>
>
> 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
(v7.6.3#76005)
[jira] [Commented] (KAFKA-5347) OutOfSequence error should be fatal
[
https://issues.apache.org/jira/browse/KAFKA-5347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184012#comment-16184012
]
Ismael Juma commented on KAFKA-5347:
[~apurva], is this still an issue?
> 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: 1.1.0
>
>
> 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)
