Kafka Advertised Host Setting

The video tutorial explains the importance of advertised listeners in Kafka setups. It covers how Kafka brokers use public and private IPs, and the role of advertised hostnames. The tutorial discusses the use of localhost for development and the challenges of connecting from external networks. It also addresses the use of public IPs and the complications that arise when IPs change in cloud environments. Finally, it provides guidelines for setting advertised listeners based on network configurations.

What is the primary role of advertised listeners in Kafka?

• To ensure clients connect using the correct host name

• To manage data replication across brokers

• To encrypt data in transit

• To balance load among Kafka brokers

Why might a Kafka client fail to connect when using localhost?

• The client is on a different private network

• The advertised listener is set to a public IP

• The broker is not running

• The client is using an outdated Kafka version

What is a potential issue when using a public IP for Kafka connections in the cloud?

• The public IP cannot be used with multiple brokers

• The public IP requires additional security settings

• The public IP is always slower

• The public IP might change after a reboot

How should advertised listeners be set if clients are on the same private network as the Kafka cluster?

• Use the internal private IP or host name

• Use the external public IP

• Use a random IP address

• Use localhost

What should be done if clients are on a public network?

• Use localhost as the advertised listener

• Set the advertised listener to the external public DNS host name

• Disable advertised listeners

• Set the advertised listener to the internal private IP