We are having the same problem as described in 
https://issues.apache.org/jira/browse/ZEPPELIN-2197

We have one interpreter each user and we have a lot of users. Basically 
resources got sucked up by all those idled interpreters.
There is one comment --- Kill it after idle for a while. How do you tell 
whether an interpreter is idled?
So does anyone has any workaround in terms of how to manage the lifecycle of 
interpreters?

Reply via email to