使用我的.net MVC应用程序负载平衡服务器的问题 [英] Problem in Load balancing severs with my .net MVC application

问题描述

我的.net MVC应用程序的负载均衡服务器出现问题。



在我的应用程序中，我们生成XML / TXT文件并将其保存在服务器中，用户将从服务器下载XML / TXT文件。



问题是当用户生成XML / TXT文件并将其保存在服务器中时，用户在Server1中是平衡的，当用户下载XML / TXT文件并且他/她驻留在server2中时。因此，用户无法从server1获取最近生成的文件。



请为这个场景给我一些解决方案。



谢谢，

Mani

Hi,

I have a problem with Load balancing severs with my .net MVC application.

In My application we generates XML/TXT file and Save it in Server and user will download the XML/TXT file from server.

The problem is when the user generates XML/TXT file and save it in server, user is balanced in Server1 and when the user downloads the XML/TXT file and he/she resides in server2. So, user couldnt able to get the recently generated file from server1.

Please give me some solution for this scenario.

Thanks,
Mani

推荐答案

你在NLB中使用什么类型的亲和力？



如果您的服务器亲和力对于您的流程来说非常重要我建议使用网络亲和力选项。



我们有后台用户负载均衡代理服务器。这意味着后续请求可以来自不同的公共IP地址。 Normaly这些IP地址只会在第4个八位字节变化，例如



1.1.1.x



用户移动数据连接也会受到快速变化的公共IP地址的影响。



这就是网络亲和力管理的内容。请求IP地址在前3个八位字节匹配的任何请求将始终路由到同一服务器。

What type of affinity are you using in your NLB?

If your server affinity is important for your processes to work I'd suggest using the Network affinity option.

We have users behind load balanced proxy servers. This means subsequent requests can come from different public IP addresses. Normaly these IP addresses will only vary on the 4th octet e.g.

1.1.1.x

Users on mobile data connections can also suffer with rapidly changing public IP addresses.

That's what network affinity manages. Any requests where the requesting IP address matches on the 1st 3 octets will always be routed to the same server.

这篇关于使用我的.net MVC应用程序负载平衡服务器的问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！