You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by "Frank Rosner (JIRA)" <ji...@apache.org> on 2017/01/11 15:50:58 UTC

[jira] [Created] (ZEPPELIN-1939) Imported and scheduled notebooks getting deleted from the filesystem

Frank Rosner created ZEPPELIN-1939:
--------------------------------------

             Summary: Imported and scheduled notebooks getting deleted from the filesystem
                 Key: ZEPPELIN-1939
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1939
             Project: Zeppelin
          Issue Type: Bug
    Affects Versions: 0.6.2
            Reporter: Frank Rosner


h4. Problem

We are facing the problem that from time to time notebooks are disappearing on users. When we investigate we notice that they are actually deleted from the filesystem (git marks them as deleted, we have the git storage enabled).

It was very difficult to isolate the problem and we were not able to fully reproduce it but rather gathered the following information:

- (probably) all disappearing notebooks have been imported using the JSON import from the UI
- (probably) all disappearing notebooks have been scheduled using the built-in scheduler from the UI
- there are notebooks which are scheduled but never disappeared; they are probably not imported
- there are notebooks which are imported but never disappeared; they are not scheduled
- there are notebooks which are imported and scheduled but don't disappear
- there seems to be a pattern that it starts deleting from the ones that are scheduled first (e.g. "library notebook" which is scheduled first, dissapeared a lot already)
- other Zeppelins which import but never used the scheduler do not have disappearing notebooks

So it totally looks like something triggered through the scheduling which is somehow related to the import function. I don't know about the internals (how notebook IDs are generated etc.) but it seems that when the scheduler kicks in, something causes a hiccup.

Any ideas?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)