kvserver: assert uniqueness in registerProposalLocked #97566
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We routinely overwrite entries in the `r.mu.proposals` map. That is "fine" (better if we didn't, but currently it is by design - it happens in refreshProposalsLocked and during tryReproposeWithNewLeaseIndex) but our overwrites should be no-ops, i.e. reference the exact same `*ProposalData`. This is now asserted. One way this would trip is a CmdID collision. Epic: none Release note: None
|
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. |
|
This change is |
pav-kv
approved these changes
Feb 24, 2023
|
bors r=pavelkalinnikov |
|
Build succeeded: |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We routinely overwrite entries in the
r.mu.proposalsmap. That is"fine" (better if we didn't, but currently it is by design - it
happens in refreshProposalsLocked and during
tryReproposeWithNewLeaseIndex) but our overwrites should be no-ops, i.e.
reference the exact same
*ProposalData.This is now asserted.
One way this would trip is a CmdID collision.
Epic: none
Release note: None