[
https://issues.apache.org/jira/browse/IGNITE-6893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-6893:
-------------------------------------
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.
> Provide metric to monitor Java Deadlocks
> -----------------------------------------
>
> Key: IGNITE-6893
> URL: https://issues.apache.org/jira/browse/IGNITE-6893
> Project: Ignite
> Issue Type: Improvement
> Reporter: Anton Vinogradov
> Assignee: Andrey Kuznetsov
> 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
(v6.4.14#64029)
