-
Notifications
You must be signed in to change notification settings - Fork 968
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
BZPop bug #3276
Comments
We should not put private links in our public repo (for security considerations). |
@adiholden @romange I have found only one possible issue. We have 2 steps:
|
I haven't found using of cluster, replication but the save operation happened on July 10, 2024 2:59:31 PM (GMT) |
I've found one more bug with KEY_MOVE error and have fixed it #3334 But it looks like we have at least one more |
I haven't found the real reason for this bug, but it looks like the execution order was next:
The problem is that I don't see how the 3rd step can happen.
|
ok, how can you prove that 2 has happened, and it was due to RegisterBreakHook? |
coord_state=6 means that the operation was canceled, I think about RegisterBreakHook because we don't have a replication and a cluster so only one option is left |
Based on the logs... isn't the key an empty string? |
I took it into account that is why I have written about the 3rd step |
Fixed with #3371 |
E20240706 06:12:17.647733 2255 zset_family.cc:1343] BUG: Callback didn't run! BLOCK//claimed=1 coord_state=6 local_res=0/
E20240706 06:12:11.367316 2255 zset_family.cc:1343] BUG: Callback didn't run! BLOCK//claimed=1 coord_state=6 local_res=0/
The text was updated successfully, but these errors were encountered: