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
Mutex deadlock / race in API node #3583
Comments
The stack trace takes place while the node is shutting down. We can add a timeout on the thread join, but this seems like a fairly minimal issue. The deadlock is not occurring while the node is operational. If you don't believe the node should have been shutting down, there may be a different issue, but this is not enough information to diagnose the problem. |
Hm, yes, unfortunately I tried to shut it down before taking the stack trace, I should have done it the other way around. If it occurs again I will take the trace while it's halted. |
Attached is another log from another API node (different one) taken while stuck. |
I am not seeing any deadlock here... The write thread:
It is not waiting on a lock. There are 54 instances of API threads waiting on futures in The node might just be reaching capacity and beginning to slow down. If it continues happening, more stack traces would be useful. |
debug for all threads.txt
A highly used, non-mira "full node" API deadlocked with the included backtrace.
The main thread is stuck as follows:
Locks should have timeouts.
The text was updated successfully, but these errors were encountered: