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

sql: add some logging on SQL / KV boundary #124779

Merged
merged 1 commit into from
May 29, 2024

Conversation

yuzefovich
Copy link
Member

This commit audits all main entry points from SQL to KV and adds simple log messages (hidden behind verbosity level 2) right before performing the KV operation. We do so both on the write and read paths. This could be helpful when investigating latency spikes with gaps in the traces (although it's still likely to be insufficient in practice - i.e. Go execution traces are likely to be needed, yet this commit could make things a bit clearer).

Fixes: #112902.

Release note: None

@yuzefovich yuzefovich requested a review from michae2 May 28, 2024 23:10
@yuzefovich yuzefovich requested a review from a team as a code owner May 28, 2024 23:10
Copy link

blathers-crl bot commented May 28, 2024

It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR?

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

@cockroach-teamcity
Copy link
Member

This change is Reviewable

Copy link
Collaborator

@michae2 michae2 left a comment

Choose a reason for hiding this comment

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

:lgtm: Very nice! This will come in handy.

Reviewed 7 of 7 files at r1, all commit messages.
Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @yuzefovich)

This commit audits all main entry points from SQL to KV and adds simple
log messages (hidden behind verbosity level 2) right before performing
the KV operation. We do so both on the write and read paths. This could
be helpful when investigating latency spikes with gaps in the traces
(although it's still likely to be insufficient in practice - i.e. Go
execution traces are likely to be needed, yet this commit could make
things a bit clearer).

Release note: None
@yuzefovich
Copy link
Member Author

TFTR!

bors r+

@craig
Copy link
Contributor

craig bot commented May 29, 2024

Build failed:

@yuzefovich
Copy link
Member Author

bors r+

@craig
Copy link
Contributor

craig bot commented May 29, 2024

Build failed:

@yuzefovich
Copy link
Member Author

Another pre-emption.

bors r+

@craig craig bot merged commit d5f825c into cockroachdb:master May 29, 2024
22 checks passed
@yuzefovich yuzefovich deleted the sql-logging branch May 29, 2024 03:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

sql: sprinkle more log messages throughout SQL
3 participants