All of lore.kernel.org
 help / color / mirror / Atom feed
From: Svein-Erik Lund <sel@selund.se>
To: ceph-devel@vger.kernel.org
Subject: Feature request regarding size and min_size on pools
Date: Tue, 10 Sep 2013 16:21:27 +0400 (MSD)	[thread overview]
Message-ID: <750758449.922.1378815687370.JavaMail.root@mail> (raw)
In-Reply-To: <1712504592.851.1378813557601.JavaMail.root@mail>

Hello,

We are implementing ceph as storage backend for some systems. 
Unfortunately we have to use a posix filesystem for storing the data.

To accomplish this we have implemented a solution quite similar to what Sebastien Han has described on his blog here http://www.sebastien-han.fr/blog/2012/07/06/nfs-over-rbd/

Now to our problem. We want to be sure that a write is replicated before we get a ack. Therefor we have set pg size to 2, and min_size to 2 as we have seen that a sudden removal of one osd can lead to data loss with min_size set to 1.

The problem now is that if one osd goes down some pg's will end up incomplete, and no io operations will be allowed to the rbd. 

This problem could be solved a couple of ways

1) An option could be set so that writes always is done to the number of replicas as size before the write is acknowledged.
2) If a situation where one a pg ends up in a incomplete state ceph tries to resolv the situation by doing a recovery of the pg's in question.

For us adding a third replica isn't a feasible solution, 1) we have our data in two locations 2) The cost would be to high.

       reply	other threads:[~2013-09-10 12:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1712504592.851.1378813557601.JavaMail.root@mail>
2013-09-10 12:21 ` Svein-Erik Lund [this message]
2013-09-10 13:51   ` Feature request regarding size and min_size on pools Sylvain Munaut

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=750758449.922.1378815687370.JavaMail.root@mail \
    --to=sel@selund.se \
    --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.