[Gluster-users] balancing redundancy with space utilization
toml at bitstatement.net
Wed Jun 4 00:41:37 UTC 2008
Currently it would seem that AFR will simply copy everything to every
brick in the AFR. If I did something like ...
subvolumes brick1 brick2 brick3 brick4 brick5 brick6 brick7 brick8
I would wind up with 8 copies of every file. Clearly, this is too many.
What I would rather have is maybe 3 copies of each file distributed
randomly across 3 servers, so that I could still have 2 servers fail and
have all data available, but without using up unnecessary space on the
other 5. The 3 would need to be round-robined in some manner so as to
distribute the disk utilization. First file goes on brick1 brick2
brick3, 2nd file goes on brick2 brick3 brick4, etc.
It seems that AFR used to have this with "option relicate *:3" but that
was removed. The supposed replacement for that, the switch scheduler,
doesn't really have the same functionality.
Unless there is a undocumented form of the "option switch.case"
statement that I have yet to see. Can I do "option switch.case *:3" or
BIT Statement LLC
More information about the Gluster-users