Skip to content
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-22.2: ui: sql activity pages depend on node info #88572

Merged
merged 1 commit into from
Sep 23, 2022

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Sep 23, 2022

Backport 1/1 commits from #88461 on behalf of @matthewtodd.

/cc @cockroachdb/release


Fixes #85249.

Previously, the statements, transactions, and transaction details pages had an implicit dependency on the state.adminUI.nodes list in the redux store, and without that list, the Regions/Nodes columns and filters would be incorrectly hidden for multiregion clusters, unless the user happened to have already browsed through a page (such as statement details) that loaded the list.

(This bug was affecting dedicated cloud clusters only. Self-hosted clusters were working properly because their global mechanism to sync alert data happened to refresh the node list.)

This change makes the dependency explicit and refreshes the list of nodes on entering those three pages.

Before After
Screen Shot 2022-09-22 at 10 42 33 AM Screen Shot 2022-09-22 at 10 41 12 AM
Screen Shot 2022-09-22 at 10 42 42 AM Screen Shot 2022-09-22 at 10 41 22 AM
Screen Shot 2022-09-22 at 10 43 00 AM Screen Shot 2022-09-22 at 10 41 38 AM

Release note (bug fix): The statements, transactions, and transaction details pages in the admin console now properly show the Regions/Nodes columns and filters for multiregion clusters.


Release justification: Bug fixes and low-risk updates to new functionality

Fixes #85249.

Previously, the statements, transactions, and transaction details pages
had an implicit dependency on the `state.adminUI.nodes` list in the
redux store, and without that list, the Regions/Nodes columns and
filters would be incorrectly hidden for multiregion clusters, unless the
user happened to have already browsed through a page (such as statement
details) that loaded the list.

(This bug was affecting dedicated cloud clusters only. Self-hosted
clusters were working properly because their global mechanism to sync
alert data happened to [refresh the node list][1].)

This change makes the dependency explicit and refreshes the list of
nodes on entering those three pages.

[1]: https://github.com/cockroachdb/cockroach/blob/6a25c6f4b985ddcd08ed51772f9e8a2645aa4582/pkg/ui/workspaces/db-console/src/redux/alerts.ts#L678-L682

Release note (bug fix): The statements, transactions, and transaction
details pages in the admin console now properly show the Regions/Nodes
columns and filters for multiregion clusters.
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-22.2-88461 branch from 6c55864 to a814372 Compare September 23, 2022 15:03
@blathers-crl
Copy link
Author

blathers-crl bot commented Sep 23, 2022

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Patches should only be created for serious issues or test-only changes.
  • Patches should not break backwards-compatibility.
  • Patches should change as little code as possible.
  • Patches should not change on-disk formats or node communication protocols.
  • Patches should not add new functionality.
  • Patches must not add, edit, or otherwise modify cluster versions; or add version gates.
If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

  • What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
  • Will this work in a cluster of mixed patch versions? Did we test that?
  • If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Sep 23, 2022
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Copy link
Contributor

@maryliag maryliag left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @matthewtodd)

@matthewtodd matthewtodd merged commit dcf5d18 into release-22.2 Sep 23, 2022
@matthewtodd matthewtodd deleted the blathers/backport-release-22.2-88461 branch September 23, 2022 18:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants