You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Xiang Zhang (Jira)" <ji...@apache.org> on 2020/03/18 00:20:00 UTC
[jira] [Comment Edited] (KAFKA-5604) All producer methods should
raise `ProducerFencedException` after the first time.
[ https://issues.apache.org/jira/browse/KAFKA-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061275#comment-17061275 ]
Xiang Zhang edited comment on KAFKA-5604 at 3/18/20, 12:19 AM:
---------------------------------------------------------------
Also, under that TODO marker, it says "this should actually never happen", I am confused by that because ProducerFencedException is always possible when two transactional instances exist at the same moment.
was (Author: iamabug):
Also, under that TODO marker, it says "this should actually never happen", I am confused by that because ProducerFencedException is always possible where two transactional instances exist at the same moment.
> All producer methods should raise `ProducerFencedException` after the first time.
> ---------------------------------------------------------------------------------
>
> Key: KAFKA-5604
> URL: https://issues.apache.org/jira/browse/KAFKA-5604
> Project: Kafka
> Issue Type: Bug
> Reporter: Apurva Mehta
> Assignee: Apurva Mehta
> Priority: Major
>
> Currently, when a `ProducerFencedException` is raised from a transactional producer, the expectation is that the application should call `close` immediately. However, if the application calls other producer methods, they would get a `KafkaException`. This is a bit confusing, and results in tickets like : https://issues.apache.org/jira/browse/KAFKA-5603.
> We should update the producer so that calls to any method other than `close` should raise a `ProducerFencedException` after the first time it is raised.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)