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
KeyDB 5.1.1 periodically crashes with assertion failed #107
Comments
EDIT: Missed your link to the log |
I mixed this up with a different bug. This bug is still active. |
We're crashing because the client pointer is NULL. All the codepaths that could lead here should be crashing much earlier so I'm still working on sorting out how this could happen. Are you running any modules? |
Great news, I was able to repro this and get a fix. The fix is in unstable and will be included in the next release. unstable docker rebuilds nightly if you would like to try it. The issue is caused if a new client connects around the time we finish an AOF rewrite. A dangling fd for the AOF rewrite gets used for the new client resulting in the function being called with a NULL client pointer. |
I migrated from Redis few days ago, code from RELEASE_5. All work well except such crashes. My setup is active-active replication between 2 nodes, many write (non-overlaping) and read operations on both nodes.
Full log of last crash:
bug.txt
From dmesg:
Address of assertion:
Please let me know if you need something more.
The text was updated successfully, but these errors were encountered: