Github user sadhen commented on the issue:
https://github.com/apache/zeppelin/pull/2539
@zjffdu
It won't satisfy my need.
You may understand my concerns when you start dockerizing Zeppelin.
And these days, I encounter another dockerization problem. If I put
interpreter and server processes all in one container, the interpreter process
will run out of memory. My final solution is deploying interpreters elsewhere.
```
ERROR [2017-08-24 00:12:17,391] ({Thread-0}
TThreadPoolServer.java[serve]:194) - ExecutorService threw error:
java.lang.OutOfMemoryError: unable to create new native thread
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:714)
at
java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:950)
at
java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1368)
at
org.apache.thrift.server.TThreadPoolServer.serve(TThreadPoolServer.java:168)
at
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer.run(RemoteInterpreterServer.java:104)
INFO [2017-08-24 00:24:30,979] ({Thread-0}
RemoteInterpreterServer.java[run]:103) - Starting remote interpreter server on
port 40623
```
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
