Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
-
None
Description
Currently the broker allows startup with an incompatible inter-broker security setting. For example, if the only listening port is enabled for SSL and no "security.inter.broker.protocol" is set, then the broker will still attempt to use the default PLAINTEXT protocol. When the broker then attempts to send LeaderAndIsr and other requests over plain text to itself (which can happen if it becomes the controller), it will silently catch the error since it cannot find the corresponding endpoint. It would be better to raise a configuration error in this case since there's no way that the broker can work correctly when it becomes controller.
Attachments
Issue Links
- duplicates
-
KAFKA-3194 Validate security.inter.broker.protocol against the advertised.listeners protocols
- Resolved