In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-02-25 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >
Share
Shulou(Shulou.com)05/31 Report--
How to use AWS Route53 to achieve GSLB, many novices are not very clear about this, in order to help you solve this problem, the following editor will explain in detail for you, people with this need can come to learn, I hope you can gain something.
Recently, I have been studying other load balancing methods that are remote and do not use the cloud network load balancer Elastic Loadbalancer.
From the perspective of AWS, this method of load balancing in multiple regions is called global load balancing GSBL (Global Server Load Balancing), which implements traffic allocation among servers in different regions on the wide area network (including the Internet) to ensure the use of the best servers to serve the nearest customers, thus ensuring access quality.
Of course, GSBL has enterprise-level solutions and solutions that can be done on its own.
Here, I will briefly say that if you implement all load balancing GSBL in AWS.
Route53 in AWS is a multi-functional cloud DNS (domain name server). As long as you write a domain name on it, it will generate four superior domain names (NS) and transfer the domain name to the supplier when you write to purchase the domain name. For example, GoDaddy / who.is / DNSpod. An example is shown in the following figure:
You will find that these NS are located in different parts of the world, which can make your domain name analysis faster.
Route53 has a record of five domain names.
A brief description:
1. Simple-just normal, no different from other DNS.
2. Weighted is an IP that can not be assigned to a request according to weight, for example, you have 2 ip. The first ipweight = 5, the second ipweight = 10. The number of requests for the first ip is 5 percent 10 / 5 = 1 ip 3.
3. Latency is to send the request to the service center (region) with the fastest response. This can choose the mainland AWS!
4. Failover just do it with the load balancer. There is a healthchecker looking at your server. If the server dies, the request will not be sent.
5. Geolocation is to assign the request to the nearest server according to the outgoing address of the request.
I think the biggest difference between AWSroute53 and other DNS is
1. Route53 has healthchecker, and make corresponding actions according to healthchecker response.
2. Route53 supports Fail over
3. Everything in Route53 can be defined in API, which means it can be changed dynamically according to the program you write.
Health checker is a monitor tool customized for DNS.
There is http / https / TCP. AWS recommends that you update every 30 seconds. But you can choose 10 seconds. The problem here is that if you are less than 30, usually the server will be very busy, not recommended. If you choose 10 seconds, basically, every second will be given to PING.
Originally, the domain name will be changed only after 3 times of FAIL. But if it takes 30 * 3, a minute and a half, the failover is a little long. So I suggest that the failture threshold is 1Compact 2.
Because it is DNS failover, there is a technical problem natively: even the IP that has been DNS cache will not be changed even if failover. The solution is to rely on the failover function of the new browser to do this. There is nothing wrong with the failover I tested under Chrome. But ping / nslookup on the command line does have to wait a long time. So it would be reasonable to suggest that the failover of this DNS is now only used as a website.
As the topic of this article wants to show, how to implement global load balancing GSLB is very simple, based on Route53 Failover, plus multi-IP Record Set of Simple / Weighted. There is a small inconvenience here, that is, the record of weighted needs to be added one by one.
And CNAME is not supported for the time being, only IP. But if we want to use code to control a highly available environment, using system-generated domain names is a very popular practice. It is hoped that AWS can support Route53 Load balanced CNAME.
Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.