The advertised.listeners property would not help you to map a different port. If you need to talk to brokers at a different port you should also set the listeners property accordingly. Say if you want the broker to listen at port 10092 as an example, the server.properties needs to contain these 2 lines:
listeners=PLAINTEXT://:10092 advertised.listeners=PLAINTEXT://<my_host>:10092 Since you mentioned containers, are you using the Confluent's docker containers? If yes, the above configs should be taken care of (via an environment variable). Hope this helps. On Tue, Nov 29, 2016 at 9:56 AM, Aki Yoshida <elak...@gmail.com> wrote: > I have a question regarding how to use advertised.listeners to expose > a different port to the outside of the container where the broker is > running. > > When using advertised.listeners to register a different port as the > actual broker port, do we need a port forwarding from this configured > port to the actual broker port within the container so that the broker > itself can also find itself, right? > > thanks. > regards, aki > -- Kaufman Ng Solutions Architect | Confluent +1 646 961 8063 | @kaufmanng www.confluent.io
