You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@critical27
This problem disappear after we we applied this patch #3141 . I highly doubt that this is a similar problem to #3018 , I don't keep the stack trace for #3018 , but I can remember that both of them blocked on raftLock_ , though at different places.
Describe the bug (must be provided)
Raft deadlock after stress test.
Your Environments (must be provided)
uname -a
g++ --version
orclang++ --version
lscpu
How To Reproduce(must be provided)
Steps to reproduce the behavior:
stop the stresser, we see one storage instance offline:
pstack shows that raft of that instance is blocked on
raftLock_
:strace shows that thread 3413758(the thread raft task resides) is blocked on futex forever:
# strace -p 3413758 strace: Process 3413758 attached futex(0x7f4d384be150, FUTEX_WAIT_PRIVATE, 2, NULL
full pstack output is provided below:
3413698.txt
Expected behavior
all cluster peers still running. healthly。
Additional context
Provide logs and configs, or any other context to trace the problem.
The text was updated successfully, but these errors were encountered: