John R Pierce wrote:
drbd is asynchronous replication, isn't it? so if the active 'master' fails just as its written and acknowledged an incoming message, that message could be lost if the replication hasn't completed by the time of failure ?
I believe you can run DRBD so primary writes dont return till the secondary write also completes. No idea how that impacts performance :D