[Branch-2.8] Fix validateGlobalNamespaceOwnership wrap exception issue. #14612
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.
Cherry-pick #14269
Motivation
When Rest API call
AdminResource#validateGlobalNamespaceOwnership
, broker will executePulsarWebResource#checkLocalOrGetPeerReplicationCluster
.In
PulsarWebResource#checkLocalOrGetPeerReplicationCluster
:pulsar/pulsar-broker/src/main/java/org/apache/pulsar/broker/web/PulsarWebResource.java
Lines 773 to 802 in 6d717a0
Line 780, 794, and 801 has thrown RestException.
But
validateGlobalNamespaceOwnership
has wrapped the exception :pulsar/pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/AdminResource.java
Lines 202 to 216 in 6d717a0
This could make the user confused that the log printed is not matched with the REST API.
Modification
Documentation
no-need-doc