dask / dask/distributed

Inconsistent treatment of non-string worker names

Open
#5,743 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
Python
Stars
1.7k
Forks
778
Avg merge
2h 50m
Merged PRs (30d)
3

Description

The treatment of numeric worker names is inconsistent:

- ``Client.retire_workers(names=[...])`` maps worker names to strings, so a worker may be called ``1`` and you can pass ``"1"`` to the method, or vice versa
- ``Client.submit(..., workers=[...])`` does not do the mapping; ``1`` and ``"1"`` are different
- ``Client.scatter(..., workers=[...])`` does not do the mapping either
- ``Client.replicate(..., workers=[...])`` silently fails when passing string names and crashes when passing numeric names
- ...other methods?

(note: scatter/replicate to specific workers are pending discussion and redesign within the scope of the Active Memory Manager)

xref:
- #2949

@mrocklin in #2949 you mentioned support for CLIs. Were you referring to any specific CLI? Is the feature still desirable?
CC @gjoseph92

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.