On 6/22/07, Otte, Joerg <[EMAIL PROTECTED]> wrote:
> one more question... was the cluster very active during that time? > ie. moving resources around? Yes, the resource group (and contained 7 resources) were moved once per Minute - (to see if this works was the primary goal of the testcase).
ok - that gives me a pretty good idea of the size of the leak feel free to bug me again if you dont hear from me again on this thanks!
-----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von ext Andrew Beekhof Gesendet: Freitag, 22. Juni 2007 11:22 An: High-Availability Linux Development List Betreff: Re: [Linux-ha-dev] Hb-2.0.9/SuSE: memory leak in crmd/lrmdundersolaris 10/i386 On 6/22/07, Otte, Joerg <[EMAIL PROTECTED]> wrote: > > > are these the only two processes growing? > There are other (smaller) increments as well. > Here is the complete list: > > RSS VSZ RSS VSZ > 1708 4496 1708 4496 /usr/sfw/lib/python2.3/heartbeat/ha_logd > 1316 4396 1316 4396 /usr/sfw/lib/python2.3/heartbeat/ha_logd > 9204 12788 9204 12788 /usr/sfw/lib/python2.3/heartbeat/heartbeat > 1292 5720 1292 5720 /usr/sfw/lib/python2.3/heartbeat/heartbeat > 1500 5776 1500 5776 /usr/sfw/lib/python2.3/heartbeat/heartbeat > 1548 5776 1548 5776 /usr/sfw/lib/python2.3/heartbeat/heartbeat > 1500 5776 1500 5776 /usr/sfw/lib/python2.3/heartbeat/heartbeat > 1524 5776 1524 5776 /usr/sfw/lib/python2.3/heartbeat/heartbeat > 2468 4632 2500 4664 /usr/sfw/lib/python2.3/heartbeat/ccm > 5484 8524 5496 8524 /usr/sfw/lib/python2.3/heartbeat/cib > 5840 7860 6496 8516 /usr/sfw/lib/python2.3/heartbeat/lrmd > 2788 4652 2884 4748 /usr/sfw/lib/python2.3/heartbeat/stonithd > 2500 4576 2500 4576 /usr/sfw/lib/python2.3/heartbeat/attrd > 5716 7580 6488 8356 /usr/sfw/lib/python2.3/heartbeat/crmd > 3316 6704 3316 6704 /usr/sfw/lib/python2.3/heartbeat/mgmtd > 4476 6500 4480 6500 /usr/sfw/lib/python2.3/heartbeat/tengine > 6396 10372 6396 10372 /usr/sfw/lib/python2.3/heartbeat/pengine > > > over what interval is the growth? > 12 hours > > > are there any tools on solaris to show where the leaks are coming > > from? (on linux we have valgrind, support for which is easily enabled > > in heartbeat) > I don't know of any tool which comes for free. > ok, thanks for that info. one more question... was the cluster very active during that time? ie. moving resources around? anyway, i'll be sure to run it through valgrind and see what it has to say _______________________________________________________ Linux-HA-Dev: [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/ _______________________________________________________ Linux-HA-Dev: [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
_______________________________________________________ Linux-HA-Dev: [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
