That's an awesome way to have a fault tolerant solution. A completely
different way of thinking about the problem; my background is more from
replicating services so I tend to go for a front-end load balancer with
failure detection and two active nodes. It so much depends on exactly
what problem is being solved - there isn't one problem and there isn't
one solution. Do let me know how it goes.
Andy
On 13/05/13 16:36, Stephen Allen wrote:
I am working towards the point of deploying Fuseki in production, and
my plan is to try to use DRBD [1] to mirror TDB's data and journal
files to the failover machine. The failover machine will be "warm",
meaning it won't be running Fuseki during normal operation, but upon
failure of the master, a Fuseki instance will be started up using the
data/journal files managed by the block-level replication provided by
DRBD. As our data is fairly critical, we plan to use fully
synchronous block mirroring. Given this set-up (combined with daily
nquad dumps for backup), we hope to have a pretty highly available
infrastructure.
This is still in the planning stages, and I don't really have any
details on the supporting software yet, but right now I'm thinking of
using Pacemaker (and possibly Corosync) in a set-up very similar to
the one that can be used for MySQL [2] or PostgreSQL [3].
-Stephen
[1] http://www.drbd.org/
[2] https://dev.mysql.com/doc/refman/5.0/en/ha-drbd.html
[3] http://wiki.postgresql.org/images/0/07/Ha_postgres.pdf
