Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Auth: Incremental backoff for failed slave checks #4953
Both for soa-retry-default and slave-cycle-interval appear 'related' settings for this... We could limit the time between checks to the minimum of
Feb 21, 2017
1 check passed
Thanks for this great feature. Just a comment from our experience with failing masters: a zone which was removed form the master but not from the slave causes plenty of logging every slave-check cycle, but rarely caused problem on the slave. But what really causes massive problems is a non-responsive master. Because then the queries have to timeout which massively slow downs the slave. We have customers with >200.000 domains. If their master is not available we have to manually remove these customer from the slave checks to avoid performance issues on our slave. Hence, it would be great if you could also implement a similar feature but not per "domain", but per "master IP". So, skipping SOA checks for some time for certain master IP addresses if the a certain amount of queries failed in a certain time.