> Is osd.1 using the heap profiler as well? Keep in mind that active use > of the memory profiler will itself cause memory usage to increase — > this sounds a bit like that to me since it's staying stable at a large > but finite portion of total memory. Well, the memory consumption was already high before the profiler was started. So yes with the memory profiler enable an OSD might consume more memory but this doesn't cause the memory leaks. Any ideas? Nothing to say about my scrumbing theory? Thanks! -- Regards, Sébastien Han. On Thu, Jan 10, 2013 at 10:44 PM, Gregory Farnum <greg@xxxxxxxxxxx> wrote: > On Wed, Jan 9, 2013 at 10:09 AM, Sylvain Munaut > <s.munaut@xxxxxxxxxxxxxxxxxxxx> wrote: >> Just fyi, I also have growing memory on OSD, and I have the same logs: >> >> "libceph: osd4 172.20.11.32:6801 socket closed" in the RBD clients > > That message is not an error; it just happens if the RBD client > doesn't talk to that OSD for a while. I believe its volume has been > turned down quite a lot in the latest kernels/our git tree. > -Greg -- 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
