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

Acceptance testing 22.2 - Transaction high contention insights do not link users to transaction that blocked it #87784

Closed
kevin-v-ngo opened this issue Sep 10, 2022 · 1 comment
Assignees
Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.

Comments

@kevin-v-ngo
Copy link

kevin-v-ngo commented Sep 10, 2022

We should guide users to the blocking (transactions N waited on) transactions for more context which would give users more details. More specifically, whether the blocking transaction also waited for other transactions to complete.

image

Jira issue: CRDB-19536

@kevin-v-ngo kevin-v-ngo added the C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. label Sep 10, 2022
@ericharmeling ericharmeling self-assigned this Sep 12, 2022
ericharmeling added a commit to ericharmeling/cockroach that referenced this issue Sep 12, 2022
This commit adds a link to the transaction insight details page for
a blocking transaction, if that transaction is also waiting on another
transaction.

Fixes cockroachdb#87784.

Release note: None
Release justification: high-benefit change to existing functionality
ericharmeling added a commit to ericharmeling/cockroach that referenced this issue Sep 16, 2022
This commit adds a link to the transaction insight details page for
a blocking transaction, if that transaction is also waiting on another
transaction.

Fixes cockroachdb#87784.

Release note: None
Release justification: high-benefit change to existing functionality
@ericharmeling
Copy link
Contributor

Closing this issue (see #87876 (comment)). I think resolving #87750 and #83780 and #91696 should be sufficient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants