Hi Anand,
I see this could be a problem, is the backoff causing the delays for
failed zone transfers?
There is a configuration option "background-workers" with which you
can limit the number of parallel requests,
but if you can email me some statistics about failed/passed transfers
and transfers/second we can probably work out
some more clever queuing.
Cheers,
Marek
On 4 June 2014 12:11, Marek Vavruša <marek(a)vavrusa.com> wrote:
Hi Anand,
I see this could be a problem, is the backoff causing the delays for
failed zone transfers?
There is a configuration option "background-workers" with which you
can limit the number of parallel requests,
but if you can email me some statistics about failed/passed transfers
and transfers/second we can probably work out
some more clever queuing.
Cheers,
Marek
On 4 June 2014 12:06, Anand Buddhdev <anandb(a)ripe.net> wrote:
> On 03/06/2014 20:10, Marek Vavruša wrote:
>
>> Hi Everyone,
>>
>> with the 1.5.0 mostly feature-complete, us jolly folks at the CZ.NIC Labs
>> thought
>> that the time has come to share it with you in form of a first release
>> candidate.
>
> Great stuff Marek!
>
> I've started an instance of 1.5.0-rc1 with a few thousand slave zones
> configured. The bootstrap takes quite a while as Knot has to XFR all the
> zones in.
>
> It looks like Knot is hitting our master very hard, because it seems to
> want to make too many parallel connections. I see this in the logs:
>
> 2014-06-04T09:58:51 [error] AXFR of 'zone' with 'master': Requested
> resource is busy.
>
> Each such error will cause Knot to retry the zone later, and waste time
> and cycles. Is there any way to get Knot to limit the number of parallel
> XFRs it does? Or re-use TCP connections?
>
> The Knot server has been running for over 15 minutes now, and has still
> not finished boot-strapping all the zones.
>
> Regards,
>
> Anand
> _______________________________________________
> knot-dns-users mailing list
> knot-dns-users(a)lists.nic.cz
>
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users