Hi Moon,
Sorry for the late reply.
I would like to use bin/zeppelin-daemon.sh, because I want to keep it as
the background process while I can do some other work in the container.
I also tried to use `nohup bin/zeppelin.sh &` command, but still, once the
interpreter process is running in the
Hao Ren,
It looks like other interpreters are working even if Zeppelin is started
inside the container using "bin/zeppelin-daemon.sh start" command, except
for Spark interpreter. So I guess it is somehow related to Spark.
One question, do you have any particular reason try to use
Here is the ps tree for the two cases.
And I have no idea why Zeppelin fork some sub processes for STTY when
Zeppelin is hanging
* Working
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 1144 4 ?Ss 08:24 0:00 /dev/init
--
Hi,
I am testing zeppelin in docker container by using the official image:
https://hub.docker.com/r/apache/zeppelin/dockerfile
I notice that the Dockfile above is using "bin/zeppelin.sh" to start
zeppelin, instead of "bin/zeppelin-daemon start".
I am not clear on the difference between the two
