-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Fix delete namespace issue. #14215
Fix delete namespace issue. #14215
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/impl/NamespacesBase.java
Show resolved
Hide resolved
pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/impl/NamespacesBase.java
Show resolved
Hide resolved
@shibd Could you please help review this PR? |
pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/impl/NamespacesBase.java
Show resolved
Hide resolved
pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/impl/NamespacesBase.java
Show resolved
Hide resolved
pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/impl/NamespacesBase.java
Outdated
Show resolved
Hide resolved
pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/impl/NamespacesBase.java
Outdated
Show resolved
Hide resolved
Ping @eolivelli , Please help review this Pr, Thanks. |
Hi, @eolivelli Could you help review again, thanks . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm
### Motivation When we delete namespace with `force=false`, sometimes there may occur `Cannot delete non empty bundle`. Because delete system topic and delete namespace bundles are put into futures, can't keep their order. We should delete `system topic` first and then delete `namespace bundles`. ### Modifications - Use admin cli to delete system topic. - Delete system topic first and then delete namespace bundles - Make internalClearZkSources async and the code more readable. (cherry picked from commit 145f29a)
There's a new flaky test #14516 . @Technoboy- could you please check if it's caused by this PR #14215? |
Ok |
Cherry-pick #14215 ### Motivation When we delete namespace with `force=false`, sometimes there may occur `Cannot delete non empty bundle`. Because delete system topic and delete namespace bundles are put into futures, can't keep their order. We should delete `system topic` first and then delete `namespace bundles`. ### Modifications - Use admin cli to delete system topic. - Delete system topic first and then delete namespace bundles - Make internalClearZkSources async and the code more readable.
### Motivation When we delete namespace with `force=false`, sometimes there may occur `Cannot delete non empty bundle`. Because delete system topic and delete namespace bundles are put into futures, can't keep their order. We should delete `system topic` first and then delete `namespace bundles`. ### Modifications - Use admin cli to delete system topic. - Delete system topic first and then delete namespace bundles - Make internalClearZkSources async and the code more readable.
@Technoboy- Please provide a correct documentation label for your PR. |
Motivation
When we delete namespace with
force=false
, sometimes there may occurCannot delete non empty bundle
.Because delete system topic and delete namespace bundles are put into futures, can't keep their order.
We should delete
system topic
first and then deletenamespace bundles
.Modifications
Documentation
no-need-doc