Re:The Elephant was a Trojan Horse: On the Death of Map-Redu...
by necubi on Thursday June 26, 2014 @03:25PM
(#7951182)
It's not used for tolerating disk errors (typically in a production context you have RAID for that, and failures tend to be for the entire disk). It's used to reduce storage requirements via striping. See the QFS paper (http://db.disi.unitn.eu/pages/VLDBProgram/pdf/industry/p808-...) for a good description of how this works. The basic idea is that with RS you can get 3x replication by splitting the data into 6 pieces stored on different servers, plus three parity blocks. This requires 1.5x storage rather than 3x while still tolerating the loss of any three machines of the nine.
Re:The Elephant was a Trojan Horse: On the Death of Map-Redu...
by erikano on Friday June 27, 2014 @02:43AM
(#7952967)
>[T]ypically in a production context you have RAID for that, and failures tend to be for the entire disk[.]
Does QFS run in addition to other file systems on the storage nodes or does it manage disks directly? You see, I was thinking that maybe ZFS + QFS might be a good idea and would like to know if it's possible. Also, is QFS available for FreeBSD and/or SmartOS storage nodes and clients? How about CoreOS and Debian, are storage nodes and clients available for those?
I thought erasure codes were a much better approach.