On 04/02/16 17:03, Anand Buddhdev wrote: Hi Jan,
> Next, I edited the config file, and added 4682 slave zones to it. They > all share the "default" template, which defines one master server. Then > I called "knotc reload". Knot logged all the zones, and said it was > going to bootstrap them. But then it just sat there, doing *something*, > and it was a full 118 seconds later, when it started to check the master > for updates. Here's the log snippet showing this: I have one more observation. The test server has been running for about 5 hours now. Of the 4682 zones configured, 2891 have still not been transferred in. I ran "knotc zone-refresh" and Knot appears to be trying to refresh zones. It appears to be doing some kind of batching. It does a bunch of zones, and then waits 5 seconds before doing another batch. The numer of untransferred zones is going down, albeit slowly. I think Knot 2's slave zone refresh strategy and timing need still more work, if it's to work effectively for a configuration with lots of slave zones. Regards, Anand _______________________________________________ knot-dns-users mailing list [email protected] https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users
