[PIP-136]: Sync Pulsar policies across multiple clouds #15223
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rdhabalia
requested review from
Jason918,
Technoboy-,
codelipenghui,
eolivelli,
jiazhai,
merlimat and
sijie
|
@rdhabalia:Thanks for your contribution. For this PR, do we need to update docs? |
rdhabalia
force-pushed
the
metadata_sync2
branch
from
0e0eafe to
ad74ea9
Compare
|
can we get a review? we need this feature for our usecase? |
|
ping. asking community to review it. |
|
this PR has been open for more than 2 months with approved PIP. Please don't change the release of this PR without reviewing and merging it. |
|
closing with new implementation: #16425 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Motivation
Implementation of PIP-136
Sometimes it's not possible to share metadata-store (global zookeeper) between pulsar clusters deployed on separate cloud provider platforms, and synchronizing configuration metadata (policies) can be a critical path to share tenant/namespace/topic policies between clusters and administrate pulsar policies uniformly across all clusters. Therefore, we need a mechanism to sync configuration metadata between clusters deployed on the different cloud platforms.
PIP-136 also has a section
Rejected alternativewith use of system-topic along with metadata-synchronizer to replicate and persist local topic policies with it.