<p>It seems like the AutoScaling Group from AWS are not that synchronized with the Docker Swarm configuration and the default timeouts in the AutoScaling are not accepted in the Docker Swarm managers.</p>

<p>Actually the Health Check is not configured good by default in the EE CloudFormation template, even if the managers are running and stable the Health Check fails and the AutoScalling Group tries to launch new managers. New launched managers are not able to become cluster participants, right after their running state.</p>

CC BY-SA 3.0
2018-04-02T13:52:42.863Z
2018-04-02T13:52:42.863Z
ibedelovski
<p>I have deployed Docker EE on AWS by choosing the package directly from the AWS Marketplace: Docker EE for AWS (Standard/Advanced) - BYOL. The cluster has been successfully launched and deployed on AWS. </p>

<p>After deploying several stacks on the UCP something really strange is happening, the managers are not able to see each other, they are losing the quorum inside the Swarm and the <code>docker info</code> command says that they are out of Swarm.</p>

<p>The AutoScalling group from AWS starts launching new managers inside the Swarm and the new launched managers are terminated in a couple of minutes because they are not Swarm's participants as well. Actually the AutoScalling group goes in a infinity loop by launching new managers and terminating the old ones.</p>

<p>The worst thing is that I am loosing the data from the Docker Services and there is no way of recovering.</p>

<p>Any ideas?</p>

CC BY-SA 3.0
2018-03-30T05:37:09.777Z
What instance sizes are you using? Don't use T2 or anything that cap's CPU. Also be sure you're sizing resources based on UCP/DTR requirements and best practice arch. https://docs.docker.com/datacenter/ucp/2.2/guides/admin/install/system-requirements/ https://success.docker.com/article/docker-ee-best-practices
Bret Fisher
CC BY-SA 3.0
2018-03-30T12:11:14.373Z
@BretFisher I am using m4.large for the managers and c3.xlarge  for the workers.

I think this is not resource issue because the cluster is still in preparation state, we do not have requests from outside to the cluster. The same issue had happened with the previous two clusters with same configuration.
ibedelovski
CC BY-SA 3.0
2018-03-30T21:44:10.617Z
Since you're using EE I recommend contacting docker support for that, definitely sounds like a misconfiguration. https://success.docker.com/support
Bret Fisher
<docker><amazon-web-services><docker-swarm>
Docker managers are losing quorum on AWS
ibedelovski
# Docker managers are losing quorum on AWS

(Asked by: username_0 on 2018-03-29)

I have deployed Docker EE on AWS by choosing the package directly from the AWS Marketplace: Docker EE for AWS (Standard/Advanced) - BYOL. The cluster has been successfully launched and deployed on AWS.

After deploying several stacks on the UCP something really strange is happening, the managers are not able to see each other, they are losing the quorum inside the Swarm and the `docker info` command says that they are out of Swarm.

The AutoScalling group from AWS starts launching new managers inside the Swarm and the new launched managers are terminated in a couple of minutes because they are not Swarm's participants as well. Actually the AutoScalling group goes in a infinity loop by launching new managers and terminating the old ones.

The worst thing is that I am loosing the data from the Docker Services and there is no way of recovering.

Any ideas?

**Tags:** docker, amazon-web-services, docker-swarm

> **Comments:**
> **username_1**: What instance sizes are you using? Don't use T2 or anything that cap's CPU. Also be sure you're sizing resources based on UCP/DTR requirements and best practice arch. https://docs.docker.com/datacenter/ucp/2.2/guides/admin/install/system-requirements/ https://success.docker.com/article/docker-ee-best-practices  
> **username_0**: @BretFisher I am using m4.large for the managers and c3.xlarge  for the workers.  I think this is not resource issue because the cluster is still in preparation state, we do not have requests from outside to the cluster. The same issue had happened with the previous two clusters with same configuration.  
> **username_1**: Since you're using EE I recommend contacting docker support for that, definitely sounds like a misconfiguration. https://success.docker.com/support  

---

## 1 answers

### Answer by username_0 on 2018-04-02. Score: 1

It seems like the AutoScaling Group from AWS are not that synchronized with the Docker Swarm configuration and the default timeouts in the AutoScaling are not accepted in the Docker Swarm managers.

Actually the Health Check is not configured good by default in the EE CloudFormation template, even if the managers are running and stable the Health Check fails and the AutoScalling Group tries to launch new managers. New launched managers are not able to become cluster participants, right after their running state.


---

