OTD Health Checks Not Working Correctly When Custom Request-URI is Specified
(Doc ID 2423871.1)
Last updated on MARCH 23, 2020
Applies to:Oracle Traffic Director - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
When an Oracle Traffic Director instance starts, it performs an initial health check for all the origin servers in all of the configured origin-server pools.
If the initial health check indicates that an origin server is healthy, Oracle Traffic Director sends further health-check requests to an origin server only in the following situations:
-The server has not served any request successfully for the entire duration of the previous health-check interval.
-Dynamic discovery is enabled for this origin server pool.
If a health check-either initial or subsequent-indicates that an origin server is not available, Oracle Traffic Director repeats the health check at the specified health-check interval.
This works fine when the default health checking mechanism is used. However, when a custom request URI (a GET request ) is specified or if an external command is configured for health check, the health checking is not working correctly. See below testing scenarios:
Is it possible for a feature or change request to be added to OTD to always send health checks during every health check interval?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document