On 2/4/2012 2:04 PM, Brian Candler wrote:
> On Sat, Feb 04, 2012 at 06:49:23AM -0600, Stan Hoeppner wrote:
>> Apparently you've read of a different GlusterFS. The one I know of is
>> for aggregating multiple storage hosts into a cloud storage resource.
>> It is not designed to replace striping or concatenation of disks within
>> a single host.
> Sure it can. A gluster volume consists of "bricks". Each brick is served by
> a glusterd process listening on a different TCP port. Those bricks can be on
> the same server or on different servers.
That's some interesting flexibility. I'd never heard of the "intranode"
Gluster setup. All the example ocnfigs I'd seen showed md/hardware RAID
with EXT4 atop, then EXT4 exported through Gluster.
>> Even if what you describe can be done with Gluster, the performance will
>> likely be significantly less than a properly setup mdraid or hardware
>> raid. Again, if it can be done, I'd test it head-to-head against RAID.
> I'd expect similar throughput but higher latency. Given that I'm using low
> RPM drives which already have high latency, I'm hoping the additional
> latency will be insignificant. Anyway, I'll know more once I've done the
As they say, there's more than one way to skin a cat.
>> I've never been a fan of parity RAID, let alone double parity RAID.
> I'm with you on that one.
When you lose a disk in this setup, how do you rebuild the replacement
drive? Do you simply format it and then move 3TB of data across GbE
from other Gluster nodes? Even if the disk is only 1/3rd full, such a
restore seems like an expensive and time consuming operation. I'm
thinking RAID has a significant advantage here.