All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Barber <steve.barber@nist.gov>
To: Gregory Farnum <greg@inktank.com>
Cc: Jeff Mitchell <jeffrey.mitchell@gmail.com>,
	ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Using locally replicated OSDs to reduce Ceph replication
Date: Wed, 17 Apr 2013 19:02:00 -0400	[thread overview]
Message-ID: <20130417230200.GC4565@nist.gov> (raw)
In-Reply-To: <CAPYLRzj0LMK_hCArN4K2t9DyLQsjqx-ysHidvvXi4=fDVBbdFw@mail.gmail.com>

On Wed, Apr 17, 2013 at 06:23:43PM -0400, Gregory Farnum wrote:
> On Wed, Apr 17, 2013 at 3:02 PM, I wrote:
> > In particular, has anyone tried making a big RAID set (of any type) and
> > carving out space (logical volumes, zvols, etc.) to become virtual OSDs?
> > Any architectural gotchas with this idea?
> 
> I believe there are some people running with this architecture;
> there's just less knowledge about how it behaves in the long term. It
> should be fine subject to the standard issues with RAID5/6 small
> writes, which OSDs do a lot of (and I don't know why you'd bother
> using a mirroring RAID instead of Ceph replication!).
> I can say that there would be little point to carving up the arrays
> into multiple OSDs; other than that, have fun. :)
> -Greg
> Software Engineer #42 @ http://inktank.com | http://ceph.com

So you think it'd be worth trying just running a few really large OSDs in
a configuration like that?  I wasn't sure that would scale as well, but I'm
still pretty new to Ceph.

About mirroring/RAID vs. Ceph replication, I was under the impression that
there would be a lot of extra network traffic generated by writes with so
many replicas which might not be optimal.  True enough about RAID 5/6 small
writes.

Just gotta try it and see I guess.

Thanks for the feedback!
Steve

  reply	other threads:[~2013-04-17 23:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17 22:02 Using locally replicated OSDs to reduce Ceph replication Steve Barber
2013-04-17 22:23 ` Gregory Farnum
2013-04-17 23:02   ` Steve Barber [this message]
2013-04-17 23:09     ` Gregory Farnum

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=20130417230200.GC4565@nist.gov \
    --to=steve.barber@nist.gov \
    --cc=ceph-devel@vger.kernel.org \
    --cc=greg@inktank.com \
    --cc=jeffrey.mitchell@gmail.com \
    /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.