All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wido den Hollander <wido@widodh.nl>
To: ceph-devel <ceph-devel@vger.kernel.org>
Subject: higher level library for storing large(r) RADOS objects
Date: Thu, 03 May 2012 08:07:10 +0200	[thread overview]
Message-ID: <4FA2208E.5010208@widodh.nl> (raw)

Hi,

I've been talking to Josh today and we've been talking a bit about 
storing large objects in RADOS.

One of the problem I currently see with using RADOS is storing really 
large objects.

RADOS objects are stored on the OSD as a whole file, so potentially a 
single RADOS object could press an OSD over the full_ratio and stalling 
the whole cluster.

This also shows another problem. It this object is heavily used a couple 
of OSDs will be very busy with the I/O's for this object.

So I was thinking about an library on top of RADOS which is kind of 
similar to RBD, but it's only focused on storing objects.

The first object in a pool could have a couple of xattrs:

object1
- stripe_size: 4096
- size: 40960

Based on the xattr operation we know where to read or write when asked 
for a specific offset and length.

object1, object1_1, object1_2, until object1_9

Potentially this could also be used for the RADOS Gateway? Since that 
will suffer from the same problem when you want to scale out.

With the RAODS Gateway you can't control a user storing a 200G tar file 
with his backups in it, you never know.

It's just a thought but I just wanted to get it out there and check out 
the opinions.

Comments? Suggestions?

Wido

             reply	other threads:[~2012-05-03  6:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03  6:07 Wido den Hollander [this message]
2012-05-03  6:21 ` higher level library for storing large(r) RADOS objects Yehuda Sadeh Weinraub
2012-05-03 15:19   ` Wido den Hollander

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=4FA2208E.5010208@widodh.nl \
    --to=wido@widodh.nl \
    --cc=ceph-devel@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.