Revisit swarm init --force-new-cluster behavior
Open
@anshulpundir is already working on this.
Since Mar 6, 2018.
- Dominant language
- Go
- Stars
- 3.7k
- Forks
- 676
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
Doing docker swarm init --force-new-cluster when there are more than one managers present leads to inconsistencies in the cluster memberlist with the other managers still seeing the old cluster manager list while the manager where the docker swarm init --force-new-cluster was run only seeing itself as the manager.
One option is to disallow init --force-new-cluster when the size of the raft group is > 1.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.