max-cache-size doesn't work with 9.5.0b1

Fajar A. Nugraha fajar at fajar.net
Wed Feb 20 05:11:12 UTC 2008


On 2/20/08, JINMEI Tatuya / 神明達哉 <Jinmei_Tatuya at isc.org> wrote:
> At Mon, 18 Feb 2008 11:08:38 +0700,
> "Fajar A. Nugraha" <fajar at fajar.net> wrote:
> > I'm experiencing the same problem under RHEL5/ppc, bind 9.5.0b1, 64bit
> > binary, so it's not FreeBSD-specific problem.
> > Max-cache-size is 1G, and yet memory usage (RES) is at 5.5 GB and growing.
> > Similar thing happens with 32bit binary, with the difference that it
> > dies once memory usage is over 4G.
>
> If your operational environment allows, can you try to run the server
> with the following setting?
> - a smaller max-cache-size value (e.g., 128MB), and
> - a relatively smaller datasize value (e.g., 512MB)
>
> Then memory allocation will start failing at some point, and some
> unusual log messages will possibly appear, which might help diagnose
> the problem.

Where will the log appear? syslog? Should I start named with "-g"?
Should your last patch be applied first?

>
> BTW:
> - does this also happen if you build named without threads?
> - does this also happen for BIND 9.4?
>

Haven't checked the non-thread version, but right now for 9.4 the
memory usage seems reasonable enough, with max-cache-size 2G it's now
using 3G RES. It's only running for a day though, I'll have to check
back in a few days.

Regards,

Fajar



More information about the bind-users mailing list