Skip to content

Expose consensus subscription queue readiness - #19302

Open
Caideyipi wants to merge 1 commit into
masterfrom
codex/queues-bound-readiness
Open

Caideyipi wants to merge 1 commit into
masterfrom
codex/queues-bound-readiness

Conversation

@Caideyipi

@Caideyipi Caideyipi commented Nov 17, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Add queues_bound_on_dns to SHOW 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

SHOW SUBSCRIPTIONS DETAILS ON "topic-1";

The relevant columns can look like this:

TopicName ConsumerGroupName DataNodeId queues_bound_on_dns
topic-1 group-1 3 [3, 4]
topic-1 group-1 4 [3, 4]

[3, 4] means those DataNodes independently reported all matching local queues bound when sampled.

Validation

  • Scoped Spotless command exited 0.
  • git show --check passed.
  • Maven tests were not run.

@Caideyipi

Copy link
Copy Markdown
Collaborator Author

Review round 1 for commit 7c3eade1aa11d474aa50fd5a1c3dc827e5609c97 found no actionable issues. The final local SHA and confirmed remote PR head are both 7c3eade1aa11d474aa50fd5a1c3dc827e5609c97. The scoped Spotless command exited 0 and git show --check passed; Maven tests were not run. No update step remains incomplete.

@sonarqubecloud

Copy link
Copy Markdown

Quality Gate Failed Quality Gate failed

Failed conditions
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants