2 way with Arbiter degraded behavior

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi All

When you have a setup with 2 way replication + Arbiter backed by two
large RAID 6 volumes what happens when there is a disk failure and
rebuild in progress in one of those RAID sets from a client
perspective?

Does the FUSE client know how to prioritize the quicker disk (the RAID
set that is not in rebuild)?  If not could it be made smart in this
way? I ask because with large disks, rebuild priority could be set to
very fast on the controller card if Gluster can auto detect or in some
way work around the relatively slow performance from one of two
backends. The likelihood of having rebuilds in progress on two
different raid sets on two different servers is very low.

Another way to state this is "is there some advantage we can gain from
having double replication (RAID 6 + Gluster file replication)?"

Thanks,


Jeff Applewhite
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel



[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux