Frank Rosner created ZEPPELIN-1938:
--------------------------------------
Summary: Zeppelin does not close files in local-repo correctly /
tries to delete them when changing interpreter settings
Key: ZEPPELIN-1938
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1938
Project: Zeppelin
Issue Type: Bug
Affects Versions: 0.6.2
Reporter: Frank Rosner
h4. Problem
Sometimes when we are trying to change some interpreter settings after already
working with Zeppelin for some time we get an error message that says:
{noformat}
Unable to delete file:
/usr/local/zeppelin/local-repo/2BGVKK81C/.nfs0000000000103329930200100ac
{noformat}
Then the interpreter settings are not changed and Zeppelin starts behaving
weird. After a restart it works again.
These files are created by NFS 3 which we use to store our configuration,
notebooks, local repo, etc. They are created when files are opened afaik. The
fact that it tries to delete them but cannot looks like a problem of Zeppelin
not closing some files there but trying to delete them in the meantime.
h4. Questions
- Why does Zeppelin want to delete this files when making changes to the
interpreter configuration?
- As making changes to the interpreter settings is working after a restart but
not when working with Zeppelin for a while could it be that it is related to
artifacts (jars etc.) being downloaded to the local repo? Why does changing the
interpreter settings affect the local repo in the first place?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
