KIP-1058 — Txn consumer exerts pressure on remote storage when reading non-txn topic
Accepted Kafka 4.0 Tiered StorageTransactions
KIP-1058 adds a `txnIdxEmpty` tagged field to `RemoteLogSegmentMetadataRecord` and `RemoteLogSegmentMetadataSnapshot` so the Remote Log Manager can skip fetching remote transaction indexes for segments that have no aborted transactions. When `isolation.level=READ_COMMITTED` consumers fetch from topics with no aborted transactions, the broker currently scans all remote segment transaction indexes sequentially before reaching local segments, causing excessive remote storage API calls and increased fetch latency.
Details
| Author | Kamal Chandraprakash |
| Status | Accepted |
| Kafka Version | 4.0 |
| JIRA | KAFKA-16780 |
| Wiki | View on Apache Wiki |
| Created | 2024-06-17 |
| Last Modified | 2024-11-06 |
Explore how this KIP affects the Kafka protocol in the Protocol Explorer, or see the full KIP database.