All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wido den Hollander <wido@42on.com>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Finding out via librados if a cluster is near full
Date: Wed, 29 May 2013 10:24:18 +0200	[thread overview]
Message-ID: <51A5BB32.3040806@42on.com> (raw)
In-Reply-To: <51A5B8EE.5070801@42on.com>

On 05/29/2013 10:14 AM, Wido den Hollander wrote:
> Hi,
>
> Is there a way to find out if a cluster is near full via librados?
>

Yes, there is. (Thanks tnt on IRC!)

There is ofcourse rados_cluster_stat which will give you:

struct rados_cluster_stat_t {
   uint64_t kb, kb_used, kb_avail;
   uint64_t num_objects;
};


One thing here is however that you don't know to what the (near)full 
ratio has been set to. So you have to do your own guessing.

> The reason I'm asking is that I'm working on a deployment of the RADOS
> Gateway and one of the potential problems I see is that the RADOS
> Gateway can keep writing and filling up the whole cluster.
>

So, with the cluster stat information we could implement:

rgw_refuse_write_above_ratio DOUBLE 0.90

> It's obvious that it's the admin's responsibility to make sure that
> doesn't happen, but what I'd like to do is make the RADOS Gateway deny
> PUT requests when the cluster is near full.
>
> That way normal meta data operations (thus writes) can continue, but new
> objects won't be accepted until the cluster has enough space available.
>
> This might also be useful for librbd. Refuse the creation of new RBD
> images so that existing images can continue operating.
>


-- 
Wido den Hollander
42on B.V.

Phone: +31 (0)20 700 9902
Skype: contact42on

  reply	other threads:[~2013-05-29  8:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29  8:14 Finding out via librados if a cluster is near full Wido den Hollander
2013-05-29  8:24 ` Wido den Hollander [this message]
2013-05-31 22:18   ` Dan Mick

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=51A5BB32.3040806@42on.com \
    --to=wido@42on.com \
    --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.