Loading...
 
Architecture / Installation

Architecture / Installation


Multiple MySQL replication slaves?

posts: 2

I have an interesting situation.

My office has multiple locations (a central office and numerous satellite locations), and the connection between the satellites and central office is very slow. I wanted to have a single Tiki installation that was 'mirrored' to multiple satellite locations.

I have already pored through the documentation, and seen the page on replication. But it is not very well documented (it only shows some configuration lines; it doesn't show if the slave has to be created, if preferences are mirrored or independent on the different servers, etc). It also appears to only support one shadow host (I'm guessing that the shadow is the 'slave' Tiki).

Is there a way to support multiple slave systems from a single master?

Note the following:

1. I don't necessarily need the Tiki configuration mirrored. I can do that myself, and certain configuration items will be different (LDAP hosts, etc).

2. I don't need to be able to write content on all the servers at once. I would be happy writing content at the master system (in the central office), and read-only copies on the slave systems. No 'multiple masters' for content.

3. I need to be able to replicate the pages and any attached files. I currently have the file gallery storing files in the database, so that may be enough if the database replicates.

4. I don't need Intertiki, since I'm using LDAP hosts for authentication (and those hosts replicate with each other on their own). I need content mirroring.

posts: 2

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.