Skip to content

Commit ab73117

Browse files
authored
Merge pull request #121213 from AzureMentor/patch-56
Enhance instructions for setting up health checks and failover configuration
2 parents 6172c3e + 3fd1f45 commit ab73117

File tree

1 file changed

+14
-3
lines changed

1 file changed

+14
-3
lines changed

articles/reliability/reliability-traffic-manager.md

Lines changed: 14 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -138,10 +138,21 @@ This scenario is ideal for the use of Azure Traffic Manager that has inbuilt pro
138138

139139
1. Set up health check and failover configuration
140140

141-
In this step, you set the DNS TTL to 10 seconds, which is honored by most internet-facing recursive resolvers. This configuration means that no DNS resolver will cache the information for more than 10 seconds. For the endpoint monitor settings, the path is current set at / or root, but you can customize the endpoint settings to evaluate a path, for example, prod.contoso.com/index. The example below shows the **https** as the probing protocol. However, you can choose **http** or **tcp** as well. The choice of protocol depends upon the end application. The probing interval is set to 10 seconds, which enables fast probing, and the retry is set to 3. As a result, Traffic Manager will fail over to the second endpoint if three consecutive intervals register a failure. The following formula defines the total time for an automated failover:
142-
Time for failover = TTL + Retry * Probing interval
141+
In this step, you set the DNS TTL to 10 seconds, which is honored by most internet-facing recursive resolvers. This configuration means that no DNS resolver will cache the information for more than 10 seconds.
142+
143+
For the endpoint monitor settings, the path is current set at / or root, but you can customize the endpoint settings to evaluate a path, for example, prod.contoso.com/index.
144+
145+
The example below shows the **https** as the probing protocol. However, you can choose **http** or **tcp** as well. The choice of protocol depends upon the end application. The probing interval is set to 10 seconds, which enables fast probing, and the retry is set to 3. As a result, Traffic Manager will fail over to the second endpoint if three consecutive intervals register a failure.
146+
147+
The following formula defines the total time for an automated failover:
148+
149+
`Time for failover = TTL + Retry * Probing interval`
150+
143151
And in this case, the value is 10 + 3 * 10 = 40 seconds (Max).
144-
If the Retry is set to 1 and TTL is set to 10 secs, then the time for failover 10 + 1 * 10 = 20 seconds. Set the Retry to a value greater than **1** to eliminate chances of failovers due to false positives or any minor network blips.
152+
153+
If the Retry is set to 1 and TTL is set to 10 secs, then the time for failover 10 + 1 * 10 = 20 seconds.
154+
155+
Set the Retry to a value greater than **1** to eliminate chances of failovers due to false positives or any minor network blips.
145156

146157

147158
![Screenshot of setting up health check.](../networking/media/disaster-recovery-dns-traffic-manager/set-up-health-check.png)

0 commit comments

Comments
 (0)