perlbal memory leak?
Mark Smith
junior at danga.com
Sat Dec 3 00:10:34 UTC 2005
The "stats" plugin you are using leaks memory. Known bug, unfixed. It's
something funky that I haven't sat down to figure out yet. Please feel
free to have at it if you want... :)
-jr
On Fri, Dec 02, 2005, Ask Bj?rn Hansen wrote:
>
> Hi,
>
> One of my perlbal installations keep leaking(?) memory. Not at a
> super rapid rate, but that's mostly because it's not getting too much
> traffic. Just now after about 4M requests it was at ~500MB. I've
> included the configuration file below. The option option I use is --
> config to specify the configuration file.
>
> I use the latest version from CVS. We use RHEL3 on this box (and
> others without the problem). perl 5.8.3 (the same on this box and
> the others).
>
> In the output (I run it under supervise) I a lot of lines like the
> one below are slowly adding up. I just saw them now and haven't
> looked at the code to see if it could be related.
>
> Undef client_ip (Perlbal::ClientProxy=ARRAY(0xb3c7dde8)) in
> assign_client. Closing. at lib/Perlbal/BackendHTTP.pm line 179.
> Undef client_ip (Perlbal::ClientProxy=ARRAY(0xb3c9cbd4)) in
> assign_client. Closing. at lib/Perlbal/BackendHTTP.pm line 179.
>
> Any ideas?
>
>
> - ask
>
> SERVER max_connections = 10000
> LOAD stats
> SERVER max_reproxy_connections = 50
>
> CREATE POOL xrl_pool
> POOL xrl_pool ADD 127.0.0.1:8233
>
> CREATE SERVICE web_proxy
> SET role = reverse_proxy
> SET pool = xrl_pool
> SET listen = 216.52.237.134:80
> SET plugins = stats
> SET trusted_upstream_proxies = 10.0.0.0/24
> SET connect_ahead = 2
> SET persist_backend = on
> SET max_backend_uses = 200
> SET backend_persist_cache = 4
> SET verify_backend = on
> ENABLE web_proxy
>
> CREATE SERVICE mgmt
> SET mgmt.role = management
> SET mgmt.listen = 0.0.0.0:8065
> ENABLE mgmt
>
>
> --
> http://www.askbjoernhansen.com/
>
--
Junior (aka Mark Smith)
junior at danga.com
Software Engineer
Six Apart / Danga Interactive
More information about the perlbal
mailing list