-
Notifications
You must be signed in to change notification settings - Fork 455
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
Blocking commands may block permanently due to lost wakeup #2473
Labels
bug
type bug
Comments
@PokIsemaine I'm not sure if I understood your point correctly:
Is that right? |
Yeah |
I see. Thank you for raising this issue. I knew this issue indeed, but didn't find a proper way to solve the data race. It's nice to have an issue to track this. |
/assign |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Search before asking
Version
unstable
Minimal reproduce step
I discovered this issue while testing a PR(#2332), even though the PR increased the likelihood of it occurring, the problem actually existed beforehand.
It is difficult to reproduce manually without modifying the code, and it almost exclusively occurs during Go's integration tests.
Here's an example with
TestRegression
:By printing some information, I was able to trace the error:
The issue occurs here:
To manually reproduce the issue consistently, you can add a sleep and complete a PUSH within 5 seconds:
What did you expect to see?
Blocking commands will not be blocked after new key values are added.
What did you see instead?
Blocking command blocks permanently.
Anything Else?
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: