-
Notifications
You must be signed in to change notification settings - Fork 9
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
Handle connection closure for Dask workers #78
Comments
This issue is a common one as I've seen several stack overflow posts about it, such as this one. A while back, I tried fixing this with a simmate/src/simmate/configuration/dask/connect_to_database.py Lines 32 to 119 in 3fb8297
|
This may be relevant to this issue -- but DigitalOcean makes automatic updates to database servers:
How would long-lived connections behave here? Could this be a cause of the connections closing? |
For long running Prefect Agent and Dask Clusters, the database connection (through Django) sometimes disconnects -- causing all following database transactions to fail with "connection already closed" error.
The text was updated successfully, but these errors were encountered: