gt; >
> > IBM Message Hub
> >
> > IBM UK Ltd, Hursley Park, SO21 2JN
> >
> >
> >
> > From: Eno Thereska
> > To: dev@kafka.apache.org
> > Date: 18/09/2018 10:24
> > Subject:Re: [DISCUSS] KIP-302 - Enable Kafka clients to use
all
>
; IBM Message Hub
> >
> > IBM UK Ltd, Hursley Park, SO21 2JN
> >
> >
> >
> > From: Eno Thereska
> > To: dev@kafka.apache.org
> > Date: 18/09/2018 10:24
> > Subject:Re: [DISCUSS] KIP-302 - Enable Kafka clients to use all
> > DNS reso
o Comar
>
> IBM Message Hub
>
> IBM UK Ltd, Hursley Park, SO21 2JN
>
>
>
> From: Eno Thereska
> To: dev@kafka.apache.org
> Date: 18/09/2018 10:24
> Subject: Re: [DISCUSS] KIP-302 - Enable Kafka clients to use all
> DNS resolved IP addresses
>
&g
:Re: [DISCUSS] KIP-302 - Enable Kafka clients to use all
DNS resolved IP addresses
Hi folks,
Could you expand the motivation a bit? When would it make sense to use an
LB in front of Kafka brokers? A client needs to access each broker
directly
to consume the data in that broker
avy but this gives users the ability to
> pick
> > > and choose.
> > > > I didn't include a setting to mix hostnames and canonical hostnames
> as
> > > I'm not sure there would be a valid use case.
> > > >
> > > > Alternativel
; > always work, across security protocols.
> > >>
> > >> A solution might be to expose to users the choice of using hostname or
> > canonical host name on both sides.
> > >> Say having one setting that collapses functionalities from both KIPs
>
ormed, using getCanonicalHostName() or
> not.
> >>
> >> Maybe that gives less flexibility as users wouldn't be able to decide
> to only perform DNS lookup on bootstrap.servers or on advertised listeners.
> >> But this would ensure consistency so that a user can decide to u
- dns.lookup.behaviour : bootstrap.servers, advertised.listeners, both
>
> Thoughts ?
>
> Jonathan Skrzypek
>
>
> -Original Message-----
> From: Edoardo Comar [mailto:edoco...@gmail.com]
> Sent: 17 May 2018 23:50
> To: dev@kafka.apache.org
> Subject: Re: [DISCUSS]
, advertised.listeners, both
Thoughts ?
Jonathan Skrzypek
-Original Message-
From: Edoardo Comar [mailto:edoco...@gmail.com]
Sent: 17 May 2018 23:50
To: dev@kafka.apache.org
Subject: Re: [DISCUSS] KIP-302 - Enable Kafka clients to use all DNS resolved
IP addresses
Hi Jonathan
>
>>>> > 2) Advertised listeners
>>>> >
>>>> > a) No lookup
>>>> > b) Use all DNS entries with host name
>>>> > c) Use all DNS entries with canonical host name
>>>> >
>>>> > The combina
nonicalHostName() ?
>
> Jonathan Skrzypek
>
> -Original Message-
> From: Edoardo Comar [mailto:edoco...@gmail.com]
> Sent: 16 May 2018 17:03
> To: dev@kafka.apache.org
> Subject: Re: [DISCUSS] KIP-302 - Enable Kafka clients to use all DNS resolved
> IP addresses
>
&
gt; Jonathan Skrzypek
>
> -Original Message-
> From: Edoardo Comar [mailto:edoco...@gmail.com]
> Sent: 16 May 2018 17:03
> To: dev@kafka.apache.org
> Subject: Re: [DISCUSS] KIP-302 - Enable Kafka clients to use all DNS resolved
> IP addresses
>
> Hi Rajini,
>
[mailto:edoco...@gmail.com]
Sent: 16 May 2018 17:03
To: dev@kafka.apache.org
Subject: Re: [DISCUSS] KIP-302 - Enable Kafka clients to use all DNS resolved
IP addresses
Hi Rajini,
In your example KIP-302 would attempt to connect to the first address
returned, let's say
www.apache.org/195.154.151.36
s kind of sounds related to the environment you're running to me.
>> >> What is the rationale behind using the advertised listeners to do your
>> >> load balancing advertisement rather than a top level alias that has
>> >> everything ?
>> >>
>> >
to do your
> >> load balancing advertisement rather than a top level alias that has
> >> everything ?
> >>
> >> It sounds like in your case there is a mismatch between
> bootstrap.servers
> >> and advertised.listeners, and you want advertised.listeners
urned by the broker.
>> So the extra parameter doesn't only have to do with DNS but it's also
>> appending from the broker, maybe the parameter name should reflect this ?
>>
>> Jonathan Skrzypek
>>
>>
>> -Original Message-
>> From: Skrzypek,
doardo
> Jonathan Skrzypek
>
>
> -Original Message-
> From: Skrzypek, Jonathan [Tech]
> Sent: 14 May 2018 14:46
> To: dev@kafka.apache.org
> Subject: RE: [DISCUSS] KIP-302 - Enable Kafka clients to use all DNS resolved
> IP addresses
>
> Hi,
>
> I see you n
from the broker, maybe the parameter name should reflect this ?
>
> Jonathan Skrzypek
>
>
> -Original Message-
> From: Skrzypek, Jonathan [Tech]
> Sent: 14 May 2018 14:46
> To: dev@kafka.apache.org
> Subject: RE: [DISCUSS] KIP-302 - Enable Kafka clients to use all DNS
> res
but it's also appending
from the broker, maybe the parameter name should reflect this ?
Jonathan Skrzypek
-Original Message-
From: Skrzypek, Jonathan [Tech]
Sent: 14 May 2018 14:46
To: dev@kafka.apache.org
Subject: RE: [DISCUSS] KIP-302 - Enable Kafka clients to use all DNS resolved
IP
Hi,
I see you noted the similarities with KIP-235.
But KIP-235 might also solve what this KIP is trying to achieve.
When parsing bootstrap.servers, KIP-235 has the client add all underlying
hostnames and IPs.
And this happens before hitting the NetworkClient.
So to me the client will try every
20 matches
Mail list logo
