[
https://issues.apache.org/jira/browse/KAFKA-7824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16799914#comment-16799914
]
Stanislav Kozlovski commented on KAFKA-7824:
--------------------------------------------
This was merged, right? Could we update the status on the KIP?
> Require member.id for initial join group request
> ------------------------------------------------
>
> Key: KAFKA-7824
> URL: https://issues.apache.org/jira/browse/KAFKA-7824
> Project: Kafka
> Issue Type: Sub-task
> Components: consumer
> Reporter: Boyang Chen
> Assignee: Boyang Chen
> Priority: Major
> Fix For: 2.2.0
>
>
> For request with unknown member id, broker will blindly accept the new join
> group request, store the member metadata and return a UUID to consumer. The
> edge case is that if initial join group request keeps failing due to
> connection timeout, or the consumer keeps restarting, or the
> max.poll.interval.ms configured on client is set to infinite (no rebalance
> timeout kicking in to clean up the member metadata map), there will be
> accumulated MemberMetadata info within group metadata cache which will
> eventually burst broker memory. The detection and fencing of invalid join
> group request is crucial for broker stability.
>
> The proposed solution is to require one more bounce for the consumer to use a
> valid member.id to join the group. Details in this
> [KIP|https://cwiki.apache.org/confluence/display/KAFKA/KIP-394%3A+Require+member.id+for+initial+join+group+request]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
