I think setting these is not a good idea b/c only apply to the specific
client where you've setup the tunnel. Other clients cannot use these
settings
advertised.host.name=localhost
advertised.port=19092
You probably need to figure out another way such as
1) Setting up a local mapping on your
Hi, all.
Sorry for my late reply.
I tried advertised.host.name/advertised.port.
But producer failed fetching metadata from kafka broker.
Configuration is below.
- Kafka cluster in DataCenter(each machine has Grobal IP Address).
Firewall allows only ssh port(22).
ex) 192.168.100.100
- Kafka
Any error in the broker, controller and state change log?
Thanks,
Jun
On Tue, Apr 8, 2014 at 3:08 PM, Sotaro Kimura rfbrin...@gmail.com wrote:
Hi, all.
Sorry for my late reply.
I tried advertised.host.name/advertised.port.
But producer failed fetching metadata from kafka broker.
Hi, all.
I'm trying Log produce to Remote Kafka Cluster over SSH Tunneling.
Configuration is below.
- Kafka cluster in DataCenter(each machine has Grobal IP Address).
Firewall allows only ssh port(22).
ex) 192.168.100.100
- Kafka producer exists out of DataCenter.
ex) 172.16.0.100
I tried
With 0.8.1 update these two properties in the server.properties config of
the broker to be 172.16.0.100 and 19092 respectively
# Hostname the broker will advertise to producers and consumers. If not
set, it uses the
# value for host.name if configured. Otherwise, it will use the value
returned
