[Opendnssec-user] Immediate sign & locking issue (1.4.0a2)

Sander Smeenk ssmeenk at freshdot.net
Tue Jul 3 21:46:16 UTC 2012

Quoting Sander Smeenk (ssmeenk at freshdot.net):

> Should i run something else to satisfy conditions for the sign call?

For those interrested:

Today i switched from SQLite3 to MySQL. Migration was quite easy, really.

I tried it in a test-vm first, the database layouts are identical and i
was able to import the sqlite3 data to MySQL with just a few tweaks.
The enforcer (now mysql) picked up on everything just right.

Some stats:
With ~150 configured zones the enforcer 'update zonelist' runtime went
from 15+ minutes to just a few seconds. Right now with ~1000 zones
configured the enforcer needs about 5 minutes to update and there's
no more concurrency locking issues, as predicted.

Furthermore, it seems that after adding a zone and running update
zonelist, the signer will already quickly configure the zone.
It looks like i can skip calling the signer explictly and still get my
signed zone in about a minute which is perfect for now.

| Laundry is the only thing that should be separated by colour!
| 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7  FBD6 F3A9 9442 20CC 6CD2
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.opendnssec.org/pipermail/opendnssec-user/attachments/20120703/0104c15b/attachment.bin>

More information about the Opendnssec-user mailing list