feat(api): add non-throwing multi-cluster status query - #664
Merged
Merged
Conversation
SunSi12138
marked this pull request as ready for review
September 12, 2026 03:58
10 tasks
SunSi12138
commented
Sep 12, 2026
SunSi12138
left a comment
SunSi12138
left a comment
Owner
Author
There was a problem hiding this comment.
发现 1 个会让新 status API 与现有独立 readiness 状态域产生确定性矛盾的 blocker；其余范围继续复核中。
SunSi12138
commented
Sep 12, 2026
SunSi12138
left a comment
SunSi12138
left a comment
Owner
Author
There was a problem hiding this comment.
补充 1 个独立的 public-interface compatibility blocker：default fallback 当前依赖一个从未标准化的 legacy exception shape。
This was referenced Sep 12, 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
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.
Summary
SharpLinkClusterStatusSnapshotas the point-in-time status projection for one configured cluster slotISharpLinkMultiClusterClient.TryGetClusterStatus(...)so valid-but-absent (including concurrently removed) clusters are an expected query miss instead of exception-driven control flowGetClusterState/GetClusterRuntimeState/GetClusterReadinessconvenience getters unchanged for compatibilityScope
This completes the remaining query/audit part of #653 without duplicating the split child issues. Multi-cluster mutation results from #656 are already on
dev; #652, #654, and #655 remain independent work for readiness publication, runtime configuration results, and health results respectively.No RPC wire contract or request hot path is changed.
Validation
Closes #653