负载平衡 - 一次只有一个VM问题 [英] Load Balance - only one VM at a time problem

问题描述

这篇文章（下面的第一个链接）描述了我想要完成的问题，但它是从2015年开始的，我想知道今天的Azure是否有一种方法可以实现这一点，而无需在负载均衡器上进行自定义探测，希望通过实时迁移和可用性
设置？

This article (first link below) describes the issue that I want to accomplish, but it's from 2015, and I'm wondering if today's Azure has a means of achieving this without a custom probe on a load balancer, hopefully with Live Migration and Availability Sets?

正如本文所述，我有一个遗留应用程序在内存中使用实时数据库。 物理基础设施部署作为外部Windows服务，监视实时数据库，并手动将更新内存传输到"双胞胎"。
服务器。 当主要故障时，负载平衡转移到"双胞胎"。 我希望消除"双胞胎"以及管理内存的应用程序服务。

as this article states, I have a legacy application that uses a real-time DB in the memory.  The physical infrastructure deployment as an external windows service that monitors the Real-time DB, and manually transfers the updates to memory to a "twin" server.  When the primary fails, the load balance transfers to the "twin".  I'm hoping to eliminate the "twin" and the application service which manages the memory.

https://devblogs.microsoft.com/azuregov/implement-automatic-failover-with-load-balanced -Sets到确保高可用性-的-VM-工作负载合天青-其中仅酮-VM-罐响应到请求-AT-A-时间/

我也发现了这篇文章：  https://azure.microsoft.com/en-us/blog/improving-azure-virtual-machine-resiliency- with-predictive-ml-and-live-migration /

I found this article as well: https://azure.microsoft.com/en-us/blog/improving-azure-virtual-machine-resiliency-with-predictive-ml-and-live-migration/

我真正想要的是类似于SQL服务器的高级服务，其中有一个主服务器，三个副本。 如果主要失败，它将无缝地处理到其中一个辅助副本的过渡 - 包括使用实时迁移
来传输内存。    https://docs.microsoft.com/en-ca/azure/sql-database/sql-database-high-availability#premium-and-business-critical-service-tier可用性

What I really want, is something like the Premium Service of SQL server, where there is a primary server, with three replicas.  Should the primary fail, it seamlessly handles the transition to one of the secondary replicas - including using Live Migration to transfer memory.   https://docs.microsoft.com/en-ca/azure/sql-database/sql-database-high-availability#premium-and-business-critical-service-tier-availability

推荐答案

 

Hi, 

Azure负载均衡器，其行为方式与在后端资源上分配负载的方式相同。

Azure Load Balancer, behaves the same way as to distribute the loads across the backend resources. 

Azure负载均衡器会将流量路由到所有正常运行的实例，如果如果要实现将VM作为主要虚拟机的逻辑，则需要从资源级别进行操作。 

Azure Load balancer will route the traffic to all healthy instances, and if you want to implement your logic of making a VM as primary, you need to do it from the resource level. 

LB探测时，辅助虚拟机应始终使探测失败，以便LB将所有流量路由到主虚拟机。主虚拟机出现故障后，辅助虚拟机应开始响应探测，以便LB将故障转移到辅助虚拟机。

When LB probes, secondary VM should always fail the probe so that LB will route all the traffic to the Primary VM. Once the Primary VM goes down, Secondary VM should start responding to the probes, so that the LB will fail-over to the secondary VM. 

如果要使用任何第三方LB，就像F5一样，你可以轻松实现你的场景。

If you want to use any 3rd party LB, like F5, you can achieve your scenario easily.

如果你有任何问题，请告诉我。 

Let me know if you have any questions. 

问候， 

Msrini

这篇关于负载平衡 - 一次只有一个VM问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！