Skip to content

when using listener_security_protocol_map, efak could not find the real host and port. #625

@charlielin

Description

@charlielin

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions