Hi Paul,
What interpreter do you find that is not killed ? Unfortunately there's no
log for the lasttimeusing (I should add that for debugging).
And let me know if it is easy to reproduce.
Paul Brenner 于2018年4月5日周四 下午11:21写道：
> Wow, looks like I was wrong. TimeoutLifecycleManager is definitel
Wow, looks like I was wrong. TimeoutLifecycleManager is definitely killing some
idle interpreters, just not all idle interpreters. I have no idea what could be
causing the difference. It looks like the manager is pulling some value for
lasttimeusing here
https://github.com/apache/zeppelin/blob/
Hi Jeff,
If I am using zeppelin in an AWS environment what type of metric could I
gather using cloudformation scripts?
On Thu, Apr 5, 2018 at 10:43 AM, Jeff Zhang wrote:
>
> Try to look for logs like following in zeppelin server log file. Make sure
> you are using TimeoutLifecycleManager instead
Try to look for logs like following in zeppelin server log file. Make sure
you are using TimeoutLifecycleManager instead of NullLifecycleManager
INFO [2018-04-04 18:12:26,209] ({main}
InterpreterSettingManager.java[]:170) - Using LifecycleManager:
org.apache.zeppelin.interpreter.lifecycle.NullLife
We finally got our team up and running on a version of Zeppelin 0.8 built from
source. However, we can’t seem to get TimeoutLifecycleManager manager to kill
idle interpreters. When I look at the config page I see:
zeppelin.interpreter.lifecyclemanager.class
org.apache.zeppelin.interpreter.lifecy
