From: Loic Dachary <loic@dachary.org>
To: Kjetil Babington <babingto@gmail.com>, ceph-devel@vger.kernel.org
Subject: Re: Ceph erasure coding
Date: Thu, 22 Oct 2015 18:59:40 +0200 [thread overview]
Message-ID: <562915FC.9090401@dachary.org> (raw)
In-Reply-To: <CA+nGFBodcEq0vOvuFP1Od0zVCyk_9PufsRSYBJYi1W4p_vh+7g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
Hi,
On 22/10/2015 18:44, Kjetil Babington wrote:
> Hi,
>
> I have a question about the capabilities of the erasure coding API in
> Ceph. Let's say that I have 10 data disks and 4 parity disks, is it
> possible to create an erasure coding plugin which creates 20 data
> chunks and 8 parity chunks, and then places two chunks on each osd?
>
> Or said maybe a bit simpler is it possible for two or more chunks from
> the same encode operation to be placed on the same osd?
This is more a question of creating a crush ruleset that does it. The erasure code plugin encodes chunks but the crush ruleset decides where they are placed.
Cheers
>
> - Kjetil Babington
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-10-22 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 16:44 Ceph erasure coding Kjetil Babington
2015-10-22 16:59 ` Samuel Just
2015-10-22 16:59 ` Loic Dachary [this message]
2015-10-26 18:34 ` Kjetil Babington
2015-10-26 19:16 ` Loic Dachary
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=562915FC.9090401@dachary.org \
--to=loic@dachary.org \
--cc=babingto@gmail.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.