[jira] [Resolved] (IMPALA-7483) Abort stuck impalad if JVM deadlock is detected

["Tim Armstrong (JIRA)" <ji...@apache.org>]

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

Tim Armstrong resolved IMPALA-7483.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.1.0

> Abort stuck impalad if JVM deadlock is detected
> -----------------------------------------------
>
>                 Key: IMPALA-7483
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7483
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Backend
>    Affects Versions: Impala 3.1.0
>            Reporter: Tim Armstrong
>            Assignee: Tim Armstrong
>            Priority: Major
>             Fix For: Impala 3.1.0
>
>
> [~tlipcon] suggested this as a mitigation for IMPALA-7482 to get the cluster unstuck.
> The JVM exposes some functionality to detect deadlock threads: https://docs.oracle.com/javase/7/docs/api/java/lang/management/ThreadMXBean.html#findDeadlockedThreads()
> We could have a background thread try to detect java-level deadlocks.
> This comment in the docs is slightly offputting "This method is designed for troubleshooting use, but not for synchronization control. It might be an expensive operation." We should probably understand what this means and what the consequences are before running this always.
> One option is to only check for deadlocks if some operations except a performance threshold. The disadvantage of this is that we need to have thresholds for every operation that can deadlock.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org