All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Ten Clay <aarontc@aarontc.com>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: [ceph-users] Extremely high OSD memory utilization on Kraken 11.2.0 (with XFS -or- bluestore)
Date: Fri, 2 Jun 2017 14:56:55 -0700	[thread overview]
Message-ID: <CAFFcurpFgvo4em=a4D27xtcszeib4Zsw6VM3oq3_0H8Xis8-Pw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1705160133070.3646@piezo.novalocal>

On Mon, May 15, 2017 at 6:35 PM, Sage Weil <sage@newdream.net> wrote:
> On Mon, 15 May 2017, Aaron Ten Clay wrote:
>> Hi Sage,
>>
>> No problem. I thought this would take a lot longer to resolve so I
>> waited to find a good chunk of time, then it only took a few minutes!
>>
>> Here are the respective backtrace outputs from gdb:
>>
>> https://aarontc.com/ceph/dumps/core.ceph-osd.150.082e9ca887c34cfbab183366a214a84c.6742.1492634493000000000000.backtrace.txt
>> https://aarontc.com/ceph/dumps/core.ceph-osd.150.082e9ca887c34cfbab183366a214a84c.7202.1492634508000000000000.backtrace.txt
>
> Looks like it's in BlueFS replay.  Can you reproduce with 'log max recent
> = 1' and 'debug bluefs = 20'?
>
> It's weird... the symptom is eating RAM, but it's hitting an assert during
> relay on mount...
>
> Thanks!
> sage
>

Sage:

Here's the log from osd.1: https://aarontc.com/ceph/ceph-osd.1.log.bz2

I'm not entirely sure the issue was reproduced. The symptom of running
away with all the RAM still happens, but there is so much in this log
I'm not sure if it has what you're looking for.

-Aaron

  reply	other threads:[~2017-06-02 21:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAFFcurqEctQ2fHHDcGYfy3YCuaq9DxZr0VU4e8dNVACNVLDmqA@mail.gmail.com>
     [not found] ` <CAFFcurqEctQ2fHHDcGYfy3YCuaq9DxZr0VU4e8dNVACNVLDmqA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-04-17 15:15   ` Extremely high OSD memory utilization on Kraken 11.2.0 (with XFS -or- bluestore) Sage Weil
     [not found]     ` <alpine.DEB.2.11.1704171457320.10661-qHenpvqtifaMSRpgCs4c+g@public.gmane.org>
2017-04-19 23:18       ` Aaron Ten Clay
     [not found]         ` <CAFFcurrA8BKF0a+9gdGAsTDbE78ci9X8dwEaWEycoF4DNQN8uw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-04 20:57           ` Aaron Ten Clay
     [not found]             ` <CAFFcuroumvWGZA+KC4V7wOiF9T0y7k9v+Ms=GgOh+bGm8gP__g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-04 21:25               ` Sage Weil
     [not found]                 ` <alpine.DEB.2.11.1705042124210.3646-qHenpvqtifaMSRpgCs4c+g@public.gmane.org>
2017-05-15 23:01                   ` Aaron Ten Clay
2017-05-16  1:35                     ` [ceph-users] " Sage Weil
2017-06-02 21:56                       ` Aaron Ten Clay [this message]
2017-04-19 23:22     ` Aaron Ten Clay

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='CAFFcurpFgvo4em=a4D27xtcszeib4Zsw6VM3oq3_0H8Xis8-Pw@mail.gmail.com' \
    --to=aarontc@aarontc.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sage@newdream.net \
    /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.