[ 
https://issues.apache.org/jira/browse/KAFKA-20000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046980#comment-18046980
 ] 

Francis Godinho edited comment on KAFKA-20000 at 12/22/25 6:49 AM:
-------------------------------------------------------------------

[~jolshan], [~chia7712] I noticed that the AddPartitionsToTxnHandler class has 
similar logic, but uses a fixed value: 
[https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/producer/internals/TransactionManager.java#L1649]

Since I'm adding the add.partitions.to.txn.retry.backoff.ms parameter to the 
client side for TxnOffsetCommitHandler, would it also make sense to change the 
logic in AddPartitionsToTxnHandler.maybeOverrideRetryBackoffMs to use that 
parameter too? Should I just do that in this ticket as well? 


was (Author: JIRAUSER308403):
[~jolshan], [~chia7712] I noticed that the AddPartitionsToTxnHandler class has 
similar logic, but uses a fixed value: 
[https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/producer/internals/TransactionManager.java#L1649]

Since I'm adding the add.partitions.to.txn.retry.backoff.ms parameter to the 
client side for TxnOffsetCommitHandler, would it also make sense to change the 
logic in AddPartitionsToTxnHandler to use that parameter too? Should I just do 
that in this ticket as well? 

> Optimize retry backoff for CONCURRENT_TRANSACTIONS to improve TV2 throughput
> ----------------------------------------------------------------------------
>
>                 Key: KAFKA-20000
>                 URL: https://issues.apache.org/jira/browse/KAFKA-20000
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Chia-Ping Tsai
>            Assignee: Francis Godinho
>            Priority: Major
>             Fix For: 4.3.0
>
>
> Transaction V2 introduces frequent state transitions (epoch bumps) that 
> briefly reject concurrent requests with CONCURRENT_TRANSACTIONS. The default 
> client retry backoff (100ms) is excessive for these transient locks, leading 
> to unnecessary latency and degraded throughput. Reducing the backoff allows 
> faster retries and smoother performance during state transitions.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to