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

PIP-45: Migrate NamespaceService to use MetadataStore #10532

Merged
merged 31 commits into from
May 25, 2021

Conversation

merlimat
Copy link
Contributor

Motivation

Converted the NamespaceService to use MetadataStore instead of direct ZK access.

@merlimat merlimat added the type/enhancement The enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages label May 10, 2021
@merlimat merlimat added this to the 2.8.0 milestone May 10, 2021
@merlimat merlimat self-assigned this May 10, 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.

great work

}
}, null);
return isExistFuture;
return pulsar.getLocalMetadataStore().exists(ServiceUnitUtils.path(bundle));
Copy link
Contributor

Choose a reason for hiding this comment

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

it is amazing to see how much this code is simpler !

@merlimat merlimat merged commit 4d4f624 into apache:master May 25, 2021
yangl pushed a commit to yangl/pulsar that referenced this pull request Jun 23, 2021
* PIP-45: Migrate NamespaceService to use MetadataStore

* Fixed copying policies to local store

* Fixed checkstyle

* Fixed tests

* Fixed test

* Fixed handling of BadVersionException

* Converted bundle split into an HTTP async operation

* Fixed issues in concurrent bundle splits

* Fixed checkstyle

* Make sure the ownership is triggered for the first attempt

* validateTopicOwnershipAsync

* Fixed deadlock when removeTopicFromCache calls NamespaceService.getBundle from MetadataStore thread

* Fixed checkstyle

* Fixed handling of future composition in validateTopicOwnershipAsync

* In internalCreateSubscriptionForNonPartitionedTopic() we shouldn't have mix sync & async operations

* Fixed checkstyle

* Fixed internalUnloadNonPartitionedTopic

* Fixed mixed sync-async usage of NamespaceService.getBundle

* Use awaitility in AdminTest

* validateGlobalNamespaceOwnership should also be done asynchronously

* Fixed checkstyle

* Fixed missing ,

* Try to get stack traces for timedout test

* Added async version of getTopicReference

* Removed import

* Fixed test mocks

* Reflect that removeTopicFromCache is an async operation
bharanic-dev pushed a commit to bharanic-dev/pulsar that referenced this pull request Mar 18, 2022
* PIP-45: Migrate NamespaceService to use MetadataStore

* Fixed copying policies to local store

* Fixed checkstyle

* Fixed tests

* Fixed test

* Fixed handling of BadVersionException

* Converted bundle split into an HTTP async operation

* Fixed issues in concurrent bundle splits

* Fixed checkstyle

* Make sure the ownership is triggered for the first attempt

* validateTopicOwnershipAsync

* Fixed deadlock when removeTopicFromCache calls NamespaceService.getBundle from MetadataStore thread

* Fixed checkstyle

* Fixed handling of future composition in validateTopicOwnershipAsync

* In internalCreateSubscriptionForNonPartitionedTopic() we shouldn't have mix sync & async operations

* Fixed checkstyle

* Fixed internalUnloadNonPartitionedTopic

* Fixed mixed sync-async usage of NamespaceService.getBundle

* Use awaitility in AdminTest

* validateGlobalNamespaceOwnership should also be done asynchronously

* Fixed checkstyle

* Fixed missing ,

* Try to get stack traces for timedout test

* Added async version of getTopicReference

* Removed import

* Fixed test mocks

* Reflect that removeTopicFromCache is an async operation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement The enhancements for the existing features or docs. e.g. reduce memory usage of the delayed messages
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants