Moving Zeppelin notebooks to local storage from HDFS if need to isolate the zeppelin nodes

[#1]

Hi All, 
I have faced some issues. We want to dedicate one of the Zeppelin node to a different agency. So, if they create any notebook, those are getting synced to every one after a restart because we are using the central storage system as HDFS. So, Zeppelin nodes are picking all notebooks and interpreter settings from the HDFS single path. To avoid this, we isolated the settings and configurations by changing Zeppelin to use the local storage, so each node will act independently. For the same, the following are helpful steps in case anyone is facing the same. Thanks.

1. Verify the procedures in a lower environment before executing the same in production.

   sudo -u <zeppelin-user> mkdir -p /var/lib/zeppelin/conf /var/lib/zeppelin/notebook
   kinit <zeppelin-user>
   hdfs dfs -get "/user/zeppelin/notebook/*" /var/lib/zeppelin/notebook
   hdfs dfs -get /user/zeppelin/conf/notebook-authorization.json /var/lib/zeppelin/conf​

2. In the Zeppelin configuration page, search for and verify the following settings:

   zeppelin.notebook.storage=org.apache.zeppelin.notebook.repo.FileSystemNotebookRepo
   zeppelin.config.fs.dir = file:///var/lib/zeppelin/conf
   zeppelin.notebook.dir = file:///var/lib/zeppelin/notebook​

3. If the settings are missing or incorrect, add or update them to the above values.
4. In the Zeppelin UI, check the Interpreters page for any duplicate entries, If any.
   duplicates exist:
   1. Backup and then delete the interpreter.json file from HDFS
      (/user/zeppelin/conf/interpreter.json) and from the local
      filesystem on the Zeppelin server host (/var/lib/zeppelin/conf/interpreter.json).
   2. Restart the Zeppelin service in Ambari.
   3. In the Zeppelin UI, confirm that the duplicate entries no longer exist.
   4. If any custom interpreter settings are missing, add them again from the
      Interpreters page.
   5. Verify that your existing notebooks are still available.

Disclaimer: 

This article is contributed by an external user. The steps may not be verified by Cloudera and may not be applicable for all use cases and are very specific to a particular distribution. Please follow with caution and at your own risk. If needed, raise a support case to get the confirmation.