-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
cluster-ui: tenants use sqlstats-supplied regions #98410
Conversation
Fixes #98056. As of #95449, the SQL Activity pages in the DB Console can draw regions information directly from the sqlstats tables, rather than having to translate node IDs to regions on page load. Here, we make that switch, but for non-system tenants only, because: 1. The ephemeral nature of serverless nodes made this view-time mapping especially problematic in that context. (See further notes in #95449.) 2. The system-tenant views also include KV node IDs in a special Regions/Nodes column, which we are unable to recreate given the backend storage structure. (Future design work might suggest removing these node IDs altogether, for a unified UI.) Release note: None
@maryliag we'll want to coordinate when to put this into a cluster-ui release. |
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.
we'll want to coordinate when to put this into a cluster-ui release.
what is the concern of what should be added together?
Reviewed 12 of 12 files at r1, all commit messages.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @matthewtodd)
Thanks, @maryliag! bors r+ |
Build failed (retrying...): |
Build succeeded: |
Fixes #98056.
As of #95449, the SQL Activity pages in the DB Console can draw regions information directly from the sqlstats tables, rather than having to translate node IDs to regions on page load.
Here, we make that switch, but for non-system tenants only, because:
The ephemeral nature of serverless nodes made this view-time mapping especially problematic in that context. (See further notes in sqlstats: include regions in statement_statistics #95449.)
The system-tenant views also include KV node IDs in a special Regions/Nodes column, which we are unable to recreate given the backend storage structure. (Future design work might suggest removing these node IDs altogether, for a unified UI.)
Screenshots!
Statements, with and without regions filter
Statement details
Transactions, with and without regions filter
Transaction details
Release note: None