12:55 PM
To: Silvio Fiorito<mailto:silvio.fior...@granturing.com>;
users@zeppelin.incubator.apache.org<mailto:users@zeppelin.incubator.apache.org>
Subject: Re: Spark interpreter idle timeout
Thank you Silvio.
I have not actually tried dynamic allocation (it's not trivial to use an
process to determine if a note is running, when it has last ran, and
then restart the interpreter.
From: Silvio Fiorito <silvio.fior...@granturing.com>
Sent: Friday, March 4, 2016 9:05 AM
To: users@zeppelin.incubator.apache.org; Dylan Meissner
Subject: Re: Spar
o:
"users@zeppelin.incubator.apache.org<mailto:users@zeppelin.incubator.apache.org>"
<users@zeppelin.incubator.apache.org<mailto:users@zeppelin.incubator.apache.org>>
Subject: Spark interpreter idle timeout
Greetings,
We run multiple Zeppelin's per user in a Mesos cluster. T
Greetings,
We run multiple Zeppelin's per user in a Mesos cluster. The Mesos Marathon
framework hosts the Zeppelin servers, and running a note causes a Spark
framework to start a Spark context to distribute the workload described in the
notes. This works well for us.
However, when notebooks
