Hi Andrew, Thanks for the KIP. Changing the default makes sense to me, and 5.0 is the right place for it. I have a few questions.
LB1: On topics without transactions there is nothing for read_committed to filter, so I would not expect a noticeable difference there. For topics that do use transactions, and for tiered topics, is there any concern that the extra work on the fetch path (looking up aborted transactions) will significantly increase the load on brokers in existing applications? LB2: The motivation says KIP-679 enabled idempotence and set acks=1. I believe KIP-679 set acks=all. Could you fix the wording? LB3: It looks like the share group change would apply on each broker individually after the upgrade. Could a rolling upgrade leave one share group with different isolation levels on different partitions, since each broker applies its own default? Would tying the change to the share.version feature make sense here? Thanks, Lucas On Thu, Nov 12, 2026 at 10:15 PM Andrew Schofield via dev <[email protected]> wrote: > > Hi, > I would like to start discussion on a new KIP to change the default > isolation level for consumers from read-uncommitted to read-committed > in Apache Kafka 5.0. > > Here's the link to the KIP: > https://urldefense.com/v3/__https://cwiki.apache.org/confluence/x/cAeWGw__;!!Ayb5sqE7!uvkRuld09Q6dbSYh3Imw_5dkUpGfLlJBxN_JwTG_D5xB3M4vgTB29tHMEsMe0wbASYLagQPBHqY90sSbh0Izaw$ > > Thanks, > Andrew
