memory leak or other problem
Adam Tkac
atkac at redhat.com
Thu Oct 4 08:55:05 UTC 2007
On Wed, Oct 03, 2007 at 03:12:07AM +0900, JINMEI Tatuya / 神明達哉 wrote:
> > Any updates on this issue? One of our DNS stopped responding and Bind
> > needed to be restarted to get it answering again.
>
> I'd first suggest migrating to BIND 9.4 or later, because prior
> versions rely on libc malloc (by default), which can perform very
> poorly depending on the library implementation details.
I don't think so. malloc() implementation will be problem on Solaris box but SLES (I think it uses glibc implementation) should not have any problems.
>
> If 9.4 still causes the same problem (I remember someone else in this
> thread has reported that), I strongly suspect it's somehow related to
> BIND9's heavyweight cache cleaning mechanism: it goes through the
> entire cache database periodically and/or under over-memory situations
> to see if there's any disposable cache entries. I wrote a patch that
> completely eliminates this overhead by cleaning stale entries with an
> LRU-like purge policy and without causing any batch operations.
>
> I found it worked pretty well, but since I myself have never seen the
> inactivity problem like the ones reported in this thread, I'm not
> 100% sure if this really solves the problem. I'm very much interested
> in the effectiveness of this approach, so please let me know if anyone
> of you are willing to test it with real query traffic that would cause
> the reported problem.
>
> JINMEI, Tatuya
> Communication Platform Lab.
> Corporate R&D Center, Toshiba Corp.
> jinmei at isl.rdc.toshiba.co.jp
>
>
More information about the bind-users
mailing list