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

kvserver: improve server-side trace print on ctx cancellation #105703

Merged
merged 1 commit into from
Jun 28, 2023

Conversation

tbg
Copy link
Member

@tbg tbg commented Jun 28, 2023

Noticed in passing. When a replica circuit breaker trips, the error will
typically wrap context.Canceled but this will have nothing to do with the
client's ctx (and the logs will be spammed). If we try to be sensitive to
client ctx cancellation, we ought to look at the client's ctx.

Epic: none
Release note: None

Noticed in passing. When a replica circuit breaker trips, the error will
typically wrap `context.Canceled` but this will have nothing to do with the
client's `ctx` (and the logs will be spammed). If we try to be sensitive to
client ctx cancellation, we ought to look at the client's ctx.

Epic: none
Release note: None
@tbg tbg requested a review from adityamaru June 28, 2023 10:59
@tbg tbg requested review from a team as code owners June 28, 2023 10:59
@blathers-crl
Copy link

blathers-crl bot commented Jun 28, 2023

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
Contributor

@adityamaru adityamaru left a comment

Choose a reason for hiding this comment

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

Thanks for doing this @erikgrinaker flagged this last week but I hadn't got around to sending the patch - #105378. Should we also not log if the sp.GetConfiguredRecording() returns an empty recording as noted in that issue?

@tbg
Copy link
Member Author

tbg commented Jun 28, 2023

Should we also not log if the sp.GetConfiguredRecording() returns an empty recording as noted in that issue?

That seems sensible, but I'd rather not grow this drive-by in scope. How about we leave the issue open to track that part?

bors r=adityamaru

@craig
Copy link
Contributor

craig bot commented Jun 28, 2023

Build succeeded:

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.

3 participants