Two storage servers being recruited on the same process after a failure

As part of testing fearless cluster, remote data center was brought down for sometime and when they were back up, there were multiple instances of two storage servers being recruited on the same process in the remote DC. It is not harmful as i believe the second one will go away eventually. But it should be looked into why there was additional storage server being recruited and try to avoid it.

Reproduce the reported fearless-cluster scenario by bringing the remote data center down and back up during testing. Investigate why two storage servers are recruited on the same process after recovery, then verify that only the expected server remains and duplicate recruitment is avoided.

Written by the indexing model from the issue text.