We desire the ability for web servers to have their health checked regularly to see if they can process authentication attempts. If not, the web server should be disabled in a way in which clients (Windows) using SRV records to find the web server would not use the web server, but move on to the next SRV record.
We don't want this health check at the client itself due to latency concerns.
by: Dennis R. | over a year ago | Other
Comments
Seems that every 30 seconds the web servers reach out to the database masters and do a connection check. If the web server cannot connect, then it won’t send authentication transactions there. An idea would be to improve on that existing health check and to add a transaction-based check. If one or the other fails, the web server will not bother sending any traffic there.