-
-
Notifications
You must be signed in to change notification settings - Fork 139
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
Specify a cluster scheduler listener port? #355
Comments
I can reproduce this and it seems like a regression in 0.7.0. It works as it should with 0.6.3. from dask_jobqueue import SGECluster
cluster = SGECluster(queue='short.q',
cores=10,
memory='20GB',
walltime='00:20:00',
scheduler_port=8804)
print(cluster.scheduler_address) Output with 0.6.3:
Output with 0.7.0 (random port):
My previous mental model was that This would needs to be looked at maybe @mrocklin you have a super rough guestimate how hard this would be to fix ? I am hoping this is a silly mistake that we did not catch and should be reasonably straightforward to figure out where the At the moment I don't have the bandwidth to investigate, but a PR would certainly be welcome! |
Downgrading to 0.6.3 did the trick, for me. Thanks. I'd certainly be willing to take a look at getting |
The relevant lines to affect are here: dask-jobqueue/dask_jobqueue/core.py Lines 428 to 437 in c1e0a21
You want to make sure that the options dict here includes |
Sure, help would be more than welcome on this! This is a regression in 0.7 and it would be nice to get it fixed.
Yes (there is a link to dask contributing guidelines with more material), there was some talk about adding CONTRIBUTING.md in In any case I am not sure what you mean by "only", but if you spot possible improvements in the contributing documentation, feel free to open a separate PR about this as well! |
see also dask/dask-kubernetes#196 for something similar. |
@hawk-sf would you still be willing to do something about this? |
Yes- thanks for the prompt. This had slipped down the priority list, but I’ll have time to start at the end of this week. |
FYI I have a PR in #384. |
I'm trying to use dask-jobqueue on an SGE cluster, and by default our worker nodes cannot communicate back to the login node. The admins have set aside a small range of ports us to use for this, but I can't seem to specify a port/port range for the scheduler to listen on. I see with
dask.distributed
'sLocalCluster
, you can specify the argumentscheduler_port
, butSGECluster
does not seem to take the keyword (though it doesn't complain):cluster.scheduler
shows the scheduler still being assigned a random port (always around 40,000):Is there a way to configure this?
Thanks.
The text was updated successfully, but these errors were encountered: