[feat][pip] PIP-470: Dynamic Bookie Cluster Switching for Brokers#25774
Open
wolfstudy wants to merge 2 commits into
Open
[feat][pip] PIP-470: Dynamic Bookie Cluster Switching for Brokers#25774wolfstudy wants to merge 2 commits into
wolfstudy wants to merge 2 commits into
Conversation
Signed-off-by: xiaolongran <xiaolongran@tencent.com>
Signed-off-by: xiaolongran <xiaolongran@tencent.com>
dao-jun
reviewed
May 14, 2026
| optional int64 timestamp = 4; | ||
| optional OffloadContext offloadContext = 5; | ||
| optional string bookieClusterName = 6; // ★ new (Topic Data Ledger attribution) | ||
| repeated KeyValue properties = 7; // ★ new (extension slot) |
Member
There was a problem hiding this comment.
we already have the field properties in PIP-404. And maybe we can also use the field to store bookieClusterName
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Pulsar brokers are statically bound to a single Bookie cluster via
bookkeeperMetadataServiceUriat startup. When the underlying Bookie clusterhits capacity limits or non-recoverable failures, there is no runtime way to
re-target brokers to another Bookie cluster without restart and full data
migration. This PIP introduces zero-downtime Bookie cluster switching by
attributing each ledger to its owning cluster and routing reads accordingly.