Optimising rndc reload times on a slave server with 50,000 zones
dennis.perisa at gmail.com
Sun Feb 27 02:56:40 UTC 2011
I'm looking for suggestions to substantially improve reload times on a slave
that is serving 50,000 zones (mostly customer zones).
'rndc reload' is being executed on the slave every 15 minutes. Due to the
large number of zones to trawl through, the reload process is causing
intermittent outages and/or significant delays to zone transfers.
Here are some ideas I have:
- use rndc reconfig instead
- separate zone files into separate dirs to improve O/S performance
(currently, all zone files are in a single dir)
Are these viable options? Any other thoughts/suggestions?
This is expected to be a short-term fix while we consider brute force
approach of throwing more cpu/mem/IO at this.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bind-users