Table of Contents |
---|
Status
Current state: Under Discussion
...
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
Motivation
Today group coordinator will take in unlimited number of join group requests into the membership metadata. There is a potential risk described in
Jira | ||||||
---|---|---|---|---|---|---|
|
Public Interfaces
We propose to add a new configuration into KafkaConfig.scala, and its behavior will affect the following coordinator APIs:
...
where we shall enforce the group size capping rules upon requests.
Proposed Changes
We shall add a config called group.max.size on the coordinator side.
...
- This is backward compatible change.
Rejected Alternatives
Some discussion here proposed other approaches like enforcing memory limit or changing initial rebalance delay. We believe that those approaches are "either not strict or not intuitive" (Quote from Stanislav), compared with group size cap which is very easy to understand and config by end user in the customized manner.