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/contention: turn on sql.contention.record_serialization_conflicts… #116664

Merged

Conversation

xinhaoz
Copy link
Member

@xinhaoz xinhaoz commented Dec 18, 2023

….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.

Copy link

blathers-crl bot commented Dec 18, 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

@xinhaoz xinhaoz requested review from maryliag, koorosh, a team and abarganier and removed request for a team December 18, 2023 15:37
Copy link
Contributor

@maryliag maryliag left a 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: :shipit: complete! 0 of 0 LGTMs obtained (waiting on @abarganier and @koorosh)

@xinhaoz xinhaoz force-pushed the turn-on-serialization-conflict-recording branch 2 times, most recently from c61dbe5 to bc99527 Compare December 18, 2023 15:54
Copy link
Member Author

@xinhaoz xinhaoz left a 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: :shipit: complete! 0 of 0 LGTMs obtained (waiting on @abarganier and @koorosh)

Copy link
Contributor

@maryliag maryliag left a comment

Choose a reason for hiding this comment

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

:lgtm:

Reviewable status: :shipit: 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
@xinhaoz xinhaoz force-pushed the turn-on-serialization-conflict-recording branch from bc99527 to 288a52d Compare December 18, 2023 20:19
@xinhaoz
Copy link
Member Author

xinhaoz commented Dec 18, 2023

bors r+

@craig
Copy link
Contributor

craig bot commented Dec 18, 2023

Build succeeded:

@craig craig bot merged commit fc58263 into cockroachdb:master Dec 18, 2023
9 checks passed
@xinhaoz xinhaoz deleted the turn-on-serialization-conflict-recording branch December 19, 2023 16:10
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.

None yet

3 participants