Recovery conditions and actions

After the failed server is marked down, new requests are sent to the second server. No new ICAP requests are sent to the failed server until that server is detected to be active again, based on the recovery conditions below.

Content Gateway tests for the following recovery conditions for each down ICAP server at a specified interval:

• TCP connection success
• Successfully sent OPTIONS request
• Successfully received valid response to OPTIONS request

Upon server recovery (server comes back online and is marked as up):

• Load balancing ON: Requests start being distributed to the newly up server (round-robin)
• Load balancing OFF: If the primary server recovers, all requests start being sent to the primary. If the secondary server recovers, traffic continues to be sent to the primary, until the primary goes down.