Project

General

Profile

Actions
Copy link

Bug #4297

closed

OSD: memory leak, do_notifies

Added by Samuel Just about 11 years ago. Updated about 11 years ago.

Status:
Rejected
Priority:
Urgent
Assignee:
Samuel Just
Category:
OSD
Target version:
-
% Done:

0%

Source:
Development
Tags:
Backport:
bobtail
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

From the list:

From: "Bryan K. Wright" <>
Sender:
List-ID: <ceph-devel.vger.kernel.org>
X-Mailing-List:

Hi folks,

I've been looking into my problem with OSDs that use
up a lot of memory.  Let running, I've seen them swell to 
over 8 GB of resident memory.  I'd really like to have some
way of limiting the maximum memory footprint of an OSD.
Is there a knob to do this?
I've just today recompiled ceph-osd with tcmalloc
turned on, so I could do some memory profiling.  (The RPMS
from ceph.com don't have it turned on.)  Here's an example
of what I see from pprof:

http://ayesha.phys.virginia.edu/~bryan/junk2.pdf

Any suggestions would be appreciated.

Thanks,
                    Bryan

Files

junk2.pdf (8.66 KB) junk2.pdf pdf pprof dump Samuel Just, 02/28/2013 12:00 PM
Actions
Copy link
 #1

Updated by Samuel Just about 11 years ago

Confirmed, all osds are running v0.56.3.

Actions
Copy link
 #2

Updated by Sage Weil about 11 years ago

this could just be that oen peers are way behind and do_notifies is sending a very large set of past intervals. the large pg logs suggest that there is some degradation..

Actions
Copy link
 #3

Updated by Samuel Just about 11 years ago

  • Status changed from In Progress to Rejected

This was most likely due to a large past intervals set due to a degraded pg, rather than a leak.

Actions
Copy link

Also available in: Atom PDF