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_04_08 15:56] – Update to edit iptables file directly to apply changes. ericcloudappliance: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 seven jobs listed, when you are done, it should look like this:+Place a "#" in front of the lines to mirror the output below: 
 + 
 +``` 
 +MAILTO='' 
 +#Ansible: 
 +#* * * * * /var/www/smestorage/cron/scheduler_minute.pl 
 +#Ansible: #3 
 +#5 4 * * * /var/www/smestorage/cron/scheduler_daily.pl 
 +#Ansible: #2 
 +#* * * * * /var/www/smestorage/cron/taskmanager.pl 
 +#Ansible: #5 
 +#10 2 1 * * /var/www/smestorage/cron/scheduler_monthly.pl 
 +#Ansible: #4 
 +#5 * * * * /var/www/smestorage/cron/scheduler_hour.pl 
 +#Ansible: #7 
 +30 1 * * * /var/www/smestorage/cron/logroller.pl 
 +#Ansible: #6 
 +#10 * * * * /var/www/smestorage/cron/scheduler.pl 
 +* * * * * /var/www/smestorage/cron/scheduler_syncnodes.pl 
 +``` 
 + 
 +<WRAP center round info 100%> 
 +Please note this information above was updated with the 2106 release of the File Fabric. Please see this [[cloudappliance/high-availability-cron|guide for further information]]. 
 +</WRAP>
  
-{{::407ae286-9576-4a13-97bb-e2f0489a2a17.png?400|}} 
  
 === iptables for dbservers === === iptables for dbservers ===
Line 621: Line 643:
  
 == crontab == == crontab ==
-All of smestorage's cron jobs should run on one of the application  servers; only one of smestorage's cron jobs, logroller, should run on the other  application server.+The majority of smestorage's cron jobs should run on one of the application servers; only one of smestorage's cron jobs, logroller, should run on the other  application server.
 **As root on smeweb02 only:** **As root on smeweb02 only:**
 <code> <code>
Line 627: Line 649:
 </code> </code>
  
-Place a # in front of six of the seven jobs listed in the crontab schedule; **do not place a # in front of the logroller job**.+Your crontab should mirror the following: 
 + 
 +``` 
 +MAILTO='' 
 +#Ansible: 
 +#* * * * * /var/www/smestorage/cron/scheduler_minute.pl 
 +#Ansible: #3 
 +#5 4 * * * /var/www/smestorage/cron/scheduler_daily.pl 
 +#Ansible: #2 
 +#* * * * * /var/www/smestorage/cron/taskmanager.pl 
 +#Ansible: #5 
 +#10 2 1 * * /var/www/smestorage/cron/scheduler_monthly.pl 
 +#Ansible: #4 
 +#5 * * * * /var/www/smestorage/cron/scheduler_hour.pl 
 +#Ansible: #7 
 +30 1 * * * /var/www/smestorage/cron/logroller.pl 
 +#Ansible: #6 
 +#10 * * * * /var/www/smestorage/cron/scheduler.pl 
 +* * * * * /var/www/smestorage/cron/scheduler_syncnodes.pl 
 +``` 
 + 
 +<WRAP center round info 100%> 
 +Please note this information above was updated with the 2106 release of the File Fabric. Please see this [[cloudappliance/high-availability-cron|guide for further information]]. 
 +</WRAP>
  
 Restart both servers, so on both smeweb01 and smeweb02, execute a reboot. Restart both servers, so on both smeweb01 and smeweb02, execute a reboot.
© Copyright 2024 Nasuni.