Loading...
 
Skip to main content

Architecture / Installation


You are viewing a reply to Multiple MySQL replication slaves?

Re: Multiple MySQL replication slaves?

Yes, I'm replying to my own message:

I have found a relatively simple solution. I set up MySQL replication and left it at that. The main advantage is that it was very simple to set up, and appears to be working correctly (with a few caching gremlins loose on the slave system). Category creation seems to lag a bit, but they are in the database. A quick cache purge and it's ready to go. Also the replication is nearly instant.

The disadvantage is that some tables conflict with the two Tiki installs, and I am having to tell MySQL to ignore a few tables in the replication: tiki_actionlog and tiki_stats. If I don't ignore these tables, replication halts until I correct the problem.

If anybody knows any other tables that wouldn't need to be mirrored (not content/category related), list them here.

I wish that Tiki could support multiple slaves natively, but this appears to work for the moment.