Status

Current state: "DraftUnder Discussion"

Discussion thread: here 

JIRA: here 

Motivation

Kafka has share groups. As multiple consumers in the same share group can consume from the same partition concurrently, records get individually acknowledged and broker tracks per record state(delivered, acked, in-flight etc).

...

Compatibility, Deprecation, and Migration Plan

Behavior break

 floor  Floor raised from `0` to `200` '0' to '200' -- any cluster currently configured with share.coordinator.snapshot.update.records.per.snapshot set to a value below 200 will fail broker startup config validation after upgrade. Clusters using the default 500 or any value in [200, 500] are unaffected. Clusters that previously set the value to anything between 501 and 1000 — not currently possible since the existing range is [0, 500] — would also pass validation in the new range; this case does not apply on upgrade.

...

• Values 0–199: fail to start after upgrade (operator must fix)
• Values 200–500: unaffected
•  Values 501+: don't exist (can't happen)

Behavioral compatibility

(ceiling raise): Ceiling raise -- raising the ceiling from 500 to 1000 is non-breaking on its own. Brokers that retain their existing setting in [200, 500] behave identically to today. Operators can opt into the higher range explicitly.

...