HPE SimpliVity
1758664 Members
2501 Online
108874 Solutions
New Discussion

Re: Arbiter location of concern and best practices

 
SOLVED
Go to solution
whatlookfor
Occasional Contributor

Arbiter location of concern and best practices

Hello guys, i have concerns about possible split brain scenario that i need to confirm.

I have to two nodes in one vmware cluster, one federation, each node at two different locations. Arbiter is located on a cloud VM that can be reached from both nodes obviously.

Questions :

  • Is this deployment secure ?
  • If i lose connection between arbiter and one host or both host = i guess everything's fine as long as hosts can communicate whith each other but if i lose network connection between the two nodes meaning each can only communicate with the cloud arbiter, would it create a split brain scenario or not ?
  • Would it be better to leave the Arbiter next to a Simplivity node on the same location ?

Thanks for your help

DFi

1 REPLY 1
Danievr
HPE Pro
Solution

Re: Arbiter location of concern and best practices

The arbiter must be ouside the SimpliVity cluster to prevent both hosts going down if simplivity node hosting the arbiter is lost.

If both hosts can see arbiter - no split brain. Will re-sync once network is restored.

I work for HPE.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]