I have already commit a pull request to fix this problem, see: https://github.com/apache/incubator-zeppelin/pull/267
2015-08-30 11:38 GMT+08:00 linxi zeng <linxizeng0...@gmail.com>: > hi, moon: > After using zeppelin server for some days, we often found that > paragraph can't run while the zeppelin server process is on, restart > interpreter is just not work. Then we find out that the > RemoteInterpreterServer is in deadlock, and can't be stopped by zeppelin > server. Unfortunately, this deadlocked RemoteInterpreterServer will still > hold the hadoop resources, we need to kill the process manually each time. > > We use jstack to monitor the RemoteInterpreterServer process, the key > information is like that: (you can see the detail info in: > https://issues.apache.org/jira/browse/ZEPPELIN-271) > > 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" > > >
