Hi, Apologies for the delayed reply. Sushant, thanks for the reply. Just to flag the KIP has switched to bytes-based control (pls see below), which supersedes most of the records-based tuning discussion.
Chia, thank you for the suggestions. Both the points are now in the KIP: - chia_00: broker floor stays at 0 (no compatibility break) - chia_01: bytes-based control adopted, matching metadata.log.max.record.bytes.between.snapshots, default 20 MB. Records-based config will be marked as deprecated. Updated KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-1349%3A+Bytes-based+configurable+snapshot+frequency+for+share+groups Please take a look again. Thanks, Murali On Thu, Jun 11, 2026 at 5:20 AM Chia-Ping Tsai <[email protected]> wrote: > hi > > chia_00: Changing the lower bound of the existing config is a > compatibility issue. If we want to avoid heavy snapshots, we can set the > lower bound of the new group-level configuration to 200 by default. Also, > the broker-level constraint should be changed to 0-1000, which won’t bring > compatibility issues > > chia_01: Have you considered using bytes instead of records as the > controlled unit? > > > On 2026/05/22 19:30:38 Muralidhar Basani via dev wrote: > > Hi all, > > > > I would like to start a discussion on KIP-1349, which allows configurable > > snapshot frequency of share groups. > > > > KIP : > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1349%3A+Configurable+snapshot+frequency+for+share+groups > > > > Thanks, > > Murali > > >
