On Fri, Feb 06, 2015 at 05:06:38PM +0000, ML mail wrote: > Hello, > > I read in the Gluster Getting Started leaflet > (https://lists.gnu.org/archive/html/gluster-devel/2014-01/pdf3IS0tQgBE0.pdf) > that the max recommended brick size should be 100 TB. > > Once my storage server nodes filled up with disks they will have in > total 192 TB of storage space, does this mean I should create two > bricks per storage server node? > > Note here that these two bricks would still be on the same controller > so I don't really see the point or advantage of having two 100 TB > bricks instead of one single brick of 200 TB per node. But maybe > someone can explain the rational here? This is based on the recommendation that RHEL has for maximum size of XFS filesystems. They might have adjusted the size with more recent releases, though. However, having multiple bricks per server can help with other things too. Multiple processes (one per brick) could handle more clients at the same time. Depending on how you configure your RAID for the bricks, you could possibly reduce the performance loss while a RAID-set gets rebuild after a disk loss. Best practise seems to be to use 12 disks per RAID-set, mostly RAID10 or RAID6 is advised. HTH, Niels
Attachment:
pgpkZX6VYxG1y.pgp
Description: PGP signature
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
