dask / dask/distributed

Adaptive docs could do with a bit more details

Open
#1,789 12 comments 0 reactions 0 assignees View on GitHub
adaptive documentation
Dominant language
Python
Stars
1.7k
Forks
778
Avg merge
2h 50m
Merged PRs (30d)
3

Description

I've been piecing together an auto-scaling `dask` cluster on AWS, using `adaptive` and bits from `dask_ec2`. It would be really useful to know what the semantics of the `scale_up` and `scale_down` calls are, especially if `scale_up` should return immediately, block, return a future or something else. It isn't clear from the examples (so I'm currently reading the sources).

My main concern here is what happens when long blocking call are made inside `scale_up` or `scale_down` - for instance bringing up new AWS instances?

I'm guessing that the best way to approach this is to return a future by using `tornado.gen.coroutine`.

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.