[
https://issues.apache.org/jira/browse/KAFKA-5603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17058039#comment-17058039
]
Matthias J. Sax commented on KAFKA-5603:
----------------------------------------
Well, nobody worked on KAFKA-5604 and hence it would be nice to get it fixed.
The point being is that after the producer got fenced, `abortTransaction()`
should not be called what Streams did, but we fixed it. I can't remember if the
call to `abortTransaction` resulted in another `ProducerFencedException` or a
`KafkaException` (due to KAFKA-5604). But for this ticket it does not really
matter as an exception would be thrown anyway if the call is made and thus we
now don't make the call any longer.
> Streams should not abort transaction when closing zombie task
> -------------------------------------------------------------
>
> Key: KAFKA-5603
> URL: https://issues.apache.org/jira/browse/KAFKA-5603
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 0.11.0.0
> Reporter: Matthias J. Sax
> Assignee: Matthias J. Sax
> Priority: Critical
> Fix For: 0.11.0.1, 1.0.0
>
>
> The contract of the transactional producer API is to not call any
> transactional method after a {{ProducerFenced}} exception was thrown.
> Streams however, does an unconditional call within {{StreamTask#close()}} to
> {{abortTransaction()}} in case of unclean shutdown. We need to distinguish
> between a {{ProducerFenced}} and other unclean shutdown cases.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
