[jira] [Resolved] (IMPALA-7482) Deadlock with unknown lock holder in JVM in java.security.Provider.getService()

["Joe McDonnell (Jira)" <ji...@apache.org>]

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

Joe McDonnell resolved IMPALA-7482.
-----------------------------------
    Fix Version/s: Not Applicable
       Resolution: Cannot Reproduce

> Deadlock with unknown lock holder in JVM in java.security.Provider.getService()
> -------------------------------------------------------------------------------
>
>                 Key: IMPALA-7482
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7482
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 3.0
>            Reporter: Tim Armstrong
>            Assignee: Joe McDonnell
>            Priority: Critical
>              Labels: hang
>             Fix For: Not Applicable
>
>         Attachments: vb1220-jstack2.out
>
>
> We've seen several instances of these mystery deadlocks in impalad's embedded JVM. The signature is a deadlock stemming from sun.security.provider.Sun being locked by an unknown owner.
> {noformat}
> Found one Java-level deadlock:
> =============================
> "Thread-24":
>   waiting to lock monitor 0x0000000012364688 (object 0x000000008027ef30, a sun.security.provider.Sun),
>   which is held by UNKNOWN_owner_addr=0x0000000014120800
> {noformat}
> If this happens in HDFS, it causes HDFS I/O to hang and queries to get stuck. If it happens in the Kudu client it also causes hangs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)