Skip to content
New issue

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

Support advertised listeners for HTTP and HTTPS services #14839

Merged
merged 1 commit into from
Mar 28, 2022

Conversation

merlimat
Copy link
Contributor

Motivation

The configuration setting advertisedListeners allows to specify specific listeners for pulsar and pulsar+ssl protocols, along with other protocol handlers, though it's not currently working when HTTP(s) addresses are specified.

@merlimat merlimat added type/bug The PR fixed a bug or issue reported a bug release/2.9.3 release/2.10.1 labels Mar 24, 2022
@merlimat merlimat added this to the 2.11.0 milestone Mar 24, 2022
@merlimat merlimat self-assigned this Mar 24, 2022
@github-actions
Copy link

@merlimat:Thanks for your contribution. For this PR, do we need to update docs?
(The PR template contains info about doc, which helps others know more about the changes. Can you provide doc-related info in this and future PR descriptions? Thanks)

@Anonymitaet
Copy link
Member

@merlimat do we need to update docs for this PR?

@merlimat
Copy link
Contributor Author

@merlimat do we need to update docs for this PR?

No need for that. It's just fixing the existing behavior.

@merlimat merlimat added doc-not-needed Your PR changes do not impact docs and removed doc-label-missing labels Mar 25, 2022
@merlimat merlimat merged commit 3f66c26 into apache:master Mar 28, 2022
@merlimat merlimat deleted the fix-advertised-listeners-http branch March 28, 2022 15:56
Nicklee007 pushed a commit to Nicklee007/pulsar that referenced this pull request Apr 20, 2022
codelipenghui added a commit to codelipenghui/incubator-pulsar that referenced this pull request May 17, 2022
…g topic lookup

### Motivation

apache#14839 fixes the http lookup with multiple advertised listeners, and the added test
is try to verify the advertised listeners with 2 brokers, but the config of the
additional broker will not update, so the test get passed.

The root cause is we are using the (advertised address + WebService port) to register
the broker under the loadbalance path, but while creating the lookup result, we will
use the WebService URL to get the data, so we will get `MetadataStoreException$NotFoundException`.

### Modification

- Added properties support for ResourceUnit, so that we can carry more information while getting least loaded broker
- For creating the lookup result, use the broker znode name to get the broker data if it presents in the ResourceUnit

### Verification

No new tests needed, just fix the test that added in apache#14839
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/broker cherry-picked/branch-2.9 Archived: 2.9 is end of life cherry-picked/branch-2.10 doc-not-needed Your PR changes do not impact docs release/2.9.3 release/2.10.1 type/bug The PR fixed a bug or issue reported a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants