dask / dask/distributed

Debugpy on AWS Fargate

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

Description

**Describe the issue**:
When launching the scheduler on our AWS Fargate instance, everything works as intended.
However, when launching the scheduler with `debugpy`, to enable remote debugging, 90% of the time the dashboard does not start. This causes our cluster to fail, as we depend on its healthcheck to monitor the cluster health. Once every while, it does boot correctly, but this success appears to be rare and at random.
We correctly configured the Fargate instance for remote debugging, and in the scenarios where it does boot, we can successfully debug the dask scheduler.
The scheduler logs show no errors, and claims that the dashboard boots.

Is there any way to check its logs, or figure out the cause for this? We cannot reproduce this issue locally.

**Environment**:

- Dask version: 2023.3.0
- Python version: 3.11
- Operating System: Linux
- Install method (conda, pip, source): pip

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.