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

[Doc] Lack of understanding "Namespace change events" for Zookeeper #23748

Open
1 of 2 tasks
gulecroc opened this issue Dec 17, 2024 · 1 comment
Open
1 of 2 tasks

[Doc] Lack of understanding "Namespace change events" for Zookeeper #23748

gulecroc opened this issue Dec 17, 2024 · 1 comment
Labels
doc-required Your PR changes impact docs and you will update later.

Comments

@gulecroc
Copy link

gulecroc commented Dec 17, 2024

Search before asking

  • I searched in the issues and found nothing similar.

What issue do you find in Pulsar docs?

It is written that using namespace change events :

  • Avoid using ZooKeeper and introduce more loads to ZooKeeper.

https://pulsar.apache.org/docs/4.0.x/concepts-multi-tenancy/#namespace-change-events-and-topic-level-policies

I don't understand the purpose of this : is it use more or less Zookeeper ?

Best regards,
Guillaume

What is your suggestion?

Correct description

Any reference?

No response

Are you willing to submit a PR?

  • I'm willing to submit a PR!
@gulecroc gulecroc added the doc-required Your PR changes impact docs and you will update later. label Dec 17, 2024
@lhotari
Copy link
Member

lhotari commented Dec 18, 2024

I don't understand the purpose of this : is it use more or less Zookeeper ?

I agree, it's hard to understand. There's a need to improve this description. My assumption is what it means is that namespace change events (and topic level policies) provide a way to reduce load on the metadata store backend (which is Zookeeper in most cases with Pulsar).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-required Your PR changes impact docs and you will update later.
Projects
None yet
Development

No branches or pull requests

2 participants