Aug 022013
Here’s my plan.
I have 4 servers named them as gfs[11-14], each machine has 4 disks, with sda allocated for root, swap, etc, and sdb-sdd as data in XFS.
I’m going to run distributed-replicated volume with replication 2, and I want to keep highest availability, as much as I can. So the layout will be something like this:
| sdb | sdc | sdd | |
|---|---|---|---|
| gfs11 | brick1#R1 | brick2#R1 | brick3#R1 |
| gfs12 | brick1#R2 | brick4#R1 | brick5#R1 |
| gfs13 | brick2#R2 | brick4#R2 | brick6#R1 |
| gfs14 | brick3#R2 | brick5#R2 | brick6#R2 |
So anytime:
- If there is single box failure, I have access to all data
- If there are two boxes dead, I have access to 5/6 data
- If there are three nodes dead, I still have access to half of data
2 Responses to “Planning GlusterFS”
Sorry, the comment form is closed at this time.
Sigh, start over again – btrfs as root file system seemed ok, but obviously it was not … I power cycled a box as it failed to respond now it’s printing tons of error messages in syslog, and some system files are missing.
I will re-image all 4 machines and make root fs ext4 (Ubuntu default) and start over again.
[…] on glusterfs test environment as mentioned here, so far everything’s working with some […]