I think it's really a mortal blow to livy about the repl scene . What I can do
, I think is to monitoring spark metrics, when the driver's memory was used to
a high leve I will isolate the session.
2018-11-14
lk_hadoop
发件人："Harsch, Tim"
发送时间：2018-11-14 05:52
主题：Re: about LI
While it's true LIVY-424 creates a session leak due to REPL leak in Scala it's
not the only thing that can. I've run hundreds of simple scala commands and
the leak is only mild/moderate. However, some scala commands can be really
problematic. For instance
import org.apache.spark.sql._
tainer killed on request. Exit code is 143
Container exited with a non-zero exit code 143
Failing this attempt. Failing the application.
2018-11-12
lk_hadoop
发件人："Rabe, Jens"
发送时间：2018-11-12 14:55
主题：RE: about LIVY-424
收件人："user@livy.incubator.apache.org"
抄送：
Do y
If you're hitting the problem of LIVY-424, this is exactly a Scala REPL
issue, not a Livy issue, it is hard to fix in the Livy side.
lk_hadoop 于2018年11月12日周一 上午9:37写道：
> hi,all:
> I meet this issue https://issues.apache.org/jira/browse/LIVY-424
> , anybody know how to resolve it?
>
