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.

Sign up for GitHub

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

Jump to bottom

sql: sprinkle more log messages throughout SQL #112902

Closed
yuzefovich opened this issue Oct 23, 2023 · 0 comments · Fixed by #124779
Closed

sql: sprinkle more log messages throughout SQL #112902

yuzefovich opened this issue Oct 23, 2023 · 0 comments · Fixed by #124779
Assignees
@yuzefovich
Labels
C-cleanup Tech debt, refactors, loose ends, etc. Solution not expected to significantly change behavior. O-support Would prevent or help troubleshoot a customer escalation - bugs, missing observability/tooling, docs P-3 Issues/test failures with no fix SLA T-sql-queries SQL Queries Team

Comments

@yuzefovich
Copy link
Member

yuzefovich commented Oct 23, 2023 •
edited by cockroach-jira-scripts
Loading

We should add some more logging at the main execution points (say planNodes) throughout the SQL layer somewhere on the boundary between SQL and KV client. I don't have concrete points yet, but my hope is that it would help with investigating intermittently slow seemingly-stuck executions like we've seen in https://github.com/cockroachlabs/support/issues/2664.

Jira issue: CRDB-32671
@yuzefovich yuzefovich added C-cleanup Tech debt, refactors, loose ends, etc. Solution not expected to significantly change behavior. O-support Would prevent or help troubleshoot a customer escalation - bugs, missing observability/tooling, docs T-sql-queries SQL Queries Team labels Oct 23, 2023
@github-project-automation github-project-automation bot moved this to Triage in SQL Queries Oct 23, 2023
@DrewKimball DrewKimball moved this from Triage to 24.1 Release in SQL Queries Oct 31, 2023
@michae2 michae2 added the P-3 Issues/test failures with no fix SLA label Dec 21, 2023
@yuzefovich yuzefovich moved this from 24.1 Release to Active in SQL Queries Feb 27, 2024
@yuzefovich yuzefovich moved this from Active to 24.2 Release in SQL Queries Apr 10, 2024
@yuzefovich yuzefovich moved this from 24.2 Release to Active in SQL Queries May 28, 2024
@yuzefovich yuzefovich mentioned this issue May 28, 2024
Merged
@craig craig bot closed this as completed in d5f825c May 29, 2024
@github-project-automation github-project-automation bot moved this from Active to Done in SQL Queries May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yuzefovich yuzefovich

Labels
C-cleanup Tech debt, refactors, loose ends, etc. Solution not expected to significantly change behavior. O-support Would prevent or help troubleshoot a customer escalation - bugs, missing observability/tooling, docs P-3 Issues/test failures with no fix SLA T-sql-queries SQL Queries Team
Projects
SQL Queries
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

sql: add some logging on SQL / KV boundary yuzefovich/cockroach
2 participants
@yuzefovich @michae2