Support per-key locking for concurrent write serialization - #3
Merged
Conversation
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
1 participant
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.
📑 Description
Introduce
KeyLock, a per-key locking mechanism for minikv that enables exclusive access to individual keys. Locks are acquired viatry_lock, which returns aKeyGuardthat automatically releases the lock when dropped. This design ensures safe, deterministic serialization of writes to the same key while allowing other keys to be accessed concurrently. The implementation usesDashMapfor thread-safe, atomic entry operations, preventing race conditions and TOCTOU issues.✅ Checks
ℹ Additional Information