Tried this again yesterday and seems like it was an ephemeral issue with running 0.5.6 and 0.6.0 after each other.
— Pedro Rodriguez PhD Student in Large-Scale Machine Learning | CU Boulder Systems Oriented Data Scientist UC Berkeley AMPLab Alumni pedrorodriguez.io | 909-353-4423 github.com/EntilZha | LinkedIn On July 7, 2016 at 10:21:25 AM, Pedro Rodriguez (ski.rodrig...@gmail.com) wrote: I am working on upgrading to 0.6.0 and running into issues where I define zeppelin-env.sh but Zeppelin doesn't seem to pickup values from there. Here is what I have done 1. Download copy of zeppelin binaries and unpack 2. Copy conf/zeppelin-site.xml.template and conf/zeppelin-env.sh.template to the files without .template 3. Modified the site file to configure S3 access (works) 4. Modify zeppelin-env.sh file with: export SPARK_HOME=/path/to/spark export MASTER=spark://sparkdomain.com:7077 When I start the Zeppelin server it seems to fall back to local[*] which is the default making me think it is not picking up the env file. S3 is working so it is picking up the xml file. I also tried a property like below but this didn't work either: <property> <name>master</name> <value>spark://10.100.11.198</value> <description>Spark Master</description> </property> Any ideas? The settings seemed to work in 0.5.6 -- Pedro Rodriguez PhD Student in Distributed Machine Learning | CU Boulder UC Berkeley AMPLab Alumni ski.rodrig...@gmail.com | pedrorodriguez.io | 909-353-4423 Github: github.com/EntilZha | LinkedIn: https://www.linkedin.com/in/pedrorodriguezscience
