The solution has some downsides related to the election mechanism, meaning that if the servers or the cluster services or cluster server elect one server, they will attribute to that server an object that is called a quorum. This quorum does the server or the service that has that quorum, it is taken as the master. So when you have, for example, something happens in your data centers like a power outage or an unexpected shutdown, and you can't start the master server what sometimes will happen, is since the shutdown was unexpected, the cluster didn't have time to do some post configurations before the extension of the shutdown of the servers, sometimes that quorum can't be removed from the crashed master and the cluster wants stuff. This is part of the architecture of this service, the Failover service. So sometimes we face this type of problem. In the past, we had a lot of power outages and when we started after, our server, we faced this problem. Meaning that the cluster won't stop because one of the servers, the master crashed, and they didn't want to start. So we need to access and do some line configurations so that we will force the cluster to elect a new master and ignore the crashed one.
