[bind10-dev] it takes long time to IXFR

[JINMEI Tatuya / 神明達哉]

At Fri, 29 Mar 2013 16:59:37 +0900,
Yoshitaka Aharen <aharen at jprs.co.jp> wrote:
> 
> Hello,
> 
> On Wed, 27 Mar 2013 13:03:27 -0700
> JINMEI Tatuya / 神明達哉 <jinmei at isc.org> wrote:
> 
> > At Wed, 27 Mar 2013 13:17:30 +0900,
> > Yoshitaka Aharen <aharen at jprs.co.jp> wrote:
> > 
> > > Yes, we can apply a patch to the experimental server if it is needed.
> > > However, I must hide some part of logs as it may contain sensitive
> > > information.
> > > I haven't tried yet but the situation could be reproduced with creating
> > > a zone with some millions of records, I guess.
> > 
> > Could you apply the patch attached and check full debug logs while
> > updating the zone in IXFR?  It logs owner names, but I suspect it's
> > not data dependent, so it should be removed or obscured if you report
> > the results publicly.
> Thank you for making the patch. We've applied it and ran IXFR.
> Unfortunately the logfile has grown to over 1GB. Could you please let me
> know directly what type of log are needed and how to pass it to you?

I'd be interested in these for a single IXFR session (that takes a
long time):

% DATASRC_DATABASE_ADDDIFF updated diff table for add: %1 %2 %3
% DATASRC_DATABASE_DELETEDIFF updated diff table for delete: %1 %2 %3
% DATASRC_DATABASE_ADDNSEC3 added NSEC3 RR: %1 %2
% DATASRC_DATABASE_ADDRR added RR: %1 %2 %3
% DATASRC_DATABASE_DELETENSEC3 deleted NSEC3 RR: %1 %2
% DATASRC_DATABASE_DELETERR deleted RR: %1 %2 %3

in addition to DATASRC_SQLITE_CONNOPEN and DATASRC_SQLITE_DROPCONN
before and after them.

I guess most of the logs are for building in-memory zone after
completing the IXFR.  They are not of our interest.

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.