From: Mark Kampe <mark.kampe@inktank.com>
To: Joao Eduardo Luis <joao.luis@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Comments on Ceph.com's blog article 'Ceph's New Monitor Changes'
Date: Tue, 12 Mar 2013 10:54:05 -0700 [thread overview]
Message-ID: <513F6BBD.9060309@inktank.com> (raw)
In-Reply-To: <513DC833.9090806@inktank.com>
It seems to me that the surviving OSDs still remember all of
the osdmap and pgmap history back to "last epoch started"
for all of their PGs. Isn't this enough to enable reconstruction
of all of the pgmaps and osdmaps required to find any copy of
currently stored object?
My history has given me biases, but I prefer reconstruction over
snapshots because:
(a) it enables recovery from more catastrophic incidents
(e.g. a bug has corrupted all of the monitor stores
or a fire has reduced all monitor nodes to slag)
(b) it is less likely to result in inconsistencies involving
object updates after the last snapshot
(c) the ability to reconstruct is a superset of the ability
to audit, so we get consistency audits for free
>> It tends to be a common source of discomfort among potential Ceph
>> users that if their mons ever become unrecoverable, it's almost
>> impossible to recover your data (compare to GlusterFS, where you can
>> always pull data out of Gluster bricks unharmed, at least as long as
>> you don't use striping volumes). With a file backed mon store, I had
>> hoped that eventually this might tie into btrfs snapshots such that
>> you would have been able to roll back to a known good configuration
>> in an emergency. With the switch to leveldb, I no longer foresee that
>> ever happening. Mind sharing your thoughts on that?
prev parent reply other threads:[~2013-03-12 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 12:04 Comments on Ceph.com's blog article 'Ceph's New Monitor Changes' Joao Eduardo Luis
2013-03-12 17:54 ` Mark Kampe [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=513F6BBD.9060309@inktank.com \
--to=mark.kampe@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=joao.luis@inktank.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.