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

Workers not using environment variables for default config options #7070

Open
rjzamora opened this issue Sep 26, 2022 · 0 comments
Open

Workers not using environment variables for default config options #7070

rjzamora opened this issue Sep 26, 2022 · 0 comments

Comments

@rjzamora
Copy link
Member

rjzamora commented Sep 26, 2022

WARNING: The behavior reported here may not be a bug. For example, the consensus may be: "You must set your environment variables before importing dask." However, I want to document the recent change in behavior, because it's breaking dask-cuda CI.

What happened:

The workers within a LocalCluster do not use environment variables to set default config options unless the environment variables were set before dask was imported.

What you expected to happen:

Environment variables should still be used to set dask.config defaults after importing dask.

Minimal Complete Verifiable Example:

import os
import dask
from dask.distributed import LocalCluster, Client

def check_config():
    assert os.environ.get("DASK_DISTRIBUTED__COMM__COMPRESSION") == "False"
    print(f"distributed.comm.compression={dask.config.get('distributed.comm.compression')}")

os.environ["DASK_DISTRIBUTED__COMM__COMPRESSION"] = "False"
with LocalCluster(n_workers=1) as cluster:
    with Client(cluster) as client:
        client.run(check_config)

# Prints: distributed.comm.compression=auto
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

No branches or pull requests

1 participant