On Tue, Sep 15, 2009 at 17:15:18 +0100 (+0100), Chris Simmonds wrote: > > One option I have considered is using, say, MySQL with one master node > replicating to all the others and some mechanism to elect a new master > if the original went down. But, that sounds messy. There must be a > neater solution?
MySQL + LinuxHA + DRBD is the typical solution. You could use MySQL with replication and failover (or even multi-master if you are brave). A proper clustered filesystem (e.g. OCFS2 ontop of DRBD8) maybe better. However be aware that all of these aren't simple configs and you really want to do thorough testing beforehand - I've seen some setups be incredibly brittle - so any theoretical improvement in uptime may in practice become a major drop. For example when I was looking at GFS last year: http://www.smop.co.uk/blog/index.php/2008/02/11/gfs-goodgrief-wheres-the-documentation-file-system/ Adrian -- bitcube.co.uk - Linux infrastructure consultancy Puppet, Debian, Red Hat, Ubuntu, CentOS, ... -- Please post to: Hampshire@mailman.lug.org.uk Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire LUG URL: http://www.hantslug.org.uk --------------------------------------------------------------
