Hi Goran,
Thanks for your reply. We've tried this and got interesting results.
First, we found out that there is a port forwarding between the client and
the server. So we put the local IP (192.168.x.x) into the 'listeners'
parameter, and the external IP (98.1.96.147) into the
'advertised.listene
Client connects to IP address defined by bootstrap.servers and gets metada
that contain IP address where kafka is available. That is configured in
server.properties:
# Hostname and port the broker will advertise to producers and consumers. If
not set, # it uses the value for "listeners" if conf
Hi Suresh,
Thanks for your quick response. All the configuration files, except for
the connect-standalone.properties are unmodified and use all the default
parameters. Attaching them anyway just in case.
This setup works perfectly on my laptop with VirtualBox (ZooKeeper and the
broker on VM, the
Hi Val,
Could you share the server.properties and zookeeper.properties?
Thanks
C Suresh
On Tuesday, April 28, 2020, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Greetings to the Kafka Community!
>
> I'm a newbie in Kafka and only recently went beyond a local installation
> des
Greetings to the Kafka Community!
I'm a newbie in Kafka and only recently went beyond a local installation
described in the Quickstart. I have faced a weird issue that I can't
explain.
I want to deploy on two machines:
- Machine #1 runs ZooKeeper and a single Kafka broker. I use default
configura
