https://www.tag1consulting.com/ en https://www.tag1consulting.com/blog/mysql-replication <div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"> <p>Until recently, I was a student employee at the Oregon State University Open Source Lab. My career there ended, like many, with that painful process known as graduation. I got invaluable experience at the lab, not the least of which being the knowledge gained as their main (only) database administrator. One of my great pleasures in that position, was learning how to configure MySQL replication and manage clusters of replicating database servers. Even the simple case of a single master and a single slave has its edge cases. There are endless tips and tricks to make long-term maintenance easier and to allow you to make full use of this technology. Running replicating database servers for Drupal in particular has several tricks to it: Replication Settings - Timewarp A major issue with replication in MySQL is that it has a tendency to fall behind. There are various tricks you can employ to assist with this and some big ones for Drupal specifically. First, if you are going to use the search module, you will need to stop the replication of the temp tables it uses. These will be replicated to the slave as they are technically volatile queries, however, they are...</p> </div> <span><a title="View user profile." href="/user/narayan-newton">nnewton</a></span> <span><time datetime="2008-07-31T01:08:37-07:00" title="Thursday, July 31, 2008 - 01:08">Thu, 07/31/2008 - 01:08</time> </span> Thu, 31 Jul 2008 08:08:37 +0000 nnewton 16 at https://www.tag1consulting.com