You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Boyang Chen (JIRA)" <ji...@apache.org> on 2019/01/15 17:44:00 UTC

[jira] [Created] (KAFKA-7824) Require member.id for initial join group request

Boyang Chen created KAFKA-7824:
----------------------------------

             Summary: Require member.id for initial join group request
                 Key: KAFKA-7824
                 URL: https://issues.apache.org/jira/browse/KAFKA-7824
             Project: Kafka
          Issue Type: Improvement
          Components: consumer
            Reporter: Boyang Chen
            Assignee: Boyang Chen


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)