ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitriy Pavlov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-6893) Java Deadlocks monitoring
Date Tue, 26 Jun 2018 16:09:11 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-6893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dmitriy Pavlov updated IGNITE-6893:
-----------------------------------
    Fix Version/s:     (was: 2.6)
                   2.7

> Java Deadlocks monitoring
> -------------------------
>
>                 Key: IGNITE-6893
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6893
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Anton Vinogradov
>            Assignee: Andrey Kuznetsov
>            Priority: Major
>              Labels: iep-7
>             Fix For: 2.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
(v7.6.3#76005)

Mime
View raw message