Issue #1395 has been updated by konrad rzentarzewski.
interesting screenshot below. i've taken it just after doing "service passenger
stop" - so leaked processed were not killed (despite the apache process exited)
and they keept their active mysql connections (see netstat and mysqladmin).
btw. i've switched postgres to mysql as stored configs backend, as it appears
to work more stable (no sudden disconnects) and leak less.
<pre>
Every 2.0s: passenger-memory-stats | grep -A50 "Passenger processes" ; netstat
-nalp|grep ESTAB ; tail -10 /var/log/httpd/passenger_access.log ; mysqladmin -u
puppet --password... Thu Dec 10 23:22:45 2009
[44m[1m[33m----------- Passenger processes -----------
[37mPID Threads VMSize Private Name
-------------------------------------------[0m
1193 1 59.7 MB 0.1 MB grep -A50 Passenger processes
26882 1 3028.7 MB 1756.4 MB Rack: /usr/share/puppet/rack/puppetmasterd
26894 1 2974.9 MB 821.1 MB Rack: /usr/share/puppet/rack/puppetmasterd
28462 1 1530.1 MB 719.4 MB Rack: /usr/share/puppet/rack/puppetmasterd
### Processes: 4
### Total private dirty RSS: 3296.99 MB
tcp 0 0 127.0.0.1:3306 127.0.0.1:39207
ESTABLISHED 18452/mysqld
tcp 0 0 10.0.4.4:39634 10.0.100.2:3493
ESTABLISHED 2399/upsmon
tcp 0 0 127.0.0.1:39153 127.0.0.1:3306
ESTABLISHED 26894/puppetmasterd
tcp 0 0 127.0.0.1:39145 127.0.0.1:3306
ESTABLISHED 26882/puppetmasterd
tcp 0 0 127.0.0.1:39207 127.0.0.1:3306
ESTABLISHED 28462/puppetmasterd
tcp 0 0 10.0.4.4:22 192.168.240.184:44106
ESTABLISHED 7157/sshd: kondi [p
tcp 0 0 127.0.0.1:3306 127.0.0.1:39145
ESTABLISHED 18452/mysqld
tcp 0 0 127.0.0.1:3306 127.0.0.1:39153
ESTABLISHED 18452/mysqld
172.16.101.98 - - [10/Dec/2009:23:20:59 +0100] "POST /RPC2 HTTP/1.1" 200 170
"-" "XMLRPC::Client (Ruby 1.8.6)"
172.16.101.98 - - [10/Dec/2009:23:21:00 +0100] "POST /RPC2 HTTP/1.1" 200 170
"-" "XMLRPC::Client (Ruby 1.8.6)"
172.16.101.98 - - [10/Dec/2009:23:21:00 +0100] "POST /RPC2 HTTP/1.1" 200 170
"-" "XMLRPC::Client (Ruby 1.8.6)"
172.16.101.98 - - [10/Dec/2009:23:21:01 +0100] "POST /RPC2 HTTP/1.1" 200 170
"-" "XMLRPC::Client (Ruby 1.8.6)"
172.16.101.98 - - [10/Dec/2009:23:21:01 +0100] "POST /RPC2 HTTP/1.1" 200 170
"-" "XMLRPC::Client (Ruby 1.8.6)"
172.16.101.98 - - [10/Dec/2009:23:21:01 +0100] "POST /RPC2 HTTP/1.1" 200 170
"-" "XMLRPC::Client (Ruby 1.8.6)"
172.16.101.98 - - [10/Dec/2009:23:21:02 +0100] "POST /RPC2 HTTP/1.1" 200 120
"-" "XMLRPC::Client (Ruby 1.8.6)"
172.16.101.98 - - [10/Dec/2009:23:21:03 +0100] "POST /RPC2 HTTP/1.1" 200 170
"-" "XMLRPC::Client (Ruby 1.8.6)"
172.16.101.98 - - [10/Dec/2009:23:21:03 +0100] "POST /RPC2 HTTP/1.1" 200 120
"-" "XMLRPC::Client (Ruby 1.8.6)"
172.16.101.98 - - [10/Dec/2009:23:21:04 +0100] "POST /RPC2 HTTP/1.1" 200 170
"-" "XMLRPC::Client (Ruby 1.8.6)"
+-----+--------+-----------------+--------+---------+------+-------+-----------------------+
| Id | User | Host | db | Command | Time | State | Info
|
+-----+--------+-----------------+--------+---------+------+-------+-----------------------+
| 287 | puppet | localhost:39145 | puppet | Sleep | 486 | |
|
| 293 | puppet | localhost:39153 | puppet | Sleep | 487 | |
|
| 328 | puppet | localhost:39207 | puppet | Sleep | 414 | |
|
| 389 | puppet | localhost | | Query | 0 | | show full
processlist |
+-----+--------+-----------------+--------+---------+------+-------+-----------------------+
</pre>
----------------------------------------
Bug #1395: puppet memory usage
http://projects.reductivelabs.com/issues/1395
Author: Peter Meier
Status: Accepted
Priority: Normal
Assigned to: Markus Roberts
Category: plumbing
Target version: 0.25.2
Patch: None
Affected version: 0.25.1
Keywords: memory leaks
Branch:
In a recent discussion about using puppetd with xinetd ("main
thread":http://groups.google.com/group/puppet-users/browse_thread/thread/50c94008469fc395/11687cd0a633f8f4
) it came out that there is some investigation needed on puppetd's memory
usage.
Different people noticed that running puppetd is using a lot of footprint
(links follow), while other noticed that it uses nearly none (links follow)
Notices about high memory usage:
VIRT/RES
"141m/61m":http://groups.google.com/group/puppet-users/msg/75a8bb3b6652bae6
"127m/82m":http://groups.google.com/group/puppet-users/msg/a4a43d3edd585c03 64
bit
"166m/83m":http://groups.google.com/group/puppet-users/msg/1825ed57ff84287f
"183m/96m":http://groups.google.com/group/puppet-users/msg/ecf2cd36b6e1e3a6
version 0.24.4, 64 bit
Notices about low memory usage:
"nothing
specific":http://groups.google.com/group/puppet-users/msg/aac9fade1b906bd9
version 0.24.4
"57m/46m":http://groups.google.com/group/puppet-users/msg/680b2b2760aa8890
version 0.23.1
Personally I can add another memory usage on a 32bit machine, which is rather
low: 85m virt and 69m res, running 0.24.4
Luke then
"noticed":http://groups.google.com/group/puppet-users/msg/573a76e32fba3eb0 that
we should investigate on memory usage in the near future.
Besides the memory consumption of puppetd, also the memory consumption of
puppetmaster was discussed. There Duncan Hill noticed that splitting the
fileserver off the the main puppetmaster "improved the situation
heavily":http://groups.google.com/group/puppet-users/msg/a7083b931b5c4cda ,
however he
"noticed":http://groups.google.com/group/puppet-users/msg/f68347fdb69b8496 that
the manifest puppetmaster still consumes a lot of memory.
There have been also "other reports about memory usage trashing the master and
the
client":http://groups.google.com/group/puppet-users/browse_thread/thread/26aa8025de704cc4/1c9608f58360cdbb,
however this might not be related.
Quick Summary:
We have seen different environments reporting a lot of memory usage. Most of
them seem to be 64bit machines using 0.24.4. One report about low memory usage
was a 0.23.1 version.
Personal additional assumption: And for a first glance it looks like that 64bit
machines double the memory consumption. (Take care of this assumption)
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://reductivelabs.com/redmine/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
