Installing Apache Zeppelin
Also available as:

Enable HDFS Storage when Upgrading to HDP-2.6.3+

Perform the following steps to enable HDFS storage when upgrading to HDP 2.6.3+ from earlier versions of HDP.

  1. Before upgrading Zeppelin, perform the following steps as the Zeppelin service user.
    1. Create the /user/zeppelin/conf and /user/zeppelin/notebook directories in HDFS.
      hdfs dfs -ls /user/zeppelin
      drwxr-xr-x   - zeppelin hdfs          0 2018-01-20 04:17 /user/zeppelin/conf
      drwxr-xr-x   - zeppelin hdfs          0 2018-01-20 03:40 /user/zeppelin/notebook
    2. Copy all notebooks from the local Zeppelin server (for example, /usr/hdp/ to the /user/zeppelin/notebook directory in HDFS.
      hdfs dfs -ls /user/zeppelin/notebook
      drwxr-xr-x   - zeppelin hdfs          0 2018-01-19 01:40 /user/zeppelin/notebook/2A94M5J1Z
      drwxr-xr-x   - zeppelin hdfs          0 2018-01-19 01:40 /user/zeppelin/notebook/2BWJFTXKJ
    3. Copy the interpreter.json and notebook-authorization.json files from the local Zeppelin service configuration directory (/etc/zeppelin/conf) to the/user/zeppelin/conf directory in HDFS.
      hdfs dfs -ls /user/zeppelin/conf
      -rw-r--r--   3 zeppelin hdfs     284091 2018-01-22 23:28 /user/zeppelin/conf/interpreter.json
      -rw-r--r--   3 zeppelin hdfs     123849 2018-01-22 23:29 /user/zeppelin/conf/notebook-authorization.json
  2. Upgrade Ambari.
  3. Upgrade HDP and Zeppelin. During the upgrade, verify that the following configuration settings are present in Ambari for Zeppelin. = org.apache.zeppelin.notebook.repo.FileSystemNotebookRepo
    zeppelin.config.fs.dir = conf

    If necessary, add or update these configuration settings as shown above.

  4. After the upgrade is complete:
    1. Log on to the Zeppelin server and verify that the following properties exist in the /etc/zeppelin/conf/zeppelin-site.xml file. The actual value for the keytab file and principal name may be different for your cluster.
    2. Check the Zeppelin Interpreter page to see if any interpreter (e.g. the Livy interpreter) is duplicated. This may happen in some cases. If duplicate interpreter entries are found, perform the following steps:
      1. Backup and delete the interpreter.json file from HDFS (/user/zeppelin/conf/interpreter.json) and from the local Zeppelin server.
      2. Restart the Zeppelin service.
      3. Verify that the duplicate entries no longer exist.
      4. If any custom interpreter settings were present before the upgrade, add them again via the Zeppelin interpreter UI page.
    3. Verify that your existing notebooks are available on Zeppelin.
    When an existing notebook is opened for the first time after the upgrade, it may ask you to save the interpreters associated with the notebook.