dnsdist: minimum number of successful checks for a backend to come up #7237
Description
- 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.
Usecase
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.
Description
Add a new optional rise parameter to newServer(), specifying how many health checks must be successful before the backend is marked as up.