statedb: avoid revision bumps for missing deletes#163
Merged
Conversation
Currently, (*writeTxnState).delete increments the table revision before checking whether the target object even exists. A committed delete of a missing object could thus advance the table revision without producing a corresponding revision index entry or watch notification. Fix this by moving the revision allocation until after the primary key lookup succeeded and any CompareAndDelete guard passed. Signed-off-by: Tobias Klauser <tobias@cilium.io>
|
joamaki
approved these changes
Jun 11, 2026
Contributor
|
Thanks! Just missed StateDB v0.8.2. Should've checked the open PRs first.. |
This file contains hidden or 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
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.
Currently,
(*writeTxnState).deleteincrements the table revision before checking whether the target object even exists. A committed delete of a missing object could thus advance the table revision without producing a corresponding revision index entry or watch notification.Fix this by moving the revision allocation until after the primary key lookup succeeded and any
CompareAndDeleteguard passed.