Alieh Saeedi created KAFKA-18126:
------------------------------------

             Summary: Refactoring to split the GroupMetadataManager in AK
                 Key: KAFKA-18126
                 URL: https://issues.apache.org/jira/browse/KAFKA-18126
             Project: Kafka
          Issue Type: Improvement
            Reporter: Alieh Saeedi


With classic groups, consumer groups, share groups and streams groups, there is 
too much logic in a single class in the new group coordinator, which is the 
{{{}GroupMetadataManager{}}}. Even now, before queues are fully implemented and 
before streams groups are added, the unit test class is 14k LOC.

We aim to refactor the class to (at least) split the RPC handling by group type 
- so one class for classic RPCs + helpers, one class for KIP-848 RPCs + 
helpers, one class for share groups and one for streams groups.

We’d still need a common class, since the ID space for groups is shared. One 
idea would be to have a GroupStore which just keeps the metadata for all 
groups, whereas all the RPC handling code is moved to specific classes by 
group, which access the GroupStore.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to