All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Lauhoff <lauhoff@uni-mainz.de>
To: ceph-devel@vger.kernel.org
Subject: Re: Started developing a deduplication feature
Date: Fri, 8 Apr 2016 17:01:24 +0200	[thread overview]
Message-ID: <871t6gkuuz.fsf@uni-mainz.de> (raw)
In-Reply-To: <87wpodv99m.fsf@uni-mainz.de>


Hi list,
short recap of the dedup topic from the CDM on Wednesday:


The main change from the original mail is not to add a PG backend, but
rather use Object Redirects (Tiering v2).
Another backend would have to implement its own replication for
recipes and increase the OSD code base just for dedup. Redirects are
useful beyond deduplication.


The CAS pool design was refined: An object class should handle the ref
counting and content addressing. The pool should also only
allow access through this object class to prevent collisions with
regular objects and support immutable objects.


There was also the idea of client-side deduplication by using metadata
that clients like RGW store. This would save the additional round trip
that object redirects add.


I'll be working on the CAS pool first, since there
is ongoing refactoring in the ReplicatedPG code base. I'll work out a
more detailed design document for the CAS pool soon.


~irq0
--
Marcel Lauhoff
Mail: lauhoff@uni-mainz.de
XMPP: mlauhoff@jabber.uni-mainz.de

  reply	other threads:[~2016-04-08 15:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-01 17:25 Started developing a deduplication feature Marcel Lauhoff
2016-04-01 21:31 ` Sage Weil
2016-04-04 12:38   ` Marcel Lauhoff
2016-04-08 15:01     ` Marcel Lauhoff [this message]
2016-04-08 15:18       ` Sage Weil
2016-04-08 21:50       ` Shinobu Kinjo
2016-04-12  9:35         ` Marcel Lauhoff
2016-04-28 21:08   ` Allen Samuels

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=871t6gkuuz.fsf@uni-mainz.de \
    --to=lauhoff@uni-mainz.de \
    --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.