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
Docker slow and not responding #25433
Comments
Just some initial thoughts; This may be related to #25017 I do notice you're running a two-node cluster with two managers; you should never run with two managers; 1 manager or 3 managers is better. In fact, when running with two managers, you double the chance of a manager failure (compared to running a single manager); here's why; The RAFT algorithm requires the managers to reach a quorum when making changes to the Swarm; in a two node manager setup, this effectively means that all managers must be present; if a single manager is lost, you lose control over the cluster. (And with two managers, chances are doubled that one of them fails). Also read this section of the documentation https://docs.docker.com/engine/swarm/admin_guide/#/add-manager-nodes-for-fault-tolerance /cc @LK4D4 @aaronlehmann do you think this issue is the same / related to #25017? |
It's possible, but hard to know without more context. It could simply be that the other manager is down, has changed its IP address, or some similar problem. As @thaJeztah mentioned, a two manager setup has the worst fault tolerance properties, so it's better to run with a single manager (or three). |
Isn't ContainX/docker-volume-netshare in stopping status the reason? If your containers are using volumes. |
@liubin ContainX/docker-volume-netshare is installed but it was not running right when I got the problem. |
Let me close this ticket for now, as it looks like it went stale. |
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.): aws (EC2 Medium), Docker in Swarm Mode.
Issue: Docker is not responding and takes a long time to put this message out:
It takes also a considerable time to restart it:
This is happening for the first time for me.
The only plugin I installed is ContainX/docker-volume-netshare, but it was not running when this bug happened.
The real problem with this is that all of my containers are shut down after restarting Docker (on the first node). Are containers supposed to shut down after a restart ?
The text was updated successfully, but these errors were encountered: