Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App Workspace confusing while notebook is running #78

Open
gweis opened this issue Feb 3, 2019 · 2 comments
Open

App Workspace confusing while notebook is running #78

gweis opened this issue Feb 3, 2019 · 2 comments

Comments

@gweis
Copy link

gweis commented Feb 3, 2019

While a notebook is running, all the files are synced to the notebook storage.
Browse and up/download in the workspace UI connect directly to object store. So changes done in notebook server (while notebook is running) don't show up in object store.

Also any changes done to workspace will be overwritten by sync back when notebook shuts down.

Need a solution for that.

@gweis
Copy link
Author

gweis commented Feb 3, 2019

Possible quick fix:

Lock workspace browser while sync is in progress.

Connect workspace browser directly to notebook server (or webdav endpoint) while notebook is running.

Also let user only spawn notebook when there is no upload to object store in progress (may need to consider eventual consistency here as well)

@manhinli
Copy link

manhinli commented Feb 4, 2019

Lock workspace browser while sync is in progress.

We could extend that to "lock workspace browser when notebook server up" and put a message saying words to the effect of "contents you see here is read-only and not up to date with notebook server X which is currently active."

Connect workspace browser directly to notebook server (or webdav endpoint) while notebook is running.

If we do end up with multiple notebook server instances this would be a problem (not sure how likely we're going to do multi-instance though.)


Is there the possibility of just one-way syncing from Jupyter to the object store at certain intervals even while the notebook server is running? We can still put a "data here may be up to X minutes old/stale and this is read-only while the notebook server is running" message but at least people don't have to shut down the notebook server to get stuff out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants