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.

Sign up for GitHub

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

Jump to bottom

Random port for scheduler #1

Open
ssomnath opened this issue Mar 3, 2020 · 0 comments
Open

Random port for scheduler #1

ssomnath opened this issue Mar 3, 2020 · 0 comments

Comments

@ssomnath
Copy link
Collaborator

ssomnath commented Mar 3, 2020

Given that Summit only has five batch nodes, shouldn't the scheduler be configured to run on a random port so that more than one user can run a scheduler (on different ports) on the same batch node? This is something we encountered when setting up per-user jupyterlab servers on Summit.
pentschev pushed a commit to pentschev/nvrapids_olcf that referenced this issue Sep 24, 2020
@zronaghi
Merge pull request benjha#1 from pentschev/rmm_updates
0dd6529 
Use updated dask_cudf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ssomnath