Use MultiLockGuard to guarantee atomicity for multiple keys commands #1700
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.
In kvrocks, for multiple keys commands, we may break atomicity.
such as
ZUNION
,ZUNIONSTORE
,ZINTERSTORE
,SUNION
,SUNIONSTORE
,SINTER
,SINTERSTORE
,SDIFF
andSDIFFSTORE
.For
SDIFFSTORE destination key1 [key2 ...]
command, kvrocks willread key1, key2 ... orderly without any lock, and then restore the
diff into destination key. So maybe some keys may be changed when
we read them orderly, that breaks atomicity but redis can guarantee
atomicity.
In this PR, we are using
MultiLockGuard
to lock these keys beforewe read or write, so it is impossible to change these keys. This change
affects all commands listed previously.
Fixes #1692.