Nevermind. I figured this out. It works as expected. Great feature!
--
Ruslan Dautkhanov
On Mon, Feb 12, 2018 at 5:16 PM, Jeff Zhang wrote:
>
> Right, you spark interpreter should be killed in 10 minutes of idless,
> could you attach your full zeppelin server log & spark interpreter log ?
>
I believe this is spark bug
https://issues.apache.org/jira/browse/SPARK-18880
Brandon Barker 于2018年2月13日周二 上午9:42写道：
> Hi,
>
> I'd like to try zeppelin but require the use of external dependencies. It
> seems ideal to do this on a notebook-by-notebook basis for portability, and
> also for the c
Hi,
I'd like to try zeppelin but require the use of external dependencies. It
seems ideal to do this on a notebook-by-notebook basis for portability, and
also for the current docker setup, since adding dependencies in the
interpreter configuration isn't persisted when the container goes away.
Cur
Right, you spark interpreter should be killed in 10 minutes of idless,
could you attach your full zeppelin server log & spark interpreter log ?
Ruslan Dautkhanov 于2018年2月13日周二 上午7:45写道：
> Trying out below settings for the new TimeoutLifecycleManager :
>
>
>> zeppelin.interpreter.lifecyclemanager
Trying out below settings for the new TimeoutLifecycleManager :
> zeppelin.interpreter.lifecyclemanager.class
> org.apache.zeppelin.interpreter.lifecycle.TimeoutLifecycleManager
> zeppelin.interpreter.lifecyclemanager.timeout.checkinterval
> 6
> zeppelin.interpreter.lifecyclemanager.timeout.t
t do anything.
INFO [2018-02-12 01:12:57,129] ({pool-1-thread-4}
> RemoteInterpreterServer.java[cancel]:674) - cancel
> org.apache.zeppelin.spark.IPySparkInterpreter 20180212-001114_111220272
> INFO [2018-02-12 01:12:57,134] ({pool-1-thread-4}
> Logging.scala[logInfo]:54) - Asked to cance
