You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zeppelin.apache.org by "zenglinxi (JIRA)" <ji...@apache.org> on 2015/08/30 05:19:45 UTC

[jira] [Created] (ZEPPELIN-271) RemoteInterpreterServer deadlock

zenglinxi created ZEPPELIN-271:
----------------------------------

             Summary: RemoteInterpreterServer deadlock
                 Key: ZEPPELIN-271
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-271
             Project: Zeppelin
          Issue Type: Bug
            Reporter: zenglinxi
            Priority: Critical


After using zeppelin server for some days,  we often found that paragraph can't run while the zeppelin server process is on, and run zeppelin-daemon.sh restart is not work. Then we find zhe RemoteInterpreterServer is in deadlock, and can't be stopped by zeppelin server.
We use jstack to monitor the RemoteInterpreterServer process, the key information is like that:

Found one Java-level deadlock:
=============================
"pool-1-thread-8":
  waiting to lock monitor 0x00007f58a8006178 (object 0x00000000ebb9d298, a org.apache.zeppelin.interpreter.InterpreterGroup),
  which is held by "pool-1-thread-4"
"pool-1-thread-4":
  waiting to lock monitor 0x00007f58a8002f48 (object 0x00000000ecbd8008, a org.apache.zeppelin.interpreter.ClassloaderInterpreter),
  which is held by "pool-1-thread-2"
"pool-1-thread-2":
  waiting to lock monitor 0x00007f58a8006178 (object 0x00000000ebb9d298, a org.apache.zeppelin.interpreter.InterpreterGroup),
  which is held by "pool-1-thread-4"




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)