Open anshulpundir opened 6 years ago
@anshulpundir This is the feature. I don't see what other behavior would be expected here. --force-new-cluster
is an intentionally destructive operation.
Should we balance this with a way to evict the forked manager?
Makes sense. Changed the title.
I guess evicting the forked managers is probably a better approach since its backwards compatible. @stevvooe
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 thedocker 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.