From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: Sage Weil <sweil@redhat.com>, Haomai Wang <haomaiwang@gmail.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: ceph-disk vs keyvaluestore
Date: Thu, 02 Oct 2014 12:46:44 +1300 [thread overview]
Message-ID: <542C9264.9090300@catalyst.net.nz> (raw)
In-Reply-To: <alpine.DEB.2.00.1409292103250.6593@cobra.newdream.net>
On 30/09/14 17:05, Sage Weil wrote:
> On Tue, 30 Sep 2014, Haomai Wang wrote:
>> Hi sage,
>>
>> What do you think use existing ObjectStore::peek_journal_fsid
>> interface to detect whether journal needed.
>>
>> KeyValueStore and MemStore could set passing argument "fsid" to zero
>> to indicate no journal.
>
> I'm not sure it's a good fit... it's called on an existing store and tells
> you something about it. I would probably expect a zeroed fsid to mean
> that the specified journal is empty or does not exist, not that it doesn't
> need to exist.
>
> What we need, on the other hand, is something that just tells us whether
> we should create a journal...
>
>
And perhaps the "type" (probably not the right word) of journal:
- filestore: device or filesystem
- rocksdb: filesystem (wal directory)
- leveldb: none (I think)
FWIW, it looks like the log files for leveldb *could* benefit from being
placed somewhere else (e.g on faster storage). Is it worthwhile
suggesting to the leveldb devs?
Cheers
Mark
next prev parent reply other threads:[~2014-10-01 23:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 23:48 ceph-disk vs keyvaluestore Sage Weil
2014-09-30 2:23 ` Haomai Wang
2014-09-30 4:00 ` Haomai Wang
2014-09-30 4:05 ` Sage Weil
2014-10-01 23:46 ` Mark Kirkwood [this message]
2014-10-01 23:53 ` Sage Weil
2014-10-02 5:25 ` Haomai Wang
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=542C9264.9090300@catalyst.net.nz \
--to=mark.kirkwood@catalyst.net.nz \
--cc=ceph-devel@vger.kernel.org \
--cc=haomaiwang@gmail.com \
--cc=sweil@redhat.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.