[jira] [Commented] (IGNITE-6893) Java Deadlocks monitoring

["Stanislav Lukyanov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-6893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17319650#comment-17319650 ] 

Stanislav Lukyanov commented on IGNITE-6893:
--------------------------------------------

We don't only check for starvation, we check for any hanging Ignite threads with the thread heartbeats. The only way we may miss a deadlock is if it is in a user's thread. I don't think Ignite should be responsible for finding deadlocks in the threads it doesn't manage.

> Java Deadlocks monitoring
> -------------------------
>
>                 Key: IGNITE-6893
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6893
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Anton Vinogradov (Obsolete, actual is "av")
>            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)