Hi all,
I am observing increasing memory usage by validator component
(mem_mod_validator counter) of Unboud in time. I am running 1.17.1-2 on
latest stable Debian (Bookworm) and have a detailed memory stats in
Grafana. Our six instances of Unbound have the same behaviour. After
some time validator component consumes all available memory on the
server and has to be prevented by a restart. Unbound has following settings:
module-config: "respip validator iterator"
verbosity: 1
val-log-level: 2
logfile: "/var/log/unbound/unbound.log"
log-time-ascii: yes
statistics-interval: 900
statistics-cumulative: yes
extended-statistics: yes
num-threads: 12
num-queries-per-thread: 4096
msg-cache-size: 12G
rrset-cache-size: 24G
key-cache-size: 6G
neg-cache-size: 512M
msg-cache-slabs: 16
rrset-cache-slabs: 16
infra-cache-slabs: 16
key-cache-slabs: 16
infra-cache-numhosts: 1000000
Unbound reaches the limits above in about six days and usage by
mem_cache_rrset and mem_cache_message stops growing. mem_mod_validator
still grows. This is something what can be seen also in previous
versions of Unbound. I can provide detailed stats if needed.
Any help is appreciated.
With regards
Ales Rygl
