Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Operators must upgrade the controller/broker before relying on the per-group override.

Deprecation

None

MigrationNo

Required operator action before upgrade (only for clusters that explicitly set the broker config below 200):

1. Run kafka-configs.sh --bootstrap-server <broker> --describe --entity-type brokers --all and inspect the value of share.coordinator.snapshot.update.records.per.snapshot on each broker.

2. If any broker has the value set below 200 (most commonly `0`) either:
   - Remove the override so the broker falls back to the default of `500`, or
   - Raise the override to a value in `[200, 1000]` that matches the operator's intent.

3. Roll out the upgrade.

Operators who have never overridden the broker config (i.e., it is implicitly `500`) need no action user action required. Operators wanting the new ceiling must explicitly raise `share.coordinator.snapshot.update.records.per.snapshot`. Per-group overrides are opt-in via `kafka-configs.sh`.

Test Plan

### Benchmark workstream

...