All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Ryan <mike.ryan@inktank.com>
To: Josh Durgin <josh.durgin@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: PG recovery reservation state chart
Date: Tue, 2 Oct 2012 13:40:00 -0700	[thread overview]
Message-ID: <20121002204000.GE8206@splice> (raw)
In-Reply-To: <506B4F11.5070402@inktank.com>

On Tue, Oct 02, 2012 at 01:31:13PM -0700, Josh Durgin wrote:
> Is the local reservation taken in OSD ID order with the remote
> reservations as well? What's the difference between local and remote
> reservations? Are there different limits on remote and local
> reservations?

They come from separate pools. Each pool has a finite number of
reservations, but if one pool has no more slots the other may still
grant reservations.

> If there's more than one possible replica to backfill from could we try
> to reserve others if the first is busy instead of waiting?

I think you may have your backfill terminology backward. We don't
backfill from a replica, we backfill to a replica.

There will never be more than one replica that needs to be backfilled
to.

> Why would a remote backfill reservation fail if the OSD is full
> (disk space)? Backfill doesn't write to the replica, right? Or by
> full, do
> you mean out of reservations?

If the disk on the OSD is near full we reject backfills. This change I
implemented a few weeks ago and was merged last week.

Backfill does write to the replica.

  reply	other threads:[~2012-10-02 20:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 19:48 PG recovery reservation state chart Mike Ryan
2012-10-02 20:02 ` Gregory Farnum
2012-10-02 20:21   ` Mike Ryan
2012-10-02 20:31 ` Josh Durgin
2012-10-02 20:40   ` Mike Ryan [this message]
2012-10-02 20:35 ` Tommi Virtanen
2012-10-02 20:42   ` Mike Ryan
2012-10-02 22:00     ` Josh Durgin
2012-10-02 22:39       ` Mike Ryan
2012-10-02 21:36 ` Sage Weil
2012-10-02 21:43   ` Mike Ryan

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=20121002204000.GE8206@splice \
    --to=mike.ryan@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=josh.durgin@inktank.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.