Have similar experience, although hard to say what's the reason as all
process supposed to killed, as Moon pointed out.
Also noticed that with `mvn tests`, after almost every run, there are 1-2
zombie RemoteInterpreter processes hanging around.
--
Alex
On Fri, Dec 16, 2016 at 11:24 AM, Jeff Zhang
I believe I see this before too.
Luciano Resende 于2016年12月16日周五 上午10:17写道：
> I have also seen similar issues even using zeppelin-ddeamon but didn't
> have much time to investigate the issue when it was happening to me.
>
> On Thu, Dec 15, 2016 at 12:15 PM Ruslan Dautkhanov
> wrote:
>
> Moon,
>
I have also seen similar issues even using zeppelin-ddeamon but didn't have
much time to investigate the issue when it was happening to me.
On Thu, Dec 15, 2016 at 12:15 PM Ruslan Dautkhanov
wrote:
> Moon,
>
> > ZeppelinServer try to terminate interpreter process when shutting down
> [1].
>
> Un
Moon,
> ZeppelinServer try to terminate interpreter process when shutting down
[1].
Unfortunatally, this does not happen all the time.
I have seen zombie spark interpreter processes many times.
As a double conirmation - I see spark yarn application was still running.
> Also bin/zeppelin-deamon.s
Hi,
ZeppelinServer try to terminate interpreter process when shutting down [1].
Also bin/zeppelin-deamon.sh script clean up if some processes are left [2].
If some processes are remained after shutting down Zeppelin, that's not an
expected result.
Thanks,
moon
[1]
https://github.com/apache/zepp
How to make Interpreter processes terminate if Zeppelin server exits?
When we restart Zeppelin server (main process), in many cases, Interpreter
process keeps running, essential becoming a zombie processes.
In case of Spark interpreter, it also holds SparkContext - consuming
server-side
resources
