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
release-23.2: cluster-ui, db-console: fix bug where store ids are treated as node ids #120212
release-23.2: cluster-ui, db-console: fix bug where store ids are treated as node ids #120212
Conversation
Previously, store ids were being treated as node ids on the databases view. This resulted in "Regions/Nodes" column showing inaccurate information in some cases. Now, store ids are mapped to node ids on the databases view which resolves the issue. Also, a log message is skipped during tests so that the output isn't polluted with expected warnings. Fixes: #118957 Release note (ui change): Resolves an issue where clusters with multiple stores per node may list inaccurate region/node information in the databases table.
2f2d6d7
to
9c9dd35
Compare
Thanks for opening a backport. Please check the backport criteria before merging:
If your backport adds new functionality, please ensure that the following additional criteria are satisfied:
Also, please add a brief release justification to the body of your PR to justify this |
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.
Reviewed 2 of 14 files at r1, all commit messages.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @laurenbarker and @xinhaoz)
TFTRs! |
Backport 1/1 commits from #119260 on behalf of @laurenbarker.
/cc @cockroachdb/release
Previously, store ids were being treated as node ids on the databases view. This resulted in "Regions/Nodes" column showing inaccurate information in some cases. Now, store ids are mapped to node ids on the databases view which resolves the issue.
Fixes: #118957
Release note (ui change): Resolves an issue where clusters with multiple stores per node may list inaccurate region/node information in the databases table.
Release justification: Without this fix, customers with multiple stores per node may see inaccurate information in the databases table.