Hello Klaus, very nice work! I will try to have a look at it very soon. Any other subscribers are welcome to comment too, of course ;)
Kind regards, Peter van Dijk On Sep 14, 2011, at 3:02 PM, Klaus Darilion wrote: > Hi! > > First version of a patch which does: > > - add next_check to domains table > > Postgresql: > ALTER TABLE domains ADD COLUMN next_check INTEGER DEFAULT 0; > CREATE INDEX nextchecktype_index ON domains (next_check,type); > > - instead of calculation refresh-expiration every slave-batch cycle > calculate the next_check in advance and query only for SLAVE zones where > next_check is older than NOW(). > > - added "refresh" and "retry" values to DomainInfo struct. > > - extended setFresh() function to set also next_check column > > - modified gsql backend to set next_check on UPDATEs > - bind backend just ignores next_check > > - on transfer failure UPDATE next_check with 'retry' value (there are > some scenarios where the retry value is not used, e.g. if SOA query > fails, there is no UPDATE to domain tables) > > - tested with PowerDNS trunk version (not in production yet) > > - modified PostgreSQL SQL queries > > Probably the SQL queries for other databases need to be extended as > well, using the database's support for epoch calculation of NOW(). > > Maybe someone wants to review the patch and give some comments. > > regards > Klaus > <slave-next_check-patch.txt>_______________________________________________ > Pdns-users mailing list > [email protected] > http://mailman.powerdns.com/mailman/listinfo/pdns-users _______________________________________________ Pdns-users mailing list [email protected] http://mailman.powerdns.com/mailman/listinfo/pdns-users
