Here is configurations related to Helium:
ZEPPELIN_HELIUM_REGISTRY("zeppelin.helium.registry", "helium," +
HELIUM_PACKAGE_DEFAULT_URL),
ZEPPELIN_HELIUM_NODE_INSTALLER_URL("zeppelin.helium.node.installer.url",
"https://nodejs.org/dist/";),
ZEPPELIN_HELIUM_NPM_INSTALLER_URL("zeppelin.helium.
I seem to have fixed this by upgrading Zeppelin to use thrift 0.9.3. I
took the v0.8.1 tag and then cherry picked this:
https://github.com/apache/zeppelin/commit/4b436ca22091baab8170fa80713e86918db5b987
I note that the HDP Zeppelin distro already has this commit included.
James
On Thu, 21 Mar 2
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
-- /usr/loc
Hi,
We are trying to set up an additional instance of zeppelin and load balance
the backend using an Nginx proxy and iphashing.
The set up so far looks good.We are using CEPH storage to store the run
time configurations and share the same volume across both the instances.So
interpreter.json,noteboo