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

Posted to dev@zeppelin.apache.org by "SunShun (Jira)" <ji...@apache.org> on 2022/01/28 10:13:00 UTC

[jira] [Created] (ZEPPELIN-5644) Optimize the interpreter execution process

SunShun created ZEPPELIN-5644:
---------------------------------

             Summary: Optimize the interpreter execution process
                 Key: ZEPPELIN-5644
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-5644
             Project: Zeppelin
          Issue Type: Improvement
          Components: Interpreters
    Affects Versions: 0.10.0
            Reporter: SunShun
             Fix For: 0.11.0


Hi, I found some issues when trying to investigate the spark OOM issue:
 # Thread of interpreter executor hasn't been closed when interpreter is closed;
 # When restart from notebook page, the Zeppelin Daemon are going to close all interpreters, while Zeppelin interpreter server only close the opened interpreters indeed, and it causes in duplicated interpreters kept in server side;
 # After one user starts multi spark sessions, duplicated loaded Classes are founded for the innerScalaInterpreter inside the spark interpreter, since the threads are created in different sub threads, and they don't share loaded class.

I will create a PR to solve the above issues.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)