dask / dask/distributed

Warn (and eventually raise) when client.scatter is used with Active Memory Manager enabled

Open
#8,921 4 comments 0 reactions 0 assignees View on GitHub
needs triage
Dominant language
Python
Stars
1.7k
Forks
778
Avg merge
2h 50m
Merged PRs (30d)
3

Description

Using ``scatter`` is generally not a good idea anymore and doesn't have any effect if the active memory manager is enabled. People are frequently running into this or are using scatter anyway, which is a bad UX and confusing.

We should raise a warning if ``scatter`` is used and point people to delayed and probably raise at some point later or get rid of the method completely.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.