You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Jason Gustafson (Jira)" <ji...@apache.org> on 2020/11/30 22:49:00 UTC
[jira] [Updated] (KAFKA-10702) Slow replication of empty
transactions
[ https://issues.apache.org/jira/browse/KAFKA-10702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Gustafson updated KAFKA-10702:
------------------------------------
Issue Type: Improvement (was: Bug)
> Slow replication of empty transactions
> --------------------------------------
>
> Key: KAFKA-10702
> URL: https://issues.apache.org/jira/browse/KAFKA-10702
> Project: Kafka
> Issue Type: Improvement
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Priority: Major
>
> We hit a case in which we had to re-replicate a compacted topic from the beginning of the log. Some portions of the log consisted mostly of transaction markers, which were extremely slow to replicate. The problem is that `ProducerStateManager` adds all of these empty transactions to its internal collection of `ongoingTxns` before immediately removing them. There could be tens of thousands of empty transactions in the worst case from a single `Fetch` response, so this can create a huge amount of pressure on the broker.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)