You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allocations become stuck in pending status when the Docker engine becomes unresponsive. Obviously, there is a serious issue with Docker here that needs to be resolved, and there is only so much that the client can do if the engine is unresponsive, but I would expect that the allocations would eventually be moved to another client rather than being stuck in pending forever. This issue may be related to #2747, but seems different enough (Docker vs. raw-exec) to warrant a separate issue.
Reproduction steps
An unresponsive Docker engine (perhaps stopped with SIGSTOP) and new allocations.
Nomad Client logs
The client logs show that the client eventually stops dequeuing allocations in Client.watchAllocations when the updates channel is full. The full stack traces after SIGQUIT are in nomad_docker_pending.txt
@dadgar Thanks for the update. I've now seen "pending with no allocation" happen a few times where there wasn't an issue with the Docker engine. I believe we've solved the issue with the Docker timeouts, so we'll see if this continues and wait for RC2.
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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Nomad version
Nomad v0.6.0-rc1 (5187fcf+CHANGES)
Operating system and Environment details
CentOS 7.3.1611
Docker 17.03.2-ce
Consul v0.8.5
Issue
Allocations become stuck in pending status when the Docker engine becomes unresponsive. Obviously, there is a serious issue with Docker here that needs to be resolved, and there is only so much that the client can do if the engine is unresponsive, but I would expect that the allocations would eventually be moved to another client rather than being stuck in pending forever. This issue may be related to #2747, but seems different enough (Docker vs. raw-exec) to warrant a separate issue.
Reproduction steps
An unresponsive Docker engine (perhaps stopped with SIGSTOP) and new allocations.
Nomad Client logs
The client logs show that the client eventually stops dequeuing allocations in
Client.watchAllocations
when theupdates
channel is full. The full stack traces after SIGQUIT are in nomad_docker_pending.txtThe text was updated successfully, but these errors were encountered: