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

[pulsar-broker] cluster-resource use cluster name to fetch cluster-metadata #9928

Closed
wants to merge 5 commits into from

Conversation

rdhabalia
Copy link
Contributor

Motivation

Note: On top of : #9925
Cluster-resources should be able to fetch cluster-metadata and internal-path should be handled by the base-resources. It will make code clean and will be helpful for future abstraction.

@rdhabalia rdhabalia added this to the 2.8.0 milestone Mar 16, 2021
@rdhabalia rdhabalia self-assigned this Mar 16, 2021
@rdhabalia rdhabalia changed the title @rdhabalia [pulsar-broker] cluster-resource use cluster name to fetch cluster-metadata [pulsar-broker] cluster-resource use cluster name to fetch cluster-metadata Mar 16, 2021
Copy link
Contributor

@eolivelli eolivelli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
I left one suggestion PTAL

@@ -390,7 +391,7 @@ public void deleteCluster(
}
} catch (Exception e) {
log.error("[{}] Failed to get cluster usage {}", clientAppId(), cluster, e);
throw new RestException(e);
throw new RestException(e instanceof ExecutionException ? e.getCause() : e);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about adding an utility function for this line? I see it written more times

@rdhabalia
Copy link
Contributor Author

/pulsarbot run-failure-checks

} else {
log.error("[{}] Failed to get partitioned topic list for namespace {}", clientAppId(),
namespaceName.toString(), e);
throw new RestException(e);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be better, just a suggestion
throw new RestException(e instanceof ExecutionException ? e.getCause() : e)

@codelipenghui
Copy link
Contributor

Hi Rajan @rdhabalia, Could you please help resolve the conflicts? so that we can merge it before 2.8.0

@codelipenghui codelipenghui modified the milestones: 2.8.0, 2.9.0 May 23, 2021
@rdhabalia
Copy link
Contributor Author

it seems #11693 again had same changes and that new PR is merged. so, we should close this one.

@eolivelli eolivelli modified the milestones: 2.9.0, 2.10.0 Oct 6, 2021
@codelipenghui codelipenghui removed this from the 2.10.0 milestone Jan 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants