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

Change Coiled executor to use Dask async API #299

Open
tomwhite opened this issue Sep 5, 2023 · 1 comment
Open

Change Coiled executor to use Dask async API #299

tomwhite opened this issue Sep 5, 2023 · 1 comment
Labels

Comments

@tomwhite
Copy link
Member

tomwhite commented Sep 5, 2023

It would be nice if we could change CoiledFunctionsDagExecutor to be similar to (or based on) AsyncDaskDistributedExecutor, as it would then inherit all the features of that latter, like retries, backups, batching etc (see #276).

@tomwhite
Copy link
Member Author

When doing #309 I noticed that the underlying Dask client used for coiled.function is not asynchronous. So to do this PR we'd need to get the cluster object from the function (see https://docs.coiled.io/_modules/coiled/function.html), then construct an asynchronous client ourselves. The code would then look very like AsyncDaskDistributedExecutor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant