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/contention: turn on sql.contention.record_serialization_conflicts… #116664
sql/contention: turn on sql.contention.record_serialization_conflicts… #116664
Conversation
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does this turn on certain collections (e.g. traces) that it wouldn't with the setting off? Curious if turning on by default can cause performance degradation
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @abarganier and @koorosh)
c61dbe5
to
bc99527
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@maryliag No, it just allows the information to be recorded by the contention registry when it is available.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @abarganier and @koorosh)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @abarganier and @koorosh)
….enabled Turn on sql.contention.record_serialization_conflicts.enabled by default and make this setting public. Release note (ops change): The cluster setting sql.contention.record_serialization_conflicts.enabled is now on by default. This means any 40001 errors that are returned containing conflicting transaction information will be recorded by the contention registry. Closes: cockroachdb#114416
bc99527
to
288a52d
Compare
bors r+ |
Build succeeded: |
….enabled
Turn on sql.contention.record_serialization_conflicts.enabled by default and make this setting public.
Release note (ops change): The cluster setting
sql.contention.record_serialization_conflicts.enabled is now on by default. This means any 40001 errors that are returned containing conflicting transaction information will be recorded by the contention registry.