This page is meant as a template for writing a KIP. To create a KIP choose Tools->Copy on this page and modify with your content and replace the heading with the next KIP number and a description of your issue. Replace anything in italics with your own description.
Current state: Under Discussion
Discussion thread:
JIRA:
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
KIP-932 introduced Share Groups to Kafka, enabling cooperative consumption with queueing semantics. Currently, the behavior of share groups is governed by several broker-level configurations. While some configurations can be dynamically updated, some limits are currently static and applied globally to all share groups on a broker. This KIP aims to address this limitation by enabling dynamic, group-level configuration for these essential parameters.
The following table summarizes the configuration parameters for Share Groups. It indicates which parameters are currently supported as dynamic group configurations and which are introduced by this KIP.
| Broker Configuration Key | Dynamic Group Configuration Key | Description | Group Level Dynamic Config Support |
|---|---|---|---|
| share.session.timeout.ms | Yes | ||
| share.heartbeat.interval.ms | |||
| share.record.lock.duration.ms | |||
| share.partition.max.record.locks | |||
| share.delivery.count.limit | |||
| share.max.size |
We propose adding the following configurations to the list of supported dynamic configs for groups
Describe in few sentences how the KIP will be tested. We are mostly interested in system tests (since unit-tests are specific to implementation details). How will we know that the implementation works as expected? How will we know nothing broke?
If there are alternative ways of accomplishing the same thing, what were they? The purpose of this section is to motivate why the design is the way it is and not some other way.