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

Cluster failed to start: Timed out trying to connect #920

Open
shreyaslr opened this issue Nov 15, 2024 · 1 comment
Open

Cluster failed to start: Timed out trying to connect #920

shreyaslr opened this issue Nov 15, 2024 · 1 comment
Labels
needs info Needs further information from the user needs reproducible example

Comments

@shreyaslr
Copy link

Describe the issue:

I am using prefect and dask getting below error

RuntimeError: Cluster failed to start: Timed out trying to connect to tcp://dask-root-d.default:8786 after 30 s

even though the environment value is set to 300 seconds

ENV DASK_DISTRIBUTED__COMM__TIMEOUTS__CONNECT=300s

Environment:

dask-kubernetes==2023.7.0
dask==2023.7.0
distributed==2023.7.0
prefect==1.2.4
@jacobtomlinson
Copy link
Member

To help you troubleshoot this we are going to need a minimum reproducible example. It would also help if you can share the logs from the Dask scheduler Pod.

@jacobtomlinson jacobtomlinson added the needs info Needs further information from the user label Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs info Needs further information from the user needs reproducible example
Projects
None yet
Development

No branches or pull requests

2 participants