-
Notifications
You must be signed in to change notification settings - Fork 62
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
Possible segfault? #50
Comments
Got a second case, at least! |
Oh hey, this one's got an actual stacktrace!
|
Huh, and here's another, from raft_node_set_next_idx--maybe a different bug?
|
This looks resolved as of e0123a9. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With redis f88f866 and redis-raft 2d1cf30, tests with process pauses, crashes, network partitions, and membership changes could rarely cause nodes to exit with a nil assertion failure, no stacktrace, and signal 11, which is SIGSEGV, right?
20200509T141124.000-0400.zip
I recognize this is incredibly unhelpful, and I am SO sorry to file this. Maybe my cluster is cursed.
The text was updated successfully, but these errors were encountered: