[Pacemaker] drbd diskless -> failover to other node

Florian Haas florian.haas at linbit.com
Fri Aug 27 05:26:58 EDT 2010

On 2010-08-27 11:08, jimbob palmer wrote:
>> Which means you're causing a service interruption when you don't need
>> to. Instead, your application could continue running on the same node,
>> DRBD will ensure that the application transparently writes to and reads
>> from the peer when it thinks it's writing locally, and you can coolly
>> hot-swap the drive out from under DRBD, and resync.
>> Usually service interruption is worse that degraded performance. Would
>> you rather fail over automatically, perhaps during peak hours and under
>> full load (which is what you are headed for), or would you rather have
>> your app continue to run where it is, to then switch over at a time of
>> your choosing?
> Are you saying that if a server loses its disk, it will transparently
> write to the secondary server without any need to failover at all?

Yes. As long as it still has a network connection to the peer, of course.

> WOW. I never knew DRBD did this. This is a _fantastic_ feature :)

Well, that's what diskless mode is really all about.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100827/04c0405e/attachment-0003.sig>

More information about the Pacemaker mailing list