Does HealthMonitor take care of adding the target server back to rotation once it is up

[#1]

We have HealthMonitor configured to check the health of target servers. We noticed that the target is taken out of rotation if target is down.

Would the HealthMonitor also take care of adding the target server back to rotation once it is up? Or should we do anything manually to add it back to rotation.

Note: We are currently in 4.16.01.07 version

[#2 · Accepted solution]

Hi @Rajashree

With max failures set and HealthMonitor (either HTTP or TCP), a server will be put back to rotation in both the below cases and no proxy re-deployments are required.

#1 If the response of the HTTP monitor call matches with the configured settings in the SuccessResponse block.
#2 When the connection succeeds if you have TCP monitor configured.

cc @Floyd Jones Looks like the documentation here http://docs.apigee.com/api-services/content/load-balancing-across-backend-servers doesn't state that point clearly, can we update it?

[jonesfloyd]

Thanks, @Maruti Chand. We'll update the docs (DOC-2061).

[sgilson]

@Maruti Chand

I updated the doc with this information. You can see it here:

http://docs.apigee.com/api-services/content/load-balancing-across-backend-servers#healthmonitoring

Thanks,

Stephen

[#5]

Hi Maruti,

Health monitor is not making server back into rotation.

If you get 30 events of “Max failure count(5) reached for server : ” proxy takes that server out of rotation although it’s in enabled /disabled status and even after server comes up it's not taking back into rotation even server is in enabled status.

You need to disable and enable this server in UI for resolving this issue if the servers is up and running in back end.

Is there any configuration file which is defining this limitation of 30 events of max failures (5) - 5 is the max failures defined

-Venkat