Geek Answers Handbook

Zeppelin changes port already used by Spark Master

When I run zeppelin on AWS, it runs on port 8080, but there is Spark Master, so it says that the port is already in use ... I tried changing the port in zeppelin in the configuration files, in "zeppelin-site.xml.template"

<property> <name>zeppelin.server.port</name> <value>8050</value> <description>Server port.</description> </property>

I did this too in "zeppelin-env.sh.template" by adding the env line for the same port.

When I start zeppelin, I get OK, but if I see open ports, it doesn’t appear anywhere in 8050, so it looks like it’s still trying to deploy port 8080, where Spark Master ...

Someone who got zeppelin without ignoring the changed port?

thanks

+7
apache-spark apache-zeppelin
source share
4 answers

Most likely you need to copy the .template , for example. copy the modified zeppelin-env.sh.template to zeppelin-env.sh and zeppelin-site.xml.template to zeppelin-site.xml .

+11
source share

Indeed, both documented paths should work:

  • create conf/zeppelin-site.xml using the zeppelin.server.port property
  • create conf/zeppelin-env.sh and export the variable ZEPPELIN_PORT env

and restarting Zeppelin

+2
source share

From your zeppelin installation directory (example on my computer: 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 have access to it:

http: // localhost: 8180

+2
source share

The accepted answer seems a bit old, so I put here the solution I found if it is useful to others:

You can define variables (including port) either conf/zeppelin-env.sh , or in conf/zeppelin-site.xml . zeppelin-env takes precedence if both are defined.

A source:

http://zeppelin.apache.org/docs/snapshot/install/configuration.html

0
source share

More articles:


All Articles