Test RRSIG churn on large zones
Observation
Large zones (in order of 10 M RRs) need RRSIG inception and expiration times to be spread out evenly so resigning does not cause CPUs and zone transfers to explode at single point in time. Spreading resigning then causes non-negligible sustained update rate, and that reportedly is or was problem for some providers.
Inspired by https://indico.dns-oarc.net/event/46/contributions/979/
Test ideas
Impact of ongoing resigning on:
-
AXFR -
IXFR -
journal maintenance -
query latency?
I guess, if nothing else, fsync()
and journal compaction might cause some mess.