[
https://issues.apache.org/jira/browse/IGNITE-6893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162843#comment-17162843
]
Stanislav Lukyanov commented on IGNITE-6893:
--------------------------------------------
I believe we don't need this feature in particular now that we have Failure
Handlers. If there is a Java deadlock it is almost a guarantee that it will
lead to a blocked system thread, which will trigger FH. How about we close this
[~avinogradov] [~andrey-kuznetsov]?
> Java Deadlocks monitoring
> -------------------------
>
> Key: IGNITE-6893
> URL: https://issues.apache.org/jira/browse/IGNITE-6893
> Project: Ignite
> Issue Type: Improvement
> Reporter: Anton Vinogradov
> Priority: Major
> Labels: iep-7
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
