Repository navigation
Conversation
Collaborator
Author
|
Review round 1 for commit |
|
jt2594838
approved these changes
Nov 17, 2026
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.




Summary
Add
queues_bound_on_dnstoSHOW SUBSCRIPTIONS DETAILS. The column lists DataNode IDs that reported all currently matching local DataRegion queues bound for the topic and consumer group.Semantics and limits
Each DataNode evaluates its local subscription metadata and Region topology independently. ConfigNode includes an ID only for a successful response from a currently registered DataNode and the requested data model. An unavailable node, an unsuccessful response, or an older node that does not return this optional field is omitted.
This is a point-in-time diagnostic, not a cluster-wide write barrier. DataNodes are sampled independently, and Region or subscription topology can change after a sample or while ConfigNode aggregates responses. A later-created Region is not covered by an earlier result. No distributed lock is used. Queue-bound means the local queue binding is present; it does not mean lazy prefetch initialization or catch-up has completed. If a DataNode currently has no matching local DataRegion, its empty set of matching queues satisfies the all-queues-bound check.
Example
The relevant columns can look like this:
[3, 4]means those DataNodes independently reported all matching local queues bound when sampled.Validation
git show --checkpassed.