From: Jim Dowling <jdowling@sics.se>
To: linux-btrfs@vger.kernel.org
Subject: raid5 + HDFS
Date: Sat, 3 Oct 2015 00:07:16 +0200 [thread overview]
Message-ID: <560F0014.9020905@sics.se> (raw)
Hi
I am interested in combining BtrFS RAID-5 with erasure-coded replication
for HDFS. We have an implementation of Reed-Solomon replication for our
HDFS distribution called HopsFS (www.hops.io).
Some of the nice features of HDFS that make it suitable are:
* not many small files
* not excessive snapshotting
* can probably manage disks being close to capacity, as its globally
visible and blocks can be re-balanced in HDFS
What BtrFS could give us:
* stripping within a DataNode using RAID-5
* higher throughput read/write for HDFS clients over 10 GbE without
losing data locality (others are looking at stripping blocks over many
different nodes).
* true snapshotting for HDFS by providing rollback of HDFS blocks
I am concerned (actually, excited!) that RAID-5 is not production ready.
Any guidelines on how mature it is, since the big PR in Feb/March 2015?
What about scrubbing for RAID-5?
Is there anything else I should know?
Btw, here are some links i found about RAID-5:
UREs are not as common on commodity disks - RAID-5 is safer than assumed:
*<https://www.high-rely.com/blog/using-raid5-means-the-sky-is-falling/>https://www.high-rely.com/blog/using-raid5-means-the-sky-is-falling/*
*
Btrfs Linux 4.1 with 5 10K RPM spinning disks:
<http://www.phoronix.com/scan.php?page=article&item=btrfs-raid015610-linux41&num=1>http://www.phoronix.com/scan.php?page=article&item=btrfs-raid015610-linux41&num=1
*Raid*-*5 *Results: ~250 MB/s for sequential reads. 559 MB/s for
sequential writes.
*
next reply other threads:[~2015-10-02 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 22:07 Jim Dowling [this message]
2015-10-02 23:51 ` raid5 + HDFS Martin Tippmann
[not found] ` <CAHT4m=XMsr=o0hVCXohi-cT=51qnB0mR_pK8108rhBQ1uQ_RBA@mail.gmail.com>
2015-10-03 14:50 ` Jim Dowling
[not found] ` <CABL_Pd8Dag2toHtn2_uSkotZoLPktaC=TOZkLiPNjQDevTRcEw@mail.gmail.com>
2015-10-05 4:49 ` Jim Dowling
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=560F0014.9020905@sics.se \
--to=jdowling@sics.se \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.