Thu Aug 16 07:59:02 PDT 2012
- Previous message: [Slony1-bugs] [Bug 272] slonik can segfault scanning input
- Next message: [Slony1-bugs] [Bug 275] monitor_thread leaks memory
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=275 Summary: monitor_thread leaks memory Product: Slony-I Version: devel Platform: PC OS/Version: Linux Status: NEW Severity: enhancement Priority: low Component: slon AssignedTo: slony1-bugs at lists.slony.info ReportedBy: ssinger at ca.afilias.info CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 This was observed against slony 2.1.1 If you have a slon running with the monitor thread on it seems to leak memory. I was able to observe this with the disorder_test where I modified SubscribeUnderLoad to continue with the slons running after the subscription was done. I then watched the VMRSS of a the slon over time. It seemed to grow at a rate of 100k per 5 minutes. ssinger at ssinger-laptop:~/src/slony1-engine/slony1-engine/clustertest$ while true ; do grep "VmRSS" /proc/19308/status; sleep 60; done VmRSS: 1824 kB VmRSS: 1856 kB VmRSS: 1880 kB VmRSS: 1908 kB VmRSS: 1924 kB VmRSS: 1952 kB VmRSS: 1972 kB VmRSS: 2000 kB When I restarted the slon with the monitor_thread disabled the slon didn't grow every minute. This investigation was prompted from an observation in the field that 2.1 was using much more memory that 2.0.6 -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.
- Previous message: [Slony1-bugs] [Bug 272] slonik can segfault scanning input
- Next message: [Slony1-bugs] [Bug 275] monitor_thread leaks memory
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list