-
Notifications
You must be signed in to change notification settings - Fork 39
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
Docs: How to purge old workers (status: Not responding) #597
Comments
Hi, Thanks for your question, please try the For example, Question, why did the workers get stuck at at |
We also have a sample fleet health check that you can deploy via CloudFormation, that will monitor the health of workers to clean them up and notify you if there are sustained issues. |
Thank you @leongdl @mwiebe
We've been using Windows Deadline worker service and sometimes we hit this bug. In other cases Deadline service failed to start (i.e. there was a timezone bug on CMF fleet like time wasn't properly synchronized with global time so Worker couldn't start, see error message below). Error:
Any comments? |
This is really good. We can use that I think. Is it compatible with CMF? |
Yes, this template was created for a CMF with an EC2 Auto Scaling Group and event-based auto scaling enabled. |
Documentation Issue
Hi there,
We are trying to figure out how to properly purge old workers?
Due to active development we have many worker with status: Not responding. How to delete them via deadline tool?
Best wishes,
Petr
The text was updated successfully, but these errors were encountered: