You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "HaiyuanZhao (Jira)" <ji...@apache.org> on 2020/10/10 04:27:00 UTC
[jira] [Updated] (KAFKA-10596) Adding some state to
TransactionMetadata which explicitly indicates that the transaction was
timed out
[ https://issues.apache.org/jira/browse/KAFKA-10596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
HaiyuanZhao updated KAFKA-10596:
--------------------------------
{code:java}
The code assumes that if we get a receive an EndTxn request and lastProducerEpoch has been set, then it must be because the coordinator timed out the transaction. That is definitely true in the common case, but I'm wondering if it is worth adding some state to TransactionMetadata which explicitly indicates that the transaction was timed out. Not super important and could be done in a follow-up.
{code}
A follow-up quoted above from comment https://github.com/apache/kafka/pull/9311#discussion_r501196960
> Adding some state to TransactionMetadata which explicitly indicates that the transaction was timed out
> ------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-10596
> URL: https://issues.apache.org/jira/browse/KAFKA-10596
> Project: Kafka
> Issue Type: Improvement
> Reporter: HaiyuanZhao
> Assignee: HaiyuanZhao
> Priority: Minor
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)