auto-tune transfers-in, transfers-out, transfers-per-ns and friends
Description
The problem, as noted in Support ticket #21991, is that without testing in a production environment and under specific circumstances (speed of network, configuration of primaries per zone, reachability, rate of zone update propagation and so on), it's hard to know what sane values to give to the options for tuning zone transfers. The types of things that need to be optimised are:
- Speed of synchronisation/completion of refreshes following a secondary server restart
- Effective use of CPU resources so that servers are not idling while there is work that could be done
- No interruption to client services during zone refreshes (for servers that are currently client-facing)
- Effective onward zone update propagation/refreshes (for servers that are intermediaries in the zone update propagation path)
- Speed of propagation of zone updates during normal operation (i.e. not when restarting something...)
Request
I'd like transfers-in, transfers-out, transfers-per-ns and friends to be able to auto-tune themselves based on knowledge of how the server is performing.
See other work currently ongoing: