All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jim Schutt" <jaschut@sandia.gov>
To: Mark Nelson <mark.nelson@inktank.com>
Cc: Sage Weil <sage@inktank.com>, ceph-devel@vger.kernel.org
Subject: Re: leveldb compaction overhead
Date: Wed, 5 Jun 2013 13:16:10 -0600	[thread overview]
Message-ID: <51AF8E7A.9050606@sandia.gov> (raw)
In-Reply-To: <51AF8BF2.5090304@inktank.com>

On 06/05/2013 01:05 PM, Mark Nelson wrote:
> 
> FWIW, I've been fighting with some mon/leveldb issues on 24-node test
> cluster causing high CPU utilization, constant reads, laggy osdmap
> updates, and mons dropping out of quorum.  Work is going on in
> wip-mon.  Should have some more testing done later today.  Other than
> some crashing it appears to be behaving much better. ;)

Cool!

I've seen that branch, but haven't had a chance to take it for
a spin yet....

Thanks -- Jim

> 
> Mark



      reply	other threads:[~2013-06-05 19:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29 21:07 leveldb compaction overhead Sage Weil
2013-05-31 21:31 ` Jim Schutt
2013-06-01  0:00   ` Sage Weil
2013-06-05 19:00     ` Jim Schutt
2013-06-05 19:05       ` Mark Nelson
2013-06-05 19:16         ` Jim Schutt [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=51AF8E7A.9050606@sandia.gov \
    --to=jaschut@sandia.gov \
    --cc=ceph-devel@vger.kernel.org \
    --cc=mark.nelson@inktank.com \
    --cc=sage@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.