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

Add config to control default direct_to_worker value #8964

Open
fjetter opened this issue Dec 12, 2024 · 0 comments
Open

Add config to control default direct_to_worker value #8964

fjetter opened this issue Dec 12, 2024 · 0 comments
Labels
config enhancement Improve existing functionality or make things work better

Comments

@fjetter
Copy link
Member

fjetter commented Dec 12, 2024

Clients can gather and scatter data directly to the workers instead of proxing everything over the scheduler. It is currently not possible to define the default of this behavior and in almost all circumstances it chooses the proxy over scheduler approach unless the client is initialized with direct_to_worker=True.

I believe it would be convenient to add this to the dask config to allow users to set this as a default in their config it they know that their deployment supports this.

@fjetter fjetter added enhancement Improve existing functionality or make things work better config and removed needs triage labels Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
config enhancement Improve existing functionality or make things work better
Projects
None yet
Development

No branches or pull requests

1 participant