Thanks Hector! Yes, making the templated group "type" with extensible
handling logic is part of the motivation of this rebalance protocol.


Guozhang

On Thu, Jul 14, 2022 at 10:35 AM Hector Geraldino (BLOOMBERG/ 919 3RD A) <
hgerald...@bloomberg.net> wrote:

> Kudos David, Guozhang, and Jason for putting together such a great
> proposal.
>
> I don't want to hijack the discussion, just wanted to mention that it
> would be great if the final design is made extensible enough, so other use
> cases (like Kafka Connect, Schema Registry, etc.) can be added later on.
>
> I can see how the concept of different group "types" in the group
> coordinator can be leveraged to support such cases. On KIP-795, I wanted to
> add public APIs for the AbstractCoordinator with the intent of formalizing
> the use of the Group Membership Protocol for resource management use cases.
> I'll probably close this KIP and wait to see what comes out of this
> redesign of the protocol.
>
> Thanks
>
> -
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-795%3A+Add+public+APIs+for+AbstractCoordinator
>
> From: dev@kafka.apache.org At: 07/06/22 04:44:59 UTC-4:00To:
> dev@kafka.apache.org
> Subject: [DISCUSS] KIP-848: The Next Generation of the Consumer Rebalance
> Protocol
>
> Hi all,
>
> I would like to start a discussion thread on KIP-848: The Next
> Generation of the Consumer Rebalance Protocol. With this KIP, we aim
> to make the rebalance protocol (for consumers) more reliable, more
> scalable, easier to implement for clients, and easier to debug for
> operators.
>
> The KIP is here: https://cwiki.apache.org/confluence/x/HhD1D.
>
> Please take a look and let me know what you think.
>
> Best,
> David
>
> PS: I will be away from July 18th to August 8th. That gives you a bit
> of time to read and digest this long KIP.
>
>
>

-- 
-- Guozhang

Reply via email to