[fix][broker] fix MetadataStoreException$NotFoundException while doing topic lookup#15633
Merged
Technoboy- merged 2 commits intoMay 19, 2022
Merged
Conversation
…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
|
@codelipenghui:Thanks for your contribution. For this PR, do we need to update docs? |
1 similar comment
|
@codelipenghui:Thanks for your contribution. For this PR, do we need to update docs? |
|
@codelipenghui:Thanks for providing doc info! |
Contributor
Author
|
/pulsarbot run-failure-checks |
315157973
approved these changes
May 18, 2022
Technoboy-
approved these changes
May 18, 2022
BewareMyPower
approved these changes
May 19, 2022
Demogorgon314
approved these changes
May 19, 2022
nicoloboschi
pushed a commit
to datastax/pulsar
that referenced
this pull request
May 23, 2022
…g topic lookup (apache#15633) (cherry picked from commit 70551a6) (cherry picked from commit 6415b31)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
#14839 fixes the HTTP lookup with multiple advertised listeners, and the added test
is trying to verify the advertised listeners with 2 brokers, but the config of the
the additional broker will not update, so the test gets 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
Verification
No new tests are needed, just fix the test that was added in #14839
Documentation
Check the box below or label this PR directly.
Need to update docs?
no-need-doc(bug fix)