Kafka clients need to be able to differentiate the different brokers, and
have explicit control which broker to connect to.
Why? Each partition resides in a specific broker, and the client needs to
connect to the partition leader to perform read & writes, if they are all
under the same virtual ip,
Honestly I didnt get this question.
Please elaborate.
On Sun, 4 Jul 2021 at 5:34 PM, M. Manna wrote:
> Hello,
>
> Is it currently possible to use a single endpoint for advertised.listeners,
> which is in front of all my brokers? the flow for example
>
> broker1-->| V
> broker2--
h exception backdoor in
>>> > > zookeeper.properties when
>>> > > zookeeper.main_connection_despite_sasl_failure="yes"
>>> > >
>>> > >
>>> > > catch (SaslException e) {
>>> > > LOG.warn("Client f
e);
>> > > if ((System.getProperty("zookeeper.maintain_connection_
>> > despite_sasl_failure")
>> > > != null)
>> > > &&
>> > > (System.getProperty("zookeeper.maintain_connection_
>> > > despi
ient connection despite SASL
> authentication
> > > failure.");
> > > } else {
> > > LOG.warn("Closing client connection due to SASL authentication
> > > failure.");
> > > cnxn.close();
> > >..
> > > }
> &g
From: Joe Hammerman
Sent: Tuesday, April 3, 2018 10:40 PM
To: users@kafka.apache.org
Subject: Re: advertised.listeners
Hi all,
Is it possible to run mixed mode with PLAINTEXT and SSL with no SASL?
MG>setup SSL on kafka
https://github.com/edenhill/librdka
;yes"))) {
> > LOG.warn("Maintaining client connection despite SASL authentication
> > failure.");
> > } else {
> > LOG.warn("Closing client connection due to SASL authentication
> > failure.");
> > cnxn.close();
>
} else {
> LOG.warn("Closing client connection due to SASL authentication
> failure.");
> cnxn.close();
>..
> }
>
>
> does this conform to your findings?
>
> M
> __
>
>
>
>
t;);
} else {
LOG.warn("Closing client connection due to SASL authentication failure.");
cnxn.close();
..
}
does this conform to your findings?
M
__
From: Darshan
Sent: Tuesday, April 3, 2018 6
> Sent: Tuesday, April 3, 2018 5:45 PM
> To: rajinisiva...@gmail.com
> Cc: users@kafka.apache.org
> Subject: Re: advertised.listeners
>
> Hi Rajini
>
> The above configuration that you mentioned a while back helped me sort the
> issue of listeners and I was also able t
__
From: Darshan
Sent: Tuesday, April 3, 2018 5:45 PM
To: rajinisiva...@gmail.com
Cc: users@kafka.apache.org
Subject: Re: advertised.listeners
Hi Rajini
The above configuration that you mentioned a while back helped me sort the
issue of listeners and I
Hi Rajini
The above configuration that you mentioned a while back helped me sort the
issue of listeners and I was also able to run Kafka 0.10.2.1 with SSL and
ACLs as well from one of your other posts.
I wanted to ask you if it is possible to run Kafka in a mixed security
mode? i.e. external prod
Thanks, Rajini and Raghav. Let me try this. This is helpful.
On Wed, May 31, 2017 at 11:31 AM, Rajini Sivaram
wrote:
> If you want to use different interfaces with the same security protocol,
> you can specify listener names. You can then also configure different
> security properties for intern
If you want to use different interfaces with the same security protocol,
you can specify listener names. You can then also configure different
security properties for internal/external if you need.
listeners=INTERNAL://1.x.x.x:9092,EXTERNAL://172.x.x.x:9093
advertised.listeners=INTERNAL://1.x.x.x
Hello Darshan
Have you tried SSL://0.0.0.0:9093 ?
Rajani had suggested something similar to me a week back while I was trying
to get a ACL based setup.
Thanks.
On Wed, May 31, 2017 at 8:58 AM, Darshan
wrote:
> Hi
>
> Our Kafka broker has two IPs on two different interfaces.
>
> eth0 has 172.x
15 matches
Mail list logo
