Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dnsdist: minimum number of successful checks for a backend to come up #7237

rgacogne opened this issue Nov 28, 2018 · 0 comments


None yet
1 participant
Copy link

commented Nov 28, 2018

  • Program: dnsdist
  • Issue type: Feature request

Short description

While it's possible require more than one failed check before a backend is marked as down using the maxCheckFailures option, there is currently no way of waiting for more than one successful check for a backend to get marked up again.


In some setups it might make sense to wait until 2 or 3 checks have succeeded before starting to use a backend, because we care about stability more than we want the backend to get back up fast.


Add a new optional rise parameter to newServer(), specifying how many health checks must be successful before the backend is marked as up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.