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

Cannot run two notebooks with IPyParallelExecutor #39

Closed
WardLT opened this issue Nov 27, 2017 · 5 comments
Closed

Cannot run two notebooks with IPyParallelExecutor #39

WardLT opened this issue Nov 27, 2017 · 5 comments

Comments

@WardLT
Copy link
Contributor

WardLT commented Nov 27, 2017

If I execute two Jupyter notebooks that both use IPyParallelExecutor workers, Parsl jobs for the notebook that started last do not run.

@yadudoc
Copy link
Member

yadudoc commented Nov 28, 2017

@WardLT Have you noticed this behavior only on the ALCF jupyter notebooks or do you see this on local notebooks as well ?

@WardLT
Copy link
Contributor Author

WardLT commented Nov 28, 2017 via email

@yadudoc
Copy link
Member

yadudoc commented Nov 30, 2017

I'm able to reproduce this issue by simply running two instances of the same notebook and running them simultaneously. The apps in the first notebook to run execute, while the ones in the second seem to simply hang.

@WardLT
Copy link
Contributor Author

WardLT commented Nov 30, 2017 via email

@yadudoc
Copy link
Member

yadudoc commented Dec 19, 2017

@WardLT , I'm working on isolating the IPP elements in a similar problem. For a single run of a workflow, multiple sites (say a NERSC machine and a local cluster) is being used. For isolation we start separate controllers for each site and their configuration are kept apart by having the config files live in directories named after the sites (~/.ipython/cori or ~/.ipython/midway).

However this naming convention is not particularly effective if there are two workflows using the same config, being launched at the same time. Do you think temporary directories to store config make sense ?

@yadudoc yadudoc mentioned this issue Dec 19, 2017
benclifford pushed a commit that referenced this issue Aug 9, 2018
I decided not to provide a default `channel_script_dir` because
it might be confusing in case the user provides their own channel.
Passing `None` to `LocalChannel` would overwrite its own default
(which is better to specify in the signature). Fixes #39.
benclifford pushed a commit that referenced this issue Aug 9, 2018
annawoodard added a commit that referenced this issue Sep 24, 2018
I decided not to provide a default `channel_script_dir` because
it might be confusing in case the user provides their own channel.
Passing `None` to `LocalChannel` would overwrite its own default
(which is better to specify in the signature). Fixes #39.
annawoodard added a commit that referenced this issue Sep 24, 2018
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