From: Nigel Williams <nigel.williams-w4dW+7W4mDC6c6uEtOJ/EA@public.gmane.org>
To: ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
Cc: ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: v0.87 Giant released
Date: Thu, 30 Oct 2014 10:40:38 +1100 [thread overview]
Message-ID: <54517AF6.6030408@utas.edu.au> (raw)
In-Reply-To: <alpine.DEB.2.00.1410291454570.1234-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
On 30/10/2014 8:56 AM, Sage Weil wrote:
> * *Degraded vs misplaced*: the Ceph health reports from 'ceph -s' and
> related commands now make a distinction between data that is
> degraded (there are fewer than the desired number of copies) and
> data that is misplaced (stored in the wrong location in the
> cluster).
Is someone able to briefly described how/why misplaced happens please, is it repaired
eventually? I've not seen misplaced (yet).
> leveldb_write_buffer_size = 32*1024*1024 = 33554432 // 32MB
> leveldb_cache_size = 512*1024*1204 = 536870912 // 512MB
I noticed the typo, wondered about the code, but I'm not seeing the same values anyway?
https://github.com/ceph/ceph/blob/giant/src/common/config_opts.h
OPTION(leveldb_write_buffer_size, OPT_U64, 8 *1024*1024) // leveldb write buffer size
OPTION(leveldb_cache_size, OPT_U64, 128 *1024*1024) // leveldb cache size
next prev parent reply other threads:[~2014-10-29 23:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 21:56 v0.87 Giant released Sage Weil
[not found] ` <alpine.DEB.2.00.1410291454570.1234-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2014-10-29 23:40 ` Nigel Williams [this message]
[not found] ` <54517AF6.6030408-w4dW+7W4mDC6c6uEtOJ/EA@public.gmane.org>
2014-10-30 5:54 ` Sage Weil
[not found] ` <alpine.DEB.2.00.1410292251440.27022-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2014-10-30 8:37 ` Joao Eduardo Luis
[not found] ` <5451F8DD.3020907-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org>
2014-11-12 13:32 ` debian Only
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=54517AF6.6030408@utas.edu.au \
--to=nigel.williams-w4dw+7w4mdc6c6uetoj/ea@public.gmane.org \
--cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.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.