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

LocalCluster not using default ports #4429

Open
jacobtomlinson opened this issue Jan 14, 2021 · 2 comments · May be fixed by #8760
Open

LocalCluster not using default ports #4429

jacobtomlinson opened this issue Jan 14, 2021 · 2 comments · May be fixed by #8760
Labels
bug Something is broken good first issue Clearly described and easy to accomplish. Good for beginners to the project.

Comments

@jacobtomlinson
Copy link
Member

jacobtomlinson commented Jan 14, 2021 •
edited
Loading

What happened:

When creating a LocalCluster object the comm is started on a random high port, even if there are no other clusters running.

What you expected to happen:

Should use port 8786.

Minimal Complete Verifiable Example:

$ conda create -n dask-lc-test -c conda-forge -y python=3.8 ipython dask distributed
$ conda activate dask-lc-test

The dask-scheduler command works as expeted.

$ dask-scheduler
distributed.scheduler - INFO - -----------------------------------------------
distributed.scheduler - INFO - -----------------------------------------------
distributed.scheduler - INFO - Clear task state
distributed.scheduler - INFO -   Scheduler at:   tcp://10.51.100.43:8786
distributed.scheduler - INFO -   dashboard at:                     :8787

But LocalCluster does not.

>>> from dask.distributed import LocalCluster
>>> cluster = LocalCluster()
>>> cluster.scheduler_address
'tcp://127.0.0.1:45083'

Anything else we need to know?:

  • Dask version: 2020.12.0 (tried latest source too)
  • Python version: 3.8
  • Operating System: macOS and Ubuntu 18.04
  • Install method (conda, pip, source): conda and source
@quasiben
Copy link
Member

Thanks @jacobtomlinson -- this would be a good first issue if someone want to pick it up. Might not be more than changing the port number here:

distributed/distributed/deploy/local.py

Line 104 in da3d2a4

scheduler_port=0,

@quasiben quasiben added bug Something is broken good first issue Clearly described and easy to accomplish. Good for beginners to the project. labels Jan 14, 2021
@FabioRosado FabioRosado mentioned this issue Jan 15, 2021
Closed
@Yasir323
Copy link

Yasir323 commented Oct 2, 2023

Is this issue still not resolved? May I work in it?

@tmi tmi linked a pull request Jul 11, 2024 that will close this issue
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something is broken good first issue Clearly described and easy to accomplish. Good for beginners to the project.
Projects
None yet
Milestone
No milestone
3 participants
@quasiben @jacobtomlinson @Yasir323