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 [2019_06_19 14:34] ericcloudappliance/mastermasterdb [2020_02_14 15:37] – [File Fabric HA Master - Master Database with Automatic Failover] dan
Line 1: Line 1:
 ===== File Fabric HA Master - Master Database with Automatic Failover ===== ===== File Fabric HA Master - Master Database with Automatic Failover =====
-last updated Sept 182018+== last updated Feb. 142020 ==
  
 ==== Disclaimer ==== ==== Disclaimer ====
Line 97: Line 97:
  
 == crontab == == crontab ==
-You must also disable some jobs in crontab, these should only run on one application serverAgain, as root on smesql01 and smesql02:+You must also disable some jobs in crontab. As root on smesql01 and smesql02:
 <code> <code>
 crontab -e -u smestorage crontab -e -u smestorage
Line 565: Line 565:
  
 ==== Part IV ==== ==== Part IV ====
 +
 +<WRAP center round important 100%>
 +If you will be using a load balancer to distribute traffic to your web servers, configure the load balancer to provide session stickiness.
 +</WRAP>
  
 === Configure the application servers === === Configure the application servers ===
Line 607: Line 611:
  
 == crontab == == crontab ==
-You must also disable crontab on the smeweb02 servercrontab should only run from one application server.+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.
 **As root on smeweb02 only:** **As root on smeweb02 only:**
 <code> <code>
-=crontab -e -u smestorage+crontab -e -u smestorage
 </code> </code>
  
-Place a "#" infront of the seven jobs listed, when you are done, it should look like this: +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**.
- +
-{{::407ae286-9576-4a13-97bb-e2f0489a2a17.png?400|}}+
  
 Restart both servers, so on both smeweb01 and smeweb02, execute a reboot. Restart both servers, so on both smeweb01 and smeweb02, execute a reboot.