How to check for high memory in the recursor process #15268
Replies: 5 comments 6 replies
-
Would you mind telling us the amount of memory the server has? |
Beta Was this translation helpful? Give feedback.
-
The first two numbers are the configures maximum number of entries. To get the current number of entries for the two main caches:
See https://docs.powerdns.com/recursor/metrics.html#gathered-information for other metrics. Looking at https://docs.powerdns.com/recursor/performance.html#memory-usage, it feels your memory usage is pretty high, |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
I did a test with a tight shell loop doing |
Beta Was this translation helpful? Give feedback.
-
The reload code replaces the whole Lua context for each worker thread, so I'm not sure what causes your memory growing. It must be some resource that is not cleaned up, but without further details it is impossible to tell. So far my my local testing showed that the reload mechanism itself is working fine and not causing growth. |
Beta Was this translation helpful? Give feedback.
-
Description:
I am conducting an experiment where I built a Docker image of Ubuntu 22.04 and ran the container of the image. I successfully started a recursive service inside the container. At first, the process only used 9% of the server's memory, but after running for a while, I found through the top command that the process used more than 70% of the server's memory and continued to rise. Eventually, the process was killed by the system due to OOM. How can I investigate where the problem lies. Can you give me some suggestions for checking? Thanks a lot.
Information:
/usr/sbin/pdns_recursor --daemon=no --write-pid=no --disable-syslog --log-timestamp=no
Beta Was this translation helpful? Give feedback.
All reactions