Joathan Levenson created ZEPPELIN-4798:
------------------------------------------
Summary: Can't launch python.docker interpreter in 0.9.0 running
on k8s
Key: ZEPPELIN-4798
URL: https://issues.apache.org/jira/browse/ZEPPELIN-4798
Project: Zeppelin
Issue Type: Bug
Components: Interpreters
Affects Versions: 0.9.0
Reporter: Joathan Levenson
When attempting to launch a python.docker interpreter in 0.9.0 running on
kubernetes, the following error is being presented:
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was
removed in 8.0OpenJDK 64-Bit Server VM warning: ignoring option
MaxPermSize=512m; support was removed in 8.0 WARN [2020-05-04 08:56:31,046]
(\{main} ZeppelinConfiguration.java[create]:159) - Failed to load
configuration, proceeding with a default INFO [2020-05-04 08:56:31,104]
(\{main} ZeppelinConfiguration.java[create]:171) - Server Host: 0.0.0.0 INFO
[2020-05-04 08:56:31,105] (\{main} ZeppelinConfiguration.java[create]:173) -
Server Port: 8080 INFO [2020-05-04 08:56:31,105] (\{main}
ZeppelinConfiguration.java[create]:177) - Context Path: / INFO [2020-05-04
08:56:31,110] (\{main} ZeppelinConfiguration.java[create]:178) - Zeppelin
Version: 0.9.0-preview1 INFO [2020-05-04 08:56:31,111] (\{main}
RemoteInterpreterServer.java[<init>]:161) - Starting remote interpreter server
on port 0, intpEventServerAddress: zeppelin-server.zeppelin.svc:12320 INFO
[2020-05-04 08:56:31,166] (\{main} RemoteInterpreterServer.java[<init>]:188) -
Launching ThriftServer at 10.136.129.122:12321 INFO [2020-05-04 08:56:33,847]
(\{pool-1-thread-3} RemoteInterpreterServer.java[createInterpreter]:408) -
Instantiate interpreter org.apache.zeppelin.python.PythonInterpreterDEBUG
[2020-05-04 08:56:33,847] (\{pool-1-thread-3}
InterpreterGroup.java[addInterpreterToSession]:91) - Add Interpreter
org.apache.zeppelin.python.PythonInterpreter to session shared_session INFO
[2020-05-04 08:56:33,856] (\{pool-1-thread-3}
RemoteInterpreterServer.java[createInterpreter]:408) - Instantiate interpreter
org.apache.zeppelin.python.IPythonInterpreterDEBUG [2020-05-04 08:56:33,856]
(\{pool-1-thread-3} InterpreterGroup.java[addInterpreterToSession]:91) - Add
Interpreter org.apache.zeppelin.python.IPythonInterpreter to session
shared_session INFO [2020-05-04 08:56:33,859] (\{pool-1-thread-3}
RemoteInterpreterServer.java[createInterpreter]:408) - Instantiate interpreter
org.apache.zeppelin.python.PythonInterpreterPandasSqlDEBUG [2020-05-04
08:56:33,860] (\{pool-1-thread-3}
InterpreterGroup.java[addInterpreterToSession]:91) - Add Interpreter
org.apache.zeppelin.python.PythonInterpreterPandasSql to session shared_session
INFO [2020-05-04 08:56:33,864] (\{pool-1-thread-3}
RemoteInterpreterServer.java[createInterpreter]:408) - Instantiate interpreter
org.apache.zeppelin.python.PythonCondaInterpreterDEBUG [2020-05-04
08:56:33,864] (\{pool-1-thread-3}
InterpreterGroup.java[addInterpreterToSession]:91) - Add Interpreter
org.apache.zeppelin.python.PythonCondaInterpreter to session shared_session
INFO [2020-05-04 08:56:33,875] (\{pool-1-thread-3}
RemoteInterpreterServer.java[createInterpreter]:408) - Instantiate interpreter
org.apache.zeppelin.python.PythonDockerInterpreterDEBUG [2020-05-04
08:56:33,876] (\{pool-1-thread-3}
InterpreterGroup.java[addInterpreterToSession]:91) - Add Interpreter
org.apache.zeppelin.python.PythonDockerInterpreter to session
shared_sessionDEBUG [2020-05-04 08:56:33,939] (\{pool-1-thread-3}
RemoteInterpreterServer.java[interpret]:523) - st:activate
gcr.io/tensorflow/tensorflow:latest INFO [2020-05-04 08:56:33,961]
(\{pool-1-thread-5} SchedulerFactory.java[<init>]:62) - Scheduler Thread Pool
Size: 100ERROR [2020-05-04 08:56:33,971] (\{pool-1-thread-5}
ProcessFunction.java[process]:47) - Internal error processing
getStatusjava.lang.NullPointerException at
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer.getStatus(RemoteInterpreterServer.java:904)
at
org.apache.zeppelin.interpreter.thrift.RemoteInterpreterService$Processor$getStatus.getResult(RemoteInterpreterService.java:1711)
at
org.apache.zeppelin.interpreter.thrift.RemoteInterpreterService$Processor$getStatus.getResult(RemoteInterpreterService.java:1691)
at
org.apache.zeppelin.shaded.org.apache.thrift.ProcessFunction.process(ProcessFunction.java:38)
at
org.apache.zeppelin.shaded.org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:38)
at
org.apache.zeppelin.shaded.org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:313)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)ERROR [2020-05-04 08:56:34,004]
(\{pool-1-thread-3} ProcessFunction.java[process]:47) - Internal error
processing interpretjava.lang.NullPointerException at
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer.interpret(RemoteInterpreterServer.java:538)
at
org.apache.zeppelin.interpreter.thrift.RemoteInterpreterService$Processor$interpret.getResult(RemoteInterpreterService.java:1560)
at
org.apache.zeppelin.interpreter.thrift.RemoteInterpreterService$Processor$interpret.getResult(RemoteInterpreterService.java:1540)
at
org.apache.zeppelin.shaded.org.apache.thrift.ProcessFunction.process(ProcessFunction.java:38)
at
org.apache.zeppelin.shaded.org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:38)
at
org.apache.zeppelin.shaded.org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:313)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)DEBUG [2020-05-04 08:56:34,243]
(\{pool-1-thread-3} RemoteInterpreterServer.java[resourcePoolGetAll]:1014) -
Request resourcePoolGetAll from ZeppelinServer
Is it possible to launch this interpreter in 0.9.0 on k8s? Has this
functionality been implemented? I have noted that the python docker interpreter
executes a "docker run ..." command, instead of launching a new k8s pod?
Thank you
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
