Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
cloudappliance/mastermasterdb [2021_06_18 09:17] – smeadmincloudappliance:mastermasterdb [2022_02_09 14:47] – [Disclaimer] doug
Line 1: Line 1:
 ===== File Fabric HA Master - Master Database with Automatic Failover ===== ===== File Fabric HA Master - Master Database with Automatic Failover =====
-== last updated Feb. 14, 2020 ==+== last updated July 16, 2021 ==
  
 ==== Disclaimer ==== ==== Disclaimer ====
Line 8: Line 8:
  
 <WRAP center round important 100%> <WRAP center round important 100%>
-This setup is suitable if you have a reliable network between mysql nodes and are deploying in a single data centre. +This setup is supported for mysql nodes which are deployed in a single data centre.
  
-If the network is partitioned there is a chance that both masters can become active at the same time(split brain) and you will have corrupt data. In case of a split brain you will have to restore the data from a backup.+Cross region networks can become partitioned resulting in both masters becoming active at the same time(split brain). Split brain reconciliation is not possible and recovery of services can/will require restoration of the database from a backup before a split brain event.
  
-If you are deploying across multiple data centers or network is not reliable please follow [[cloudappliance:highavailabilitysetup]]+For this reason, when deploying across multiple data centers or regions with possibility of network partitions, please follow [[cloudappliance:highavailabilitysetup]]
 </WRAP> </WRAP>
 ==== Introduction ==== ==== Introduction ====
Line 102: Line 102:
 </code> </code>
  
-Place a "#" infront of the lines to mirror the output below:+Place a "#" in front of the lines to mirror the output below:
  
 ``` ```
© Copyright 2024 Nasuni.