cjunior_138458
Dec 16, 2014Altostratus
Health monitor and shared backend server/services
Hello, Since the boxes active / standby, makes the monitoring of servers, so we have two sources to the same destination monitored. If a monitor is making calls by default every 5 seconds, or 12 per minute or 720 per hour. We will have a total of 1440 requests in an hour to the same destination, right? It gets bad when a server or service divided by more than one pool (1440 * N).
We can consider a problem if a server is weaker than the other? Because it will receive connections from clients and the BigIP (currently, the monitor HTTP / 1.1 closes the connections). If I increase the time monitoring, for example, the service may be unavailable for someone who will fall on a server that is supposed to fail in the period being not monitored, have some effect by using "reselect" parameter in "action on service down" for this case? To decrease by less the network traffic, I used the HEAD verb, and I captured the HTTP response, that's good? someone do that?
What do you usually do to calibrate a health monitor to http to be highly available but fewer requests in monitoring to preserve the backend servers? This is really something I should worry about? You can share your experiences? Thank you so much!