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

Pass host through LocalCluster to workers #5427

Merged
merged 2 commits into from
Oct 14, 2021

Conversation

jcrist
Copy link
Member

@jcrist jcrist commented Oct 14, 2021

Ensures host parameter is properly forwarded through LocalCluster to all created objects and adds a corresponding test.

  • Closes #xxxx
  • Tests added / passed
  • Passes pre-commit run --all-files

jcrist and others added 2 commits October 4, 2021 10:02
Previously the `host` parameter to `LocalCluster` would only be
forwarded to `Scheduler` instances and not `Worker`/`Nanny` instances,
leading to workers listening on non-localhost in some configurations.
This fixes that and adds a test.
Copy link
Member

@jrbourbeau jrbourbeau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @jcrist! This is in

(Note: the failures here are unrelated. See, for example, #5406 )

@jrbourbeau jrbourbeau merged commit afce4be into dask:main Oct 14, 2021
zanieb pushed a commit to zanieb/distributed that referenced this pull request Oct 28, 2021
Previously the `host` parameter to `LocalCluster` would only be
forwarded to `Scheduler` instances and not `Worker`/`Nanny` instances,
leading to workers listening on non-localhost in some configurations.
This fixes that and adds a test.

Co-authored-by: James Bourbeau <[email protected]>
@JPvRiel
Copy link

JPvRiel commented Nov 10, 2021

Just to express thanks, I upgraded and can now confirm this potential security vulnerability is avoided as the local cluster now clearly binds to 127.0.0.1 by default.

I checked cluster.scheduler.address

'tcp://127.0.0.1:35689'

And [i[0] for i in cluster.scheduler.worker_info.items()] (had 6x workers)

['tcp://127.0.0.1:35071',
 'tcp://127.0.0.1:37679',
 'tcp://127.0.0.1:39051',
 'tcp://127.0.0.1:42149',
 'tcp://127.0.0.1:42557',
 'tcp://127.0.0.1:44993']

@jcrist jcrist deleted the pass-host-to-localcluster-worker branch November 10, 2021 15:27
quasiben pushed a commit to quasiben/distributed that referenced this pull request Nov 16, 2022
Previously the `host` parameter to `LocalCluster` would only be
forwarded to `Scheduler` instances and not `Worker`/`Nanny` instances,
leading to workers listening on non-localhost in some configurations.
This fixes that and adds a test.

Co-authored-by: James Bourbeau <[email protected]>
quasiben pushed a commit to quasiben/distributed that referenced this pull request Nov 16, 2022
Previously the `host` parameter to `LocalCluster` would only be
forwarded to `Scheduler` instances and not `Worker`/`Nanny` instances,
leading to workers listening on non-localhost in some configurations.
This fixes that and adds a test.

Co-authored-by: James Bourbeau <[email protected]>
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

Successfully merging this pull request may close these issues.

3 participants