When I start zeppelin on AWS, It starts on port 8080, but there is Spark Master so it says port already in use... I tried changing port in zeppelin in config files, in "zeppelin-site.xml.template"
<property>
<name>zeppelin.server.port</name>
<value>8050</value>
<description>Server port.</description>
</property>
I made it too in "zeppelin-env.sh.template" adding the env line for the same port.
When I start zeppelin, I get OK, but if I see the open ports, It doesn't appear 8050 anywhere, so looks like It is still trying to deploy on port 8080, where Spark Master is...
Someone who got zeppelin not ignoring changed port?
Thanks
You can restart the interpreter for the notebook in the interpreter bindings (gear in upper right hand corner) by clicking on the restart icon to the left of the interpreter in question (in this case it would be the spark interpreter).
You likely need to copy the .template files, e.g. copy your modified zeppelin-env.sh.template to zeppelin-env.sh and zeppelin-site.xml.template to zeppelin-site.xml.
From your zeppelin installation dir (example on my computer its: zeppelin-0.7.3-bin-all):
cp conf/zeppelin-env.sh.template conf/zeppelin-env.sh
vi conf/zeppelin-env.sh
Add the following parameter:
export ZEPPELIN_PORT=8180 # Add this line to zeppelin-env.sh
restart zeppelin you should now be able to access it over:
http://localhost:8180
Indeed, both documented ways should work:
conf/zeppelin-site.xml with zeppelin.server.port propertyconf/zeppelin-env.sh and export ZEPPELIN_PORT env variable and restarting Zeppelin
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With