We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
listener_security_protocol_map
When I using kafka config like this:
listeners=PUBLIC_SASL://0.0.0.0:5011,PUBLIC_PLAIN://0.0.0.0:5010 advertised.listeners=PUBLIC_SASL://192.168.181.2:5011,PUBLIC_PLAIN://192.168.181.2:5010 listener.security.protocol.map=PUBLIC_SASL:SASL_PLAINTEXT,PUBLIC_PLAIN:PLAINTEXT inter.broker.listener.name=PUBLIC_SASL
The broker info in zk list this:
{ "listener_security_protocol_map": { "PUBLIC_SASL": "SASL_PLAINTEXT", "PUBLIC_PLAIN": "PLAINTEXT" }, "endpoints": [ "PUBLIC_SASL://192.168.181.2:5011", "PUBLIC_PLAIN://192.168.181.2:5010" ], "jmx_port": -1, "features": { }, "host": "192.168.181.2", "timestamp": "1658485899402", "port": 5010, "version": 5 }
In this situation, efak could not find the real host and port, because none of the endpoints start with SASL_PLAINTEXT or SSL or PLAINTEXT.
SASL_PLAINTEXT
SSL
PLAINTEXT
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
When I using kafka config like this:
The broker info in zk list this:
In this situation, efak could not find the real host and port, because none of the endpoints start with
SASL_PLAINTEXT
orSSL
orPLAINTEXT
.The text was updated successfully, but these errors were encountered: