Looks like it would have to be the pg_interval_t maps copied into the MOSDPGNotify messages or something in the OSDMap... Can you confirm that all of your OSDs are all running the same version? There are two paths in that method, one for handling contemporary OSDs and a second path for handling OSDs prior to 0.5something. Thanks for the heap map! -Sam On Thu, Feb 28, 2013 at 10:57 AM, Bryan K. Wright <bkw1a@xxxxxxxxxxxxxxxxxxxxxxxx> wrote: > 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 > > -- > ======================================================================== > Bryan Wright |"If you take cranberries and stew them like > Physics Department | applesauce, they taste much more like prunes > University of Virginia | than rhubarb does." -- Groucho > Charlottesville, VA 22901| > (434) 924-7218 | bryan@xxxxxxxxxxxx > ======================================================================== > > > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
