DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
Note : There is another config share.coordinator.cold.partition.snapshot.interval.ms (default 5 mins) which forces snapshotting on a timely basis, but only for share partitions with no updates. So the old log recs of the idle groups would be eligible for cleanup.
Public Interfaces
- Updated broker-level config: `shareshare.coordinator.snapshot.update.records.per.snapshot`
...
- snapshot
| Code Block |
|---|
|---|---| | **Name** | `share.coordinator.snapshot.update.records.per.snapshot` (unchanged) | |
...
| **Type** | `INT` (unchanged) | |
...
| **Default** | `500` (unchanged) | |
...
| **Validator** | `between( |
...
200, |
...
1000)` — proposed initial |
...
bounds. A follow-up benchmarking ticket (filed as a sub-task of KAFKA-20070, see *Test Plan*) may |
...
revise either the floor or the ceiling before vote based on empirical data. | | **Importance** | `MEDIUM` (unchanged) | |
...
| **Doc** | "The |
...
number of update records the share coordinator writes between snapshot records, applied as a ceiling across all share groups on this broker. Must be in `[200, 1000]`. May be overridden per group via the `share.snapshot.update.records.per.snapshot` group config; per-group values are clamped to this ceiling." | |
The lower bound of `0` is preserved for backwards compatibility. The semantics of `0` ("snapshot every write") are documented but otherwise unchanged. Disallowing `0` is explicitly out of scope (see *Rejected Alternatives*).
...