hi Andrew Thanks for the KIP. I have a few questions regrading the configuration behaviour:
chia_00: Dynamic Update Behavior Are these new group-level configuration dynamic? Specifically, if we alter share.delivery.count.limit or share.partition.max.record.locks at runtime, will the changes take effect immediately for active share group? chia_01: Configuration Validation on Broker Restart How does the broker handle existing group configuration that fall out of bounds after a broker restart? For example, suppose a group has share.partition.max.record.locks set to 100 (which is valid at the time). If the broker is later restarted with a stricter limit of group.share.max.partition.max.record.locks = 50, how will the group loaded handle this conflict? Best, Chia-Ping On 2025/11/24 21:15:48 Andrew Schofield wrote: > Hi, > I’d like to start the discussion on a small KIP which adds some > configurations for share groups which were previously only available as > broker configurations. > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1240%3A+Additional+group+configurations+for+share+groups > > Thanks, > Andrew >
