-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[BUG] All stopped batch jobs restart and Docker daemon enter in stuck state after clients is restarted. #6438
Comments
@cgbaker any other information I need to send for investigation? |
This errors is normal?
|
thanks, @jonatasfreitasv. I reproduced the issue and I'm tracking down the cause. I'll let you know if there's anything else I need. |
@jonatasfreitasv : this issue was fixed by #6216 and/or #6207, which is part of 0.9.6. |
@cgbaker Nice!!! I'm start test now. |
did 0.9.6 resolve this issue? if so, please close this issue in github. |
Yes! For now is ok!!! Thx a lot... |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
0.9.5
Operating system and Environment details
CentosOS
Issue
Hello!
After I run a lot of jobs (+10k) and all finished, when I start and stop nomad clientes Docker Daemon enter in stuck state and consume all cpus and i/o.
And too start all stopped batch jobs again...
Any idea about this?
The text was updated successfully, but these errors were encountered: