Ticket #403 (closed defect: fixed)

Opened 18 months ago

Last modified 16 months ago

Possible memory leak in PowerDNS Authoritative 3.0

Reported by: anon Owned by: ahu
Priority: normal Milestone:
Component: auth Version: 3.0
Severity: normal Keywords: PowerDNS Authoritative
Cc: angele@…

Description

We updated a PowerDNS 2.9.22 to 3.0. And we have configured two backends:

launch=pipe,bind

But it doesn't work as in 2.9.22. After about 16 hours pdns_server has increased to 4 GB (end of memory):

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 13913 root 20 0 4267m 3.9g 3720 S 74 66.1 387:55.69 pdns_server

We suspect it is because the many different queries we receive. It seems pdns_server is caching our result packets although we turned off caching, see below.

We sent more details via email.

This is our configuration:

allow-recursion= cache-ttl=0 negquery-cache-ttl=0 config-dir=/etc/powerdns daemon=yes default-soa-name=a.misconfigured.dns.server do-ipv6-additional-processing=yes launch=pipe,bind bind-config=/etc/powerdns/bind/named.conf bind-check-interval=600 local-address=XXX.XXX.XXX.XXX,127.0.0.1 master=yes max-tcp-connections=500 out-of-zone-additional-processing=no pipebackend-abi-version=1 pipe-command=/var/powerdns/pipe/pipebe pipe-timeout=20 query-cache-ttl=0 recursive-cache-ttl=0 max-cache-entries=10000

Change History

Changed 16 months ago by ahu

  • status changed from new to closed
  • resolution set to fixed

PowerDNS 3.0 wasted memory on a grand scale by caching too much, see 2287, plus fix in 2328 for not cleaning metadata properly. Thanks!

Note: See TracTickets for help on using tickets.