Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Java Level Deadlocks
Description
This situation occurs if user or Ignite comes to a Java-level deadlock due to a bug in code - reverse order synchronized(mux1) {synchronized (mux2) {}} sections, reverse order reentrant locks, etc.
Detection and Solution
This most likely cannot be resolved automatically and will require JVM restart.
We can implement periodical threaddumps analysis and detect the deadlock.
Report
Deadlock should be reported to the logs.
Web Console should fire an alert on java deadlock detection and display a warning on UI.
Attachments
Issue Links
- Is contained by
-
IGNITE-5811 Detect internal Ignite problems (java-level deadlock, hangs, etc) and act according to a policy configured.
- Resolved
- links to