lhotari opened a new pull request, #21894: URL: https://github.com/apache/pulsar/pull/21894
### Motivation There's currently a problem that the leader broker cannot be determined when the advertised address and advertised listeners are configured. The workaround to the problem is to properly configure an internal advertised listener which matches the advertised address. However, applying the workaround is brittle. The code base has had inconsistent ways for a unique identifier for a broker. In some cases, there's a dummy "http://"; prefix for the identifier even when the port is the https port. This is very confusing. This PR makes the broker identifier match the "lookup service address" in all cases. ### Modifications - consistently use "lookup service address" as the broker's identifier in Pulsar load balancing. - for backwards compatibility & mixed version support, add `lookupServiceAddress` field to the leader broker information. ### Documentation <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. --> - [ ] `doc` <!-- Your PR contains doc changes. --> - [ ] `doc-required` <!-- Your PR changes impact docs and you will update later --> - [x] `doc-not-needed` <!-- Your PR changes do not impact docs --> - [ ] `doc-complete` <!-- Docs have been already added --> ### Matching PR in forked repository PR in forked repository: https://github.com/lhotari/pulsar/pull/170 -- 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]
