[jira] [Commented] (KAFKA-7641) Add `consumer.group.max.size` to cap consumer metadata size on broker

["Varun Gangawane (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-7641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17349600#comment-17349600 ] 

Varun Gangawane commented on KAFKA-7641:
----------------------------------------

That's a great explanation. Crystal clear. Thanks a lot for this Aran. In my case, all 200+ distinct remote servers (or you can say partners) are supposed to consume the same data, because they are independent of each other. So I take it as "No limit, keeping an eye on the network utilisation

-------------------------------------------

love to read [Onepunchman, Onepanman|https://onepunchmanmangaonline.net]

> Add `consumer.group.max.size` to cap consumer metadata size on broker
> ---------------------------------------------------------------------
>
>                 Key: KAFKA-7641
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7641
>             Project: Kafka
>          Issue Type: Improvement
>          Components: core
>            Reporter: Boyang Chen
>            Assignee: Stanislav Kozlovski
>            Priority: Major
>              Labels: kip
>             Fix For: 2.2.0
>
>
> In the JIRA discussion https://issues.apache.org/jira/browse/KAFKA-7610, Jason concluded an edge case of current consumer protocol which could cause memory burst on broker side:
> ```the case we observed in practice was caused by a consumer that was slow to rejoin the group after a rebalance had begun. At the same time, there were new members that were trying to join the group for the first time. The request timeout was significantly lower than the rebalance timeout, so the JoinGroup of the new members kept timing out. The timeout caused a retry and the group size eventually become quite large because we could not detect the fact that the new members were no longer there.```
> Since many disorganized join group requests are spamming the group metadata, we should define a cap on broker side to avoid one consumer group from growing too large. So far I feel it's appropriate to introduce this as a server config since most times this value is only dealing with error scenarios, client users shouldn't worry about this config.
> KIP-389: [https://cwiki.apache.org/confluence/display/KAFKA/KIP-389%3A+Introduce+a+configurable+consumer+group+size+limit]
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)