Member since
04-23-2018
3
Posts
4
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
22041 | 05-03-2018 07:06 AM |
05-03-2018
07:06 AM
1 Kudo
The solution to this was to create a config group for each broker and add a host-specific `advertised.listeners` property in the Custom kafka-broker section. This has been beautifully documented in this YouTube video: https://www.youtube.com/watch?v=bRKw5y_tx5E
... View more
03-29-2018
02:20 PM
3 Kudos
I have an HDP cluster that's running two networks: a 10.x network for external traffic and a 192.x network for internal traffic. Kafka is listening on the the 192.x network, and I have a client application running that needs to write to Kafka that's running on the 10.x network. I need Kafka to listen on both networks. The `listeners` property is currently set to `PLAINTEXT://localhost:6667`. I stumbled across a blog that says we can replace localhost with an actual IP address, e.g. `PLAINTEXT://10.x.x.x:6667,PLAINTEXT://192.x.x.x:6667`. If I set this property in Ambari, this property gets pushed to all the brokers. Obviously, the IP addresses will differ from host to host. Is there a way for Ambari to have host-specific properties? Or is there another way to configure Kafka, via Ambari, where it's listening on multiple NICs?
... View more
Labels:
- Labels:
-
Apache Ambari
-
Apache Kafka