You can't do a drbd0.8-style active/active, i.e. you can't have a single
storage partition be served by multiple servers simultaneously.
However, you can serve different partitions/disks/logical volumes/whatever
from different servers and be active/active that way (Lustre will merge
all these different partitions into one filesystem, or for however many
you have it configured). If one node fails, you just failover its
partitions to the drbd "sister" server.
We're not in production, yet, (we still have to figure out the stale nfs
file handle issue when exporting via NFS that was mentioned a few messages
ago), but it seems to work fine. Failover can be slow due to the
client reconnect timer, but that is tweakable.
Thanks,
Brent Nelson
Director of Computing
Dept. of Physics
University of Florida
On Fri, 27 Oct 2006, Mustafa A. Hashmi wrote:
Hi Brent:
On 10/12/06, Brent A Nelson <[EMAIL PROTECTED]> wrote:
If you use drbd to handle the replication at the block device level,
however, Lustre may still be a good choice for the filesystem on top,
especially if you have more than 2 servers that can be used to take
advantage of Lustre's parallelism (although you can do this even with
just 2 active/active servers)...
Are you doing active/active with drbd 0.8.x? I am simply curious if
this is in a production environment and how well it's working for you.
Regards,
--
Mustafa A. Hashmi
[EMAIL PROTECTED]
[EMAIL PROTECTED]
_______________________________________________
Lustre-discuss mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
