lhotari commented on issue #614: URL: https://github.com/apache/pulsar-helm-chart/issues/614#issuecomment-4475968410
regarding advertisedListeners, it's designed in a way where there's a separate internal and external listener. The internal listener is intended to be used within a Pulsar cluster and the addressed shouldn't be changed to LB addresses. Some docs at https://pulsar.apache.org/docs/4.2.x/concepts-multiple-advertised-listeners/#advertised-listeners-configuration. The docs might be incomplete since there's no tests in apache/pulsar or apache/pulsar-helm-chart to validate this. It is necessary to explicitly pass the listener name ("external") in the client configuration unless the external listener binds to a separate port in the brokers. In addition, it's necessary to use binary protocol for serviceUrl in the Pulsar client due to some gaps in the implementation (open PR https://github.com/apache/pulsar/pull/22062). It could be a lot easier to make the configuration work by using Pulsar Proxy. Obviously that comes with a tradeoff. One useful optimization in Pulsar Proxy with multiple Proxy instances would be to return a Proxy instance address that is in the same availability zone or region as the broker is to reduce cross-AZ and cross-region traffic ([comment here](https://github.com/apache/pulsar/issues/23963#issuecomment-2655894604)). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
