Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Specify a cluster scheduler listener port?

See original GitHub issue

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’s LocalCluster, you can specify the argument scheduler_port, but SGECluster does not seem to take the keyword (though it doesn’t complain):

cluster = SGECluster(queue='short.q',
                     cores=10,
                     memory='20GB',
                     walltime='00:20:00',
                     scheduler_port=8804)

cluster.scheduler shows the scheduler still being assigned a random port (always around 40,000):

<Scheduler: "tcp://169.230.126.85:39008" processes: 0 cores: 0>

Is there a way to configure this?

Thanks.

Issue Analytics

State:
Created 4 years ago
Comments:8 (6 by maintainers)

Top GitHub Comments

1reaction

lestevecommented, Mar 4, 2020

FYI I have a PR in #384.

0reactions

hawk-sfcommented, Feb 25, 2020

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.

Top Results From Across the Web

kube-scheduler - Kubernetes

The scheduler determines which Nodes are valid placements for each Pod in the scheduling queue according to constraints and available resources.

Quartz Configuration Reference

The port on which the RMI Registry is listening (usually 1099). org.quartz.scheduler.rmi.createRegistry. Set the 'rmi.createRegistry' flag according to how you ...

Configure availability group listener - SQL Server Always On

To change the port number of an existing listener, expand the Availability group Listeners node, right-click the listener, and select the ...

How can you change the port JobScheduler listens on?

To change the port that JobScheduler ist listening to, e.g. for JOC and XML commands, modify the value of the port parameter in...

Configuring the node port service range | Networking

Your cluster infrastructure must allow access to the ports that you specify within the expanded range. For example, if you expand the node...