大网数据广告活动
服务器运维问答

High availability of load balancers themselves

· 52CE 我爱测

In all the articles that I have read in the internet about high availability of load balancer itself, an approach using virtual IP (VIP) is mentioned. In this approach, two load balancers will remain in active-standby mode. The a…

问题原文

原帖链接 · Saptarshi · CC BY-SA 3.0

In all the articles that I have read in the internet about high availability of load balancer itself, an approach using virtual IP (VIP) is mentioned. In this approach, two load balancers will remain in active-standby mode. The active load balancer owns the VIP. If the active load balancer goes down, the stand-by load balancer detects the failure using some heart beat mechanism and takes over the VIP and thus it becomes the active load balancer.

My questions are:

  1. At any point of time, only one load balancer is serving all the requests. What if the number of incoming requests are too high? Or is the number of requests handled by any popular load balancer like (HAProxy, nginx or any hardware load balancer) are too high to exceed in real life?

  2. Is it a good alternative to have a cluster of load balancers with the same domain name such that the DNS can do a round robin load balancing while distributing traffic to the load balancers themselves? This way we can achieve auto scaling of load balancers also by dynamically adding or removing A records in the DNS server/s.

已采纳解答

原帖链接 · Tim · CC BY-SA 3.0

  1. If the number requests is too high your will get timeouts. Yes you can max out a server, if you have a small server, or there are resource constraints.

  2. Yes. Though maybe not exactly like that.

DNS can have multiple A records for the same domain, which can either give you failover or load balancing. These servers can be in different data centers. One useful article is here, or you can search for "dns load balancing".

Amazon Web Services Route 53 can route based on a number of policies, such as geograpghic area or latency. It can also detect failures with servers and send traffic to other servers. It can work with non-AWS servers. It would be a good solution to your problem. The CloudFlare Traffic Manager, currently available in early access, could be another solution.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-11-01)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。