使用流量管理器进行客户端转换 [英] client changeover using traffic Manager

问题描述

这可能不是正确的论坛，如果真是这样，我们深表歉意.

This may not be the correct forum for this, so apologies if this is so.

我们在南部和西部两个地区都有网络应用程序，并设置了流量管理器以提供弹性.我们正在使用流量管理器作为手动转换.

We have web apps in two regions south and west, there is a traffic manager set up to provide resilience.  We are using the traffic manager as a manual change over.

该网站的ARRAfinity已关闭，我们没有任何会话在运行.应用程序在启动时连接到正确区域的chrome浏览器中运行，并正常运行(这种情况是我们指向流量的区域 经理)  该应用程序创建对主机服务器的ajax调用.

The web sites have ARRAfinity tuned off and we do not have any sessions running.  The application running in a chrome browser connected to the correct region at startup, and runs correctly (this is the case what ever region we are pointing the traffic manager to)   The application creates ajax calls to the host server.

当应用程序启动并运行时，并且我们更改了流量管理器，则该应用程序将永远不会更改.如果我们检查nslookup，则客户端计算机的DNS已正确更改.我们能够更改客户的唯一方法是 关闭完整的浏览器(不仅仅是运行我们网站的标签)，然后重新启动.

When the application is up and running, and we change the traffic manager the application never changes.  If we check nslookup the DNS of the client machine has changed correctly.  The only way that we have been able to change the client is to close the complete browser (not just the tab our site is running in) and then start again.

无论我们运行的浏览器是什么，

This is the same whatever browser we are running.

任何帮助以及如何诊断都是很好的方法.这必须是一种常见用法，这是我们正在做的事情.

Any help and how to diagnose this would be great.  This must be a common usage, so it is something that we are doing.

谢谢

richie

richie

推荐答案

如您所知，Traffic Manager在DNS级别工作. DNS协议包括广泛的缓存-在递归DNS服务器和客户端中.在许多情况下，客户端中有两层缓存，一层是DNS服务，另一层是浏览器.

As you know, Traffic Manager works at the DNS level. The DNS protocol includes extensive caching - at the recursive DNS server, and in the client. In many cases, there are two layers of caching in the client--one in the DNS service, and another in the browser.

您可以在DNS记录上使用"TTL"来建议应将DNS缓存多长时间.不幸的是，这只是建议-客户可以选择忽略TTL并缓存更长的时间.您可以尝试减少流量管理器配置文件上的TTL，但效果 不能保证.

You can use the 'TTL' on the DNS records to advise how long DNS should be cached for. Unfortunately, it's just advice--clients can choose to ignore the TTL and cache for longer. You can try reducing the TTL on the Traffic Manager profile, but the effect is not guaranteed.

无论客户端缓存如何，保证立即进行故障转移的唯一方法是不仅依赖于基于DNS的路由.您可以将Traffic Manager与Azure App Gateway(可以与Web Apps一起使用)结合使用以实现此目的.请参阅https://docs.microsoft.com/zh-cn/azure/traffic-manager/traffic-manager-load-balancing-azure 有关更多信息.

The only way to guarantee immediate failover, regardless of client caching, is to not rely only on DNS-based routing. You could combine Traffic Manager with Azure App Gateway (which can work with Web Apps) to achieve this. See https://docs.microsoft.com/en-us/azure/traffic-manager/traffic-manager-load-balancing-azure for more information.

此致

乔纳森(www.opsgility.com)

Jonathan (www.opsgility.com)

这篇关于使用流量管理器进行客户端转换的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！