-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
gc_worker: compare locks by key and timestamp (#16536) #16948
gc_worker: compare locks by key and timestamp (#16536) #16948
Conversation
/run-all-tests |
@bb7133 Please merge it. |
/merge |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/run-all-tests |
@sre-bot merge failed. |
/run-integration-copr-test |
2 similar comments
/run-integration-copr-test |
/run-integration-copr-test |
/run-integration-copr-test |
/merge |
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
@sre-bot merge failed. |
/merge |
/run-all-tests |
@sre-bot merge failed. |
cherry-pick #16536 to release-4.0
Signed-off-by: youjiali1995 zlwgx1023@gmail.com
What problem does this PR solve?
Issue Number: close #16490
Problem Summary:
mergeReceiver
compares locks by key so that we only resolve the first lock. It's possible a key has locks with different timestamps:What is changed and how it works?
What's Changed:
Compare locks by key and timestamp.
Related changes
Check List
Tests
Release note
Fix the issue that Green GC misses locks when a key has locks with different timestamps.