Finally, set up your recovery policy
Here, you add the Origin Failure Recovery Policy behavior to a rule in your property and configure the various failure scenarios that must be met to trigger a failover.
Where can you add this behavior?
This is entirely up to you—you can apply it in the Default Rule so it applies to all requests, or include it in a separate rule with unique match criteria to suit your needs. Remember that rules lower in the list take precedence over the Default Rule. They're acted on first, but the behaviors you've set in the Default Rule are still applied, because they apply to all requests.
Some caveats apply to where you can include this behavior:
- This behavior cannot be applied in the Origin Failure Recovery Methods rule. This rule does not support behaviors. It only supports its two sub-rules and their required behaviors. (You can't include this behavior in the sub-rules, either.)
- The Origin Failure Recovery Methods rule has to be the last rule in the list. This is to ensure its settings get properly applied. So, you can't include a rule after the Origin Failure Recovery Methods rule and include the Origin Failure Recovery Policy behavior in it.
Start by adding the Origin Failure Recovery Policy behavior
Start by adding this behavior to the appropriate rule—for this case, we're adding it to the Default Rule to have it apply to all requests.
- Ensure the Default Rule is active in your property.
- Click Add Behavior.
- In the Search available behaviors field, input "Origin Failure" to filter the listed rules. Select Origin Failure Recovery Policy from the list.
- Click the Enable Recovery Policy slider to set it to "On." Apply settings here, as necessary.
Next, define Tuning Parameters
These are optional settings you can apply to exclude ("blacklist") a problematic origin for an amount of time.
|Enable IP Avoidance||Set this slider to "On"
to blacklist IP addresses associated with an origin for a period of
time, after a certain number of failures occur. When an IP address
is blacklisted, requests will failover to another IP address
associated with the primary origin (if applicable). Once all IP
addresses associated with primary have been blacklisted, the
Recovery Method Configuration established for Origin Responsiveness
Monitoring (ORM) is applied.
Note: Enable IP Avoidance is intended for faster server-side failover. We strongly recommend that you enable this feature so it can be used in conjunction with the ORM failure scenario. Simply using ORM is not effective and you may not see the desired failover effect.
Note: Enable IP Avoidance may not be supported if you're using Media Services Live as your origin. See Known Issues with AMD failover for more information.
|IP Avoidance Error Threshold||This is the number of failures that must occur before an origin's IP address is blacklisted.|
|IP Avoidance Retry Interval (seconds)||This is the amount of time that must elapse before a failed origin IP address is removed from the blacklist.|
|Binary Equivalent Content||Enable this to support and apply internal performance optimizations for binary equivalent content (BEC). To use BEC, your content must be identical, byte-for-byte between the primary and backup origin (as discussed in Before you begin).|
Then, configure the "failure scenarios"
A failure scenario is a selection of settings you define to determine when to trigger a retry or recovery method you've set in the Origin Failure Recovery Methods rule. Multiple failure scenarios are offered, and you can configure one or all of them for use in your policy.