From: Mark Kampe <Mark.Kampe@dreamhost.com>
To: Tommi Virtanen <tommi.virtanen@dreamhost.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: efficient removal of old objects
Date: Wed, 01 Feb 2012 16:11:30 -0800 [thread overview]
Message-ID: <4F29D4B2.6010608@dreamhost.com> (raw)
In-Reply-To: <CAORUGqCkRzAbXVjGvVDGX=MxURMy5NijsdPGRgWDpgT3_CyMow@mail.gmail.com>
On 01/31/12 17:02, Tommi Virtanen wrote:
> To make my point even clearer: point me to another data store that has
> that idiom.
(a) Automatic expiration and deletion is, and has long been, a
standard feature of archival systems ... and our RADOS
clouds are much larger than most archival systems.
(b) I have no competent opinions on the short term solution to this
particular problem, but in the longer term I do not believe
that garbage collection can or should be entrusted to clients.
Clients are ephemeral and cannot be depended on to remember,
a few years (or even hours) from now, that there were some
files they were supposed to delete.
IMHO, object store intelligence is not merely about back-ground
replication and migration, but about "being able to take
responsibility for the life cycle of the data they hold".
The amount of data we store will quickly grow beyond the
ability of external agents to manage it, and lifecycle
automation will become increasingly critical.
next prev parent reply other threads:[~2012-02-02 0:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 0:33 efficient removal of old objects Sage Weil
2012-02-01 0:52 ` Josh Durgin
2012-02-01 1:02 ` Tommi Virtanen
[not found] ` <CAC-hyiExnN6CxMh=+5tLoZy3T0=Mx6Y3P796rG3L01mZ-=+vOg@mail.gmail.com>
2012-02-01 8:04 ` Yehuda Sadeh Weinraub
2012-02-02 0:11 ` Mark Kampe [this message]
2012-02-01 1:19 ` Josh Durgin
2012-02-01 8:26 ` Yehuda Sadeh Weinraub
2012-02-01 17:39 ` Gregory Farnum
2012-02-01 18:53 ` Yehuda Sadeh Weinraub
2012-02-01 19:35 ` Gregory Farnum
2012-02-01 20:01 ` Yehuda Sadeh Weinraub
2012-02-01 19:43 ` Sage Weil
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=4F29D4B2.6010608@dreamhost.com \
--to=mark.kampe@dreamhost.com \
--cc=ceph-devel@vger.kernel.org \
--cc=tommi.virtanen@dreamhost.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.