Jul 222013
Playing with GlusterFS now, here’s the to-do list:
- Installation and basic configuration, plus getting familiar with command line utilities
- Set up RAID-10-like configuration, with geo-replication if it is possible
- Regular routine maintenance, haven’t got clear idea yet, but should include: expand a volume, shrink a volume, replace a brick in volume, re-balance data, convert another fs to glusterfs, recover from various disasters, etc.
- Performance testing with various scenarios, even people have certain number with them, include: mail server with maildir (large number of small files with small amount of concurrent access), file server (medium number of files and medium size with almost no concurrent access), video server (small number of large files with large amount of concurrent access), file based database like SQLite and BerkeleyDB (concurrent access with lots of seek operation), and RDBMS like mysql/postgre.
Sound like a great plan, right :D? Let’s see.
2 Responses to “To-do list with glusterfs”
Sorry, the comment form is closed at this time.
I’m going to play with btrfs first to make sure data on local system is reliable and expandable, then will move to glusterfs for colo-wise expansion.
I decided to give up btrfs after playing with it a day or two, it’s quite unstable to me as my simplest setup (4 disks striped) print lots of error messages in kern.log. This is one out of 4 machines I used for testing, which means the failure rate is 25%, and I cannot fix the disk (thanks fsck.btrfs) so the only way to get disks usable again is to nuke them.
I’m moving to xfs now, at least it’s what GlusterFS recommended and per history, it’s much more stable than btrfs, the root fs is still btrfs, I’ll stick with it too see if single disk performs better.
BTW, nothing to blame btrfs, they definitely told you this is unstable.