All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Andreas Joachim Peters <Andreas.Joachim.Peters@cern.ch>,
	"Zhou, Yuan" <yuan.zhou@intel.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Question on Ceph LRC design
Date: Mon, 17 Nov 2014 11:30:12 +0100	[thread overview]
Message-ID: <5469CE34.5060202@dachary.org> (raw)
In-Reply-To: <3472A07E6605974CBC9BC573F1BC02E4AE81D81C@CERNXCHG44.cern.ch>

[-- Attachment #1: Type: text/plain, Size: 3054 bytes --]


Hi Andreas,

On 17/11/2014 11:07, Andreas Joachim Peters wrote:> Hi,
> 
> if you want to compute local parities within a plug-in library by adding rows to the encoding matrix, you can still do that. If you can do LRC inside the plug-in more efficienty, one should do it in the plug-in and skip the LRC layer. I have a patch to the ISA plug-in which can do LRC like HDFS Xorbas encoding, but i didn't manage to express that in Loic's generic LRC layer  ... I think it is hard to formulate a generic framework to define LRC as a layer on top and doing the encoding/decoding only in the lowest layer.  Same problem for the shingled EC, which you cannot express in the simple LRC way ...

Could you please remind us the URL of this draft ?

> 
> I see the current LRC layering as a generic tool to use in multi-datacenter setups honouring the locality of chunks because some  of the LRC optimization codes break locality by cross-talk between locations, they reduce the traffic but do not restrict traffic within data centers.

It certainly has its use but it would be nice to have a more specialized and better optimized version that implements most subtle algorithms ;-)

Cheers

> 
> Cheers Andreas.
> ________________________________________
> From: Loic Dachary [loic@dachary.org]
> Sent: 17 November 2014 02:04
> To: Zhou, Yuan; Andreas Joachim Peters
> Cc: ceph-devel@vger.kernel.org
> Subject: Re: Question on Ceph LRC design
> 
> Hi,
> 
> I believe Andreas has a more elaborate answer on this topic. The current implementation is not as good as what is described in the paper you mention, this is correct. My incentive for chosing this path is that I was able to understand it, mainly. It is not much more than stacking layers of erasure coded chunks on top of each other ;-)
> 
> Now that we have this plugin, it would be nice to have another implementation that uses less space and possible even less network when reconstructing. During the OpenStack summit we discussed this with Kevin Greenan and there are promising directions. It would help a lot to have a sample code to study so that it can be adapted to what we have currently in Ceph. Do you know of such an implementation of LRC or other similar code designed to reduce the network bandwidth during reconstruction ?
> 
> Cheers
> 
> On 17/11/2014 01:52, Zhou, Yuan wrote:
>> Hi Loic/Anderas,
>>
>>
>>
>> I was trying to understand the LRC design in Ceph EC. Per my understanding, it seems Ceph was using a slightly different design with the Microsoft LRC: the local parities were calculated with the global parities included. Is there any special consideration on this change?
>>
>> I was asking because in a typical MS LRC design the global and local parities could be calculated at the same time actually(I mean inside the Erasure Code library). But with this new design, we lost this potential optimization.
>>
>>
>>
>> Thanks, -Yuan
>>
> 
> --
> Loïc Dachary, Artisan Logiciel Libre
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

      reply	other threads:[~2014-11-17 10:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <06681238D8946F44A60AA400760A1CBF01E28FBD@SHSMSX104.ccr.corp.intel.com>
2014-11-17  1:00 ` Question on Ceph LRC design Zhou, Yuan
     [not found] ` <06681238D8946F44A60AA400760A1CBF01E290AB@SHSMSX104.ccr.corp.intel.com>
2014-11-17  1:04   ` Loic Dachary
2014-11-17 10:07     ` Andreas Joachim Peters
2014-11-17 10:30       ` Loic Dachary [this message]

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=5469CE34.5060202@dachary.org \
    --to=loic@dachary.org \
    --cc=Andreas.Joachim.Peters@cern.ch \
    --cc=ceph-devel@vger.kernel.org \
    --cc=yuan.zhou@intel.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.