control.plane.listener.name — Kafka Broker Configuration
Name of listener used for communication between controller and brokers. A broker will use the control.
Description
Name of listener used for communication between controller and brokers. A broker will use the control.plane.listener.name to locate the endpoint in listeners list, to listen for connections from the controller. For example, if a broker's config is:listeners = INTERNAL://192.1.1.8:9092, EXTERNAL://10.1.1.5:9093, CONTROLLER://192.1.1.8:9094listener.security.protocol.map = INTERNAL:PLAINTEXT, EXTERNAL:SSL, CONTROLLER:SSLcontrol.plane.listener.name = CONTROLLEROn startup, the broker will start listening on "192.1.1.8:9094" with security protocol "SSL".On the controller side, when it discovers a broker's published endpoints through ZooKeeper, it will use the control.plane.listener.name to find the endpoint, which it will use to establish connection to the broker.For example, if the broker's published endpoints on ZooKeeper are: "endpoints" : ["INTERNAL://broker1.example.com:9092","EXTERNAL://broker1.example.com:9093","CONTROLLER://broker1.example.com:9094"] and the controller's config is:listener.security.protocol.map = INTERNAL:PLAINTEXT, EXTERNAL:SSL, CONTROLLER:SSLcontrol.plane.listener.name = CONTROLLERthen the controller will use "broker1.example.com:9094" with security protocol "SSL" to connect to the broker.If not explicitly configured, the default value will be null and there will be no dedicated endpoints for controller connections.If explicitly configured, the value cannot be the same as the value of inter.broker.listener.name.
Default Values by Kafka Version
| Kafka Version | Default Value |
|---|---|
| 2.2 | null |
| 2.3 | null |
| 2.4 | null |
| 2.5 | null |
| 2.6 | null |
| 2.7 | null |
| 2.8 | null |
| 3.0 | null |
| 3.1 | null |
| 3.2 | null |
| 3.3 | null |
| 3.4 | null |
| 3.5 | null |
| 3.6 | null |
| 3.7 | null |
| 3.8 | null |
| 3.9 | null |