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-23.1: raftlog: correctly decode empty commands #100611

Merged
merged 1 commit into from
Apr 9, 2023

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Apr 4, 2023

Backport 1/1 commits from #100401 on behalf of @erikgrinaker.

/cc @cockroachdb/release


When unquiescing a Raft group, an empty command is proposed to wake the Raft leader. During application, empty entries are considered noops, but only if they don't have a command ID. However, Raft entry decoding would preserve the command ID of an empty payload. CheckForcedErr() thus no longer considered this a noop, instead returning an error because the ProposerLeaseSequence of 0 was older than the current lease. Construction and processing of this error had a non-negligible cost when unquiescing a large number of ranges.

This patch makes sure such empty commands are decoded as empty entries, without a command ID, and thus considered noops.

Resolves #100400.

Epic: none
Release note: None


Release justification: fixes performance regression and errors due to incorrect decoding of Raft unquiescence commands.

@blathers-crl blathers-crl bot requested a review from a team as a code owner April 4, 2023 17:46
@blathers-crl blathers-crl bot requested a review from a team April 4, 2023 17:46
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-23.1-100401 branch from 641406f to f43313a Compare April 4, 2023 17:46
@blathers-crl
Copy link
Author

blathers-crl bot commented Apr 4, 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 blathers-crl bot requested a review from pav-kv April 4, 2023 17:46
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-23.1-100401 branch from 9b59edd to 2930760 Compare April 4, 2023 17:46
@blathers-crl blathers-crl bot requested a review from tbg April 4, 2023 17:46
@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Apr 4, 2023
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@erikgrinaker erikgrinaker requested a review from nicktrav April 4, 2023 18:22
Copy link
Collaborator

@nicktrav nicktrav left a comment

Choose a reason for hiding this comment

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

Backport LGTM.

@erikgrinaker erikgrinaker force-pushed the blathers/backport-release-23.1-100401 branch from 2930760 to 3b96588 Compare April 9, 2023 10:09
When unquiescing a Raft group, an empty command is proposed to wake the
Raft leader. During application, empty entries are considered noops, but
only if they don't have a command ID. However, Raft entry decoding would
preserve the command ID of an empty payload. `CheckForcedErr()` thus no
longer considered this a noop, instead returning an error because the
`ProposerLeaseSequence` of 0 was older than the current lease.
Construction and processing of this error had a non-negligible cost when
unquiescing a large number of ranges.

This patch makes sure such empty commands are decoded as empty entries,
without a command ID, and thus considered noops.

Epic: none
Release note: None
@erikgrinaker erikgrinaker force-pushed the blathers/backport-release-23.1-100401 branch from 3b96588 to 7e2d441 Compare April 9, 2023 12:01
@erikgrinaker erikgrinaker merged commit cfbd751 into release-23.1 Apr 9, 2023
@erikgrinaker erikgrinaker deleted the blathers/backport-release-23.1-100401 branch April 9, 2023 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants