On Thu, Aug 12, 2021 at 11:44 AM c...@uweeisele.eu
wrote:
> this is a bug which I also have already noticed. This has already been
> fixed (https://github.com/apache/kafka/pull/10935) and it will be
> released with Kafka 3.0.0 (
> https://issues.apache.org/jira/browse/KAFKA-13003).
Thank you fo
on GitHub.
github.com
I hope this helps.
Best Regards,
Uwe
Von: Mike Pontillo
Gesendet: Donnerstag, 12. August 2021 03:53
An: users@kafka.apache.org
Betreff: Kafka 2.8.0 "KRaft" - advertised.listeners port mismatch?
Greetings,
I'm trying to c
rs=CONTROLLER://127.0.0.1:9093,INTERNAL://127.0.0.1:9094,EXTERNAL://
0.0.0.0:9092
inter.broker.listener.name=INTERNAL
advertised.listeners=INTERNAL://127.0.0.1:9094,EXTERNAL://127.0.0.1:55032
controller.listener.names=CONTROLLER
listener.security.protocol.map=CONTROLLER:PLAINTEXT,INTERNAL:PLAINTEXT,EX
t;
On Mon, Jul 5, 2021 at 12:04 AM sunil chaudhari
wrote:
> 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.list
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--
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-->| I
broker3-->| P
I was under the impression that I can reach any broker I wanted (assuming
that
>> (org.apache.kafka.clients.NetworkClient)*
>>
>>
>>
>>
>>
>>
>>
>> *server.properties for our Kafka-1,2,3. They are identical
>> except broker.id <http://broker.id/> and super.users properties.# ID and
>> basic topic creationbroke
t;
>
>
>
>
>
>
> *server.properties for our Kafka-1,2,3. They are identical
> except broker.id <http://broker.id/> and super.users properties.# ID and
> basic topic creationbroker.id
> <http://broker.id/>=1auto.create.topics.enable=truedelete.topic.enable=tru
190.176:9093
<http://172.21.190.176:9093/>advertised.listeners=INTERNAL://1.1.1.165:9092
<http://1.1.1.165:9092/>,EXTERNAL://172.21.190.176:9093
<http://172.21.190.176:9093/>listener.security.protocol.map=INTERNAL:PLAINTEXT,EXTERNAL:SSLinter.broker.listener.name
<http://inter.b
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
erties.*
# ID and basic topic creation
broker.id=1
auto.create.topics.enable=true
delete.topic.enable=true
# LISTERN Settings
listeners=INTERNAL://1.1.1.165:9092,EXTERNAL://172.21.190.176:9093
advertised.listeners=INTERNAL://1.1.1.165:9092,EXTERNAL://
172.21.190.176:9093
listener.security.protoc
rties 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:9092,EXTERNAL://172.x.x.x:9093
>
> listener.security.protocol.map=INTERNAL:SSL,EXTERNAL:SSL
>
> inter.broker.listener.name=INTERNAL
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
t; eth0 has 172.x.x.x for external leg
> eth1 has 1.x.x.x for internal leg
>
>
> Kafka Producer is on 172.x.x.x subnet, and Kafka Consumer is on 1.x.x.x
> subnet.
>
> If we use advertised.listeners=SSL://172.x.x.x:9093, then Producer can
> producer the message, but Consum
Hi
Our Kafka broker has two IPs on two different interfaces.
eth0 has 172.x.x.x for external leg
eth1 has 1.x.x.x for internal leg
Kafka Producer is on 172.x.x.x subnet, and Kafka Consumer is on 1.x.x.x
subnet.
If we use advertised.listeners=SSL://172.x.x.x:9093, then Producer can
producer
Hi Kaufman,
I wasn't thinking of using listeners to switch the running port
itself. That makes it very simple. It was stupid of me.
thank you.
regards, aki
2016-11-30 17:43 GMT+01:00 Kaufman Ng :
> The advertised.listeners property would not help you to map a different
> port. If
The advertised.listeners property would not help you to map a different
port. If you need to talk to brokers at a different port you should also
set the listeners property accordingly. Say if you want the broker to
listen at port 10092 as an example, the server.properties needs to contain
these
I have a question regarding how to use advertised.listeners to expose
a different port to the outside of the container where the broker is
running.
When using advertised.listeners to register a different port as the
actual broker port, do we need a port forwarding from this configured
port to the
23 matches
Mail list logo
