Hi Chia-Ping,
Thanks for the feedback. The original configuration name was potentially ambiguous; it has therefore been renamed to `group.coordinator.append.max.buffer.size`. chia_00: Update the vaild values of group.coordinator.append.max.buffer.size to be less than message.max.bytes. chia_01: Yes, I agree. Make this config to be updated dynamically. chia_02: I agree with you. Since the buffer behavior is a soft limit, this change should not impact any existing functionality or require special compatibility measures. Best, Lan At 2025-08-18 00:54:15, "Chia-Ping Tsai" <chia7...@gmail.com> wrote: >hi Lan > >chia_00: > >The `group.coordinator.append.max.bytes` must be smaller than the max >message size; Otherwise, it could generate an invalid record > >chia_01: > >Since the max message size is a dynamic configuration, should we also make >`group.coordinator.append.max.bytes` dynamic? > >chia_02: > >Is compatibility necessary? The max buffer of the new coordinator is >currently transparent to users, so I don't think there are any users >explicitly setting the max message size to control the buffer used by the >new coordinator > >Best, >Chia-Ping > > >Lan Ding <isdin...@163.com> 於 2025年8月18日 週一 上午12:37寫道： > >> Hello everyone, I'd like to discuss a KIP regarding introducing a new >> configuration, >> group.coordinator.append.max.bytes Thank you! KIP link: >> https://cwiki.apache.org/confluence/x/hA5JFg Best, Lan Ding
