-
Notifications
You must be signed in to change notification settings - Fork 2k
feat(cubestore): EXPLAIN ANALYZE DETAILED per-query trace #11016
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
waralexrom
wants to merge
21
commits into
master
Choose a base branch
from
cubestore-datailed-analyze
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
83a42c5
feat(cubestore): EXPLAIN ANALYZE DETAILED trace skeleton
waralexrom 6eee4f8
feat(cubestore): trace metastore RPC calls during detailed analyze
waralexrom 1a3e157
feat(cubestore): trace metastore calls via generated TracedMetaStore …
waralexrom b15d611
feat(cubestore): trace router planning phases in detailed analyze
waralexrom 2f9c0d9
feat(cubestore): route detailed analyze through the real router-selec…
waralexrom 75d20b7
feat(cubestore): per-query MemoryPool peak on the detailed-analyze main
waralexrom 3ab788d
feat(cubestore): per-query MemoryPool peak on the select subprocess
waralexrom d0f4a5f
feat(cubestore): harvest final-stage DataFusion node metrics on the main
waralexrom fcb8d9b
feat(cubestore): harvest worker subplan DataFusion node metrics
waralexrom 8efe826
feat(cubestore): record serialized byte volume on serialize ops
waralexrom afbb23a
feat(cubestore): add output_rows to node metrics
waralexrom 6ec146a
feat(cubestore): capture executed physical plan text in detailed analyze
waralexrom d9d5fcf
feat(cubestore): measure per-region wall time and main->worker round-…
waralexrom ae36601
feat(cubestore): render explicit transport per boundary in detailed a…
waralexrom f1c46e5
feat(cubestore): render detailed analyze as a compact tree
waralexrom 4537290
feat(cubestore): add category summary, per-line kind, human-readable …
waralexrom fc07213
feat(cubestore): per-node totals in tree, move summary to bottom with…
waralexrom a75d6b9
fix(cubestore): mark wrapper spans with a flag, exclude choose_index …
waralexrom f6cab8d
test(cubestore): smoke test for EXPLAIN ANALYZE DETAILED
waralexrom 4f84a78
feat(cubestore): remove EXPLAIN ANALYZE EXTENDED, superseded by DETAILED
waralexrom be0f17f
refactor(cubestore): extract EXPLAIN ANALYZE DETAILED into its own mo…
waralexrom File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NETWORK_MESSAGE_VERSIONis still1even thoughNetworkMessagegained four new variants. Serde's default externally‑tagged repr keys by variant name, so existing variants keep working across a rolling deploy — but an old binary that receives one of the new variants will fail deserialization with a generic "unknown variant" error rather than the friendlier protocol-version mismatch on line 137. SinceEXPLAIN ANALYZE DETAILEDis user-initiated and opt-in this is unlikely to bite in practice, but worth either (a) bumping the version to make the failure mode clear, or (b) leaving a comment here noting that adding variants is wire‑compatible only because the repr is by name.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@claude We have never bumped the protocol version before. In this case, we preserve both compatibility on the production path and consistency during a rolling deployment across the cluster (which would actually be disrupted by a version bump). So it seems that bumping the version is not justified here.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Claude finished @waralexrom's task in 39s —— View job
Re: bumping
NETWORK_MESSAGE_VERSIONYou're right, and I'll withdraw the suggestion to bump it. Your reasoning is actually stronger than my original note gave it credit for.
The check at
message.rs:136is a strict equality:So bumping
1 → 2doesn't just make the new*Detailedvariants fail more clearly — it makes every message between a v1 node and a v2 node fail, including the hotSelect/RouterSelect/MetaStoreCalltraffic. During a rolling deploy the cluster is mixed-version by definition, so a bump would take the whole cluster down for the rollout window. That's the opposite of what the version field should protect.Staying at
1is correct here:*Detailedvariants only ever cross the wire when a user explicitly runsEXPLAIN ANALYZE DETAILED, which is opt-in and not part of steady-state or rolling-deploy traffic. The only degenerate case (an old binary receiving a new variant) yields a generic "unknown variant" deser error instead of the friendlier mismatch message — an acceptable trade for not breaking rolling deploys.So: no version bump. The only thing I'd still gently suggest — purely optional — is a one-line comment near the version constant or the new variants recording why it's safe to add variants without bumping (the by-name repr + opt-in path), so the next person doesn't re-derive this or "helpfully" bump it. Happy to add that if you want it; otherwise this is resolved on my end.
· branch
cubestore-datailed-analyze