2019 6:07 AM
To: dev
Subject: Re: [DISCUSS] KIP-394: Require member.id for initial join group request
Hi,
I'm late to the discussion, so apologies. One question, did we consider
having the client generate a member id in the first join group? This could
be random or known to be unique and would
Hi,
I'm late to the discussion, so apologies. One question, did we consider
having the client generate a member id in the first join group? This could
be random or known to be unique and would avoid a second join group request
in the common case. If we considered and rejected this option, it would
; > From: Boyang Chen
> > Sent: Saturday, December 1, 2018 10:53 AM
> > To: dev@kafka.apache.org
> > Subject: Re: [DISCUSS] KIP-394: Require member.id for initial join group
> > request
> >
> > Thanks Jason for the reply! Since the overall motivation and desig
__
> From: Boyang Chen
> Sent: Saturday, December 1, 2018 10:53 AM
> To: dev@kafka.apache.org
> Subject: Re: [DISCUSS] KIP-394: Require member.id for initial join group
> request
>
> Thanks Jason for the reply! Since the overall motivation and design is
&
Matthias J. Sax
Sent: Saturday, December 1, 2018 3:12 AM
To: dev@kafka.apache.org
Subject: Re: [DISCUSS] KIP-394: Require member.id for initial join group request
SGTM.
On 11/30/18 10:17 AM, Jason Gustafson wrote:
> Using the session expiration logic we already have seems like the simples
: dev@kafka.apache.org
Subject: Re: [DISCUSS] KIP-394: Require member.id for initial join group request
SGTM.
On 11/30/18 10:17 AM, Jason Gustafson wrote:
> Using the session expiration logic we already have seems like the simplest
> option (this is probably a one or two line change). The
>> From: Matthias J. Sax
>> Sent: Friday, November 30, 2018 10:26 AM
>> To: dev@kafka.apache.org
>> Subject: Re: [DISCUSS] KIP-394: Require member.id for initial join group
>> request
>>
>> Thanks! Makes sense.
>>
>> I missed that fact, that t
the broker metadata map.
> >
> > Does this sound clear to you?
> >
> > Best,
> > Boyang
> >
> > From: Stanislav Kozlovski
> > Sent: Wednesday, November 28, 2018 7:39 PM
> > To: dev@kafka.apache.org
> > Subject:
inion.
From: Matthias J. Sax
Sent: Friday, November 30, 2018 10:26 AM
To: dev@kafka.apache.org
Subject: Re: [DISCUSS] KIP-394: Require member.id for initial join group request
Thanks! Makes sense.
I missed that fact, that the `member.id` is added on the second
join
t; By then broker will include c2 within the broker metadata map.
>
> Does this sound clear to you?
>
> Best,
> Boyang
>
> From: Stanislav Kozlovski
> Sent: Wednesday, November 28, 2018 7:39 PM
> To: dev@kafka.apache.org
> Subject: Re
safe to deprecate `group.initial.rebalance.delay.ms`.
> Also one round trip
> > shouldn't increase the latency too much IMO.
> >
> > Best,
> > Boyang
> >
> > From: Stanislav Kozlovski
> > Sent: Wednesday, November 28,
ebalance.delay.ms`.
> Also one round trip
> > shouldn't increase the latency too much IMO.
> >
> > Best,
> > Boyang
> >
> > From: Stanislav Kozlovski
> > Sent: Wednesday, November 28, 2018 2:32 AM
> > To: dev@k
e `group.initial.rebalance.delay.ms`. Also
> one round trip
> shouldn't increase the latency too much IMO.
>
> Best,
> Boyang
> ____________________
> From: Stanislav Kozlovski
> Sent: Wednesday, November 28, 2018 2:32 AM
> To: dev@kafka.apache.org
> Subject: Re: [DISCUSS] KIP-394
ecate `group.initial.rebalance.delay.ms`. Also
one round trip
shouldn't increase the latency too much IMO.
Best,
Boyang
From: Stanislav Kozlovski
Sent: Wednesday, November 28, 2018 2:32 AM
To: dev@kafka.apache.org
Subject: Re: [DISCUSS] KIP-394: Require member
Hi Boyang,
The KIP looks very good.
One small question I have is now that we have one and a half round-trips
needed to join in a rebalance (1 full RT addition), is it worth it to
consider increasing the default value of `group.initial.rebalance.delay.ms`?
Best,
Stanislav
On Tue, Nov 27, 2018 at
Hi Boyang,
Thanks for the KIP. Looks good overall. I think we will need to bump the
version of the JoinGroup protocol in order to indicate compatibility with
the new behavior. The coordinator needs to know when it is safe to assume
the client will handle the error code.
Also, I was wondering if w
Hey friends,
I would like to start a discussion thread for KIP-394 which is trying to
mitigate broker cache bursting issue due to anonymous join group requests:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-394%3A+Require+member.id+for+initial+join+group+request
Thanks!
Boyang
17 matches
Mail list logo
