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

release-22.2: server: fix a race condition during server initialization #101137

Closed

Conversation

irfansharif
Copy link
Contributor

@irfansharif irfansharif commented Apr 10, 2023

Backport 1/1 commits from #101097.

/cc @cockroachdb/release


Fixes #91414.
Fixes #101010.
Fixes #100902.

The call to registerEnginesForDiskStatsMap needs to wait until the store IDs are known.

Release note: None
Epic: None

Release justification: Benign bug fix.

Fixes cockroachdb#91414.
Fixes cockroachdb#101010.
Fixes cockroachdb#100902.

The call to registerEnginesForDiskStatsMap needs to wait until the store
IDs are known.

Release note: None
@irfansharif irfansharif requested review from knz and sumeerbhola April 10, 2023 18:07
@irfansharif irfansharif requested a review from a team as a code owner April 10, 2023 18:07
@blathers-crl
Copy link

blathers-crl bot commented Apr 10, 2023

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Patches should only be created for serious issues or test-only changes.
  • Patches should not break backwards-compatibility.
  • Patches should change as little code as possible.
  • Patches should not change on-disk formats or node communication protocols.
  • Patches should not add new functionality.
  • Patches must not add, edit, or otherwise modify cluster versions; or add version gates.
If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

  • What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
  • Will this work in a cluster of mixed patch versions? Did we test that?
  • If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

@blathers-crl
Copy link

blathers-crl bot commented Apr 10, 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

@knz knz left a comment

Choose a reason for hiding this comment

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

I think this change was not needed. Here the call to registerEnginesForDiskStatsMap was already properly ordered. Is it possible this race condition was never reported on the 22.2 branch?

@irfansharif
Copy link
Contributor Author

irfansharif commented Apr 10, 2023

Doh, I didn't carefully read the original PR, I think the race is still possible. The ordering you're describing (s.node.registerEnginesForDiskStatsMap happening after waitForAdditionalStoreInit) was also true before #101097. I'll send a follow up.

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