On 13/11/15 07:28, Stephen Allen wrote:
...
This doesn't really solve the replica/hot standby issues you're
discussing. But if you are interested in high availability and failover
for a single TDB instance, you might take a look at DRBD [1][2]. Although
I've mentioned it before, I still haven't had a chance to use it. It does
seem to offer a neat solution for a "warm" standby with automatic failover
(using Heartbeat).
-Stephen
[1] http://drbd.linbit.com/
[2] https://en.wikipedia.org/wiki/Distributed_Replicated_Block_Device
DRBD could work for a (very) warm standby. If the transaction log can
be sync'ed across the machines, then it's zero loss and looks quite
promising.
For live systems, do you know how it interacts with memory mapped files
and also whether the apps can be notified of changes for managing their
in-process caches.
Andy
