mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-22 23:00:57 +08:00
TR
@wxy
This commit is contained in:
Xingyu Wang
parent
8887dc87c5
commit
395112e225
@ -1,249 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (wxy)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Load balance network traffic with HAProxy)
|
||||
[#]: via: (https://opensource.com/article/20/11/load-balancing-haproxy)
|
||||
[#]: author: (Jim O'Connell https://opensource.com/users/jimoconnell)
|
||||
|
||||
Load balance network traffic with HAProxy
|
||||
======
|
||||
Install, configure, and run HAProxy to distribute network traffic across
|
||||
several web or application servers.
|
||||
![eight stones balancing][1]
|
||||
|
||||
You don't have to work at a huge company to justify using a load balancer. You might be a hobbyist, self-hosting a website from a couple of Raspberry Pi computers. Perhaps you're the server administrator for a small business; maybe you _do_ work for a huge company. Whatever your situation, you can benefit from using the [HAProxy][2] load balancer to manage your traffic.
|
||||
|
||||
HAProxy is known as "the world's fastest and most widely used software load balancer." It packs in many features that can make your applications more secure and reliable, including built-in rate limiting, anomaly detection, connection queuing, health checks, and detailed logs and metrics. Learning the basic skills and concepts covered in this tutorial will help you use HAProxy to build a more robust, far more powerful infrastructure.
|
||||
|
||||
### Why would you need a load balancer?
|
||||
|
||||
A load balancer is a way to easily distribute connections across several web or application servers. In fact, HAProxy can balance any type of Transmission Control Protocol ([TCP][3]) traffic, including RDP, FTP, WebSockets, or database connections. The ability to distribute load means you don't need to purchase a massive web server with zillions of gigs of RAM just because your website gets more traffic than Google.
|
||||
|
||||
A load balancer also gives you flexibility. Perhaps your existing web server isn't robust enough to meet peak demand during busy times of the year and you'd like to add another, but only temporarily. Maybe you want to add some redundancy in case one server fails. With HAProxy, you can add more servers to the backend pool when you need them and remove them when you don't.
|
||||
|
||||
You can also route requests to different servers depending on the context. For example, you might want to handle your static content with a couple of cache servers, such as [Varnish][4], but route anything that requires dynamic content, such as an API endpoint, to a more powerful machine.
|
||||
|
||||
In this article, I will walk through setting up a very basic HAProxy installation to use HTTPS to listen on secure port 443 and utilize a couple of backend web servers. It will even send all traffic that comes to a predefined URL (like `/api/`) to a different server or pool of servers.
|
||||
|
||||
### Install HAProxy
|
||||
|
||||
To get started, spin up a new CentOS 8 server or instance and bring the system up to date:
|
||||
|
||||
|
||||
```
|
||||
`sudo yum update -y`
|
||||
```
|
||||
|
||||
This typically runs for a while. Grab yourself a coffee while you wait.
|
||||
|
||||
This installation has two parts: the first part installs the yum version of HAProxy, and the second part compiles and installs your binary from source to overwrite the previous HAProxy with the latest version. Installing with yum does a lot of the heavy lifting as far as generating systemd startup scripts, etc., so run the `yum install` and then overwrite the HAProxy binary with the latest version by compiling it from its source code:
|
||||
|
||||
|
||||
```
|
||||
`sudo yum install -y haproxy`
|
||||
```
|
||||
|
||||
Enable the HAProxy service:
|
||||
|
||||
|
||||
```
|
||||
`sudo systemctl enable haproxy`
|
||||
```
|
||||
|
||||
To upgrade to the latest version ([version 2.2][5], as of this writing), compile the source code. Many people assume that compiling and installing a program from its source code requires a high degree of technical ability, but it's a pretty straightforward process. Start by using `yum` to install a few packages that provide the tools for compiling code:
|
||||
|
||||
|
||||
```
|
||||
sudo yum install dnf-plugins-core
|
||||
sudo yum config-manager --set-enabled PowerTools
|
||||
# (Multiline command next 3 lines. Copy and paste together:)
|
||||
|
||||
sudo yum install -y git ca-certificates gcc glibc-devel \
|
||||
lua-devel pcre-devel openssl-devel systemd-devel \
|
||||
make curl zlib-devel
|
||||
```
|
||||
|
||||
Use `git` to get the latest source code and change to the `haproxy` directory:
|
||||
|
||||
|
||||
```
|
||||
git clone <http://git.haproxy.org/git/ haproxy>
|
||||
cd haproxy
|
||||
```
|
||||
|
||||
Run the following three commands to build and install HAProxy with integrated Prometheus support:
|
||||
|
||||
|
||||
```
|
||||
# Multiline command next 3 lines copy and paste together:
|
||||
make TARGET=linux-glibc USE_LUA=1 USE_OPENSSL=1 USE_PCRE=1 \
|
||||
PCREDIR= USE_ZLIB=1 USE_SYSTEMD=1 \ EXTRA_OBJS="contrib/
|
||||
|
||||
sudo make PREFIX=/usr install # Install to /usr/sbin/haproxy
|
||||
```
|
||||
|
||||
Test it by querying the version:
|
||||
|
||||
|
||||
```
|
||||
`haproxy -v`
|
||||
```
|
||||
|
||||
You should get the following output:
|
||||
|
||||
|
||||
```
|
||||
`HA-Proxy version 2.2.4-b16390-23 2020/10/09 - https://haproxy.org/`
|
||||
```
|
||||
|
||||
### Create the backend server
|
||||
|
||||
HAProxy doesn't serve any traffic directly—this is the job of backend servers, which are typically web or application servers. For this exercise, I'm using a tool called [Ncat][6], the "Swiss Army knife" of networking, to create some exceedingly simple servers. Install it:
|
||||
|
||||
|
||||
```
|
||||
`sudo yum install nc -y`
|
||||
```
|
||||
|
||||
If your system has [SELinux][7] enabled, you'll need to enable port 8404, the port used for accessing the HAProxy Stats page (explained below), and the ports for your backend servers:
|
||||
|
||||
|
||||
```
|
||||
sudo dnf install policycoreutils-python-utils
|
||||
sudo semanage port -a -t http_port_t -p tcp 8404
|
||||
sudo semanage port -a -t http_port_t -p tcp 10080;
|
||||
sudo semanage port -a -t http_port_t -p tcp 10081;
|
||||
sudo semanage port -a -t http_port_t -p tcp 10082;
|
||||
```
|
||||
|
||||
Create two Ncat web servers and an API server:
|
||||
|
||||
|
||||
```
|
||||
while true ;
|
||||
do
|
||||
nc -l -p 10080 -c 'echo -e "HTTP/1.1 200 OK\n\n This is Server ONE"' ;
|
||||
done &
|
||||
|
||||
while true ;
|
||||
do
|
||||
nc -l -p 10081 -c 'echo -e "HTTP/1.1 200 OK\n\n This is Server TWO"' ;
|
||||
done &
|
||||
|
||||
while true ;
|
||||
do
|
||||
nc -l -p 10082 -c 'echo -e "HTTP/1.1 200 OK\nContent-Type: application/json\n\n { \"Message\" :\"Hello, World!\" }"' ;
|
||||
done &
|
||||
```
|
||||
|
||||
These simple servers print out a message (such as "This is Server ONE") and run until the server is stopped. In a real-world setup, you would use actual web and app servers.
|
||||
|
||||
### Modify the HAProxy config file
|
||||
|
||||
HAProxy's configuration file is `/etc/haproxy/haproxy.cfg`. This is where you make the changes to define your load balancer. This [basic configuration][8] will get you started with a working server:
|
||||
|
||||
|
||||
```
|
||||
global
|
||||
log 127.0.0.1 local2
|
||||
user haproxy
|
||||
group haproxy
|
||||
|
||||
defaults
|
||||
mode http
|
||||
log global
|
||||
option httplog
|
||||
|
||||
frontend main
|
||||
bind *:80
|
||||
|
||||
default_backend web
|
||||
use_backend api if { path_beg -i /api/ }
|
||||
|
||||
#-------------------------
|
||||
# SSL termination - HAProxy handles the encryption.
|
||||
# To use it, put your PEM file in /etc/haproxy/certs
|
||||
# then edit and uncomment the bind line (75)
|
||||
#-------------------------
|
||||
# bind *:443 ssl crt /etc/haproxy/certs/haproxy.pem ssl-min-ver TLSv1.2
|
||||
# redirect scheme https if !{ ssl_fc }
|
||||
|
||||
#-----------------------------
|
||||
# Enable stats at <http://test.local:8404/stats>
|
||||
#-----------------------------
|
||||
|
||||
frontend stats
|
||||
bind *:8404
|
||||
stats enable
|
||||
stats uri /stats
|
||||
#-----------------------------
|
||||
# round robin balancing between the various backends
|
||||
#-----------------------------
|
||||
|
||||
backend web
|
||||
server web1 127.0.0.1:10080 check
|
||||
server web2 127.0.0.1:10081 check
|
||||
|
||||
#-----------------------------
|
||||
|
||||
# API backend for serving up API content
|
||||
#-----------------------------
|
||||
backend api
|
||||
server api1 127.0.0.1:10082 check
|
||||
```
|
||||
|
||||
### Restart and reload HAProxy
|
||||
|
||||
HAProxy is probably not running yet, so issue the command `sudo systemctl restart haproxy` to start (or restart) it. The `restart` method is fine for non-production situations, but once you are up and running, you'll want to get in the habit of using `sudo systemctl reload haproxy` to avoid service interruptions, even if you have an error in your config.
|
||||
|
||||
For example, after you make changes to `/etc/haproxy/haproxy.cfg`, you need to reload the daemon with `sudo systemctl reload haproxy` to effect the changes. If there is an error, it will let you know but continue running with the previous configuration. Check your HAProxy status with `sudo systemctl status haproxy`.
|
||||
|
||||
If it doesn't report any errors, you have a running server. Test it with curl on the server, by typing `curl http://localhost/` on the command line. If you see "_This is Server ONE_," then it all worked! Run `curl` a few times and watch it cycle through your backend pool, then see what happens when you type `curl http://localhost/api/`. Adding `/api/` to the end of the URL will send all of that traffic to the third server in your pool. At this point, you should have a functioning load balancer!
|
||||
|
||||
### Check your stats
|
||||
|
||||
You may have noted that the configuration defined a frontend called `stats` that is listening on port 8404:
|
||||
|
||||
|
||||
```
|
||||
frontend stats
|
||||
bind *:8404
|
||||
stats uri /stats
|
||||
stats enable
|
||||
```
|
||||
|
||||
In your browser, load up `http://localhost:8404/stats`. Read HAProxy's blog "[Exploring the HAProxy Stats page][9]" to find out what you can do here.
|
||||
|
||||
### A powerful load balancer
|
||||
|
||||
Although I covered just a few of HAProxy's features, you now have a server that listens on ports 80 and 443, redirecting HTTP traffic to HTTPS, balancing traffic between several backend servers, and even sending traffic matching a specific URL pattern to a different backend server. You also unlocked the very powerful HAProxy Stats page that gives you a great overview of your systems.
|
||||
|
||||
This exercise might seem simple, make no mistake about it—you have just built and configured a very powerful load balancer capable of handling a significant amount of traffic.
|
||||
|
||||
For your convenience, I put all the commands in this article in a [GitHub Gist][10].
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/20/11/load-balancing-haproxy
|
||||
|
||||
作者：[Jim O'Connell][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/jimoconnell
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/water-stone-balance-eight-8.png?itok=1aht_V5V (eight stones balancing)
|
||||
[2]: https://www.haproxy.org/
|
||||
[3]: https://en.wikipedia.org/wiki/Transmission_Control_Protocol
|
||||
[4]: https://varnish-cache.org/
|
||||
[5]: https://www.haproxy.com/blog/announcing-haproxy-2-2/
|
||||
[6]: https://nmap.org/ncat
|
||||
[7]: https://www.redhat.com/en/topics/linux/what-is-selinux
|
||||
[8]: https://gist.github.com/haproxytechblog/38ef4b7d42f16cfe5c30f28ee3304dce
|
||||
[9]: https://www.haproxy.com/blog/exploring-the-haproxy-stats-page/
|
||||
[10]: https://gist.github.com/haproxytechblog/d656422754f1b5eb1f7bbeb1452d261e
|
||||
@ -0,0 +1,235 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (wxy)
|
||||
[#]: reviewer: (wxy)
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Load balance network traffic with HAProxy)
|
||||
[#]: via: (https://opensource.com/article/20/11/load-balancing-haproxy)
|
||||
[#]: author: (Jim O'Connell https://opensource.com/users/jimoconnell)
|
||||
|
||||
用 HAProxy 实现网络流量的负载平衡
|
||||
======
|
||||
|
||||
> 安装、配置和运行 HAProxy，在几个网络或应用服务器之间分配网络流量。
|
||||
|
||||
|
||||
|
||||
不是只有在一个大型公司工作才需要使用负载平衡器。你可能是一个业余爱好者，用几台树莓派电脑自我托管一个网站。也许你是一个小企业的服务器管理员；也许你确实在一家大公司工作。无论你的情况如何，你都可以使用 [HAProxy][2] 负载平衡器来管理你的流量。
|
||||
|
||||
HAProxy 被称为“世界上最快和使用最广泛的软件负载平衡器”。它包含了许多可以使你的应用程序更加安全可靠的功能，包括内置的速率限制、异常检测、连接排队、健康检查以及详细的日志和指标。学习本教程中所涉及的基本技能和概念，将有助于你使用 HAProxy 建立一个更强大的、远为强大的基础设施。
|
||||
|
||||
### 为什么需要一个负载平衡器？
|
||||
|
||||
负载平衡器是一种在几个网络或应用服务器之间轻松分配连接的方法。事实上，HAProxy 可以平衡任何类型的传输控制协议（[TCP][3]）流量，包括 RDP、FTP、WebSockets 或数据库连接。分散负载的能力意味着你不需要因为你的网站流量比谷歌大就购买一个拥有几十万 G 内存的大型网络服务器。
|
||||
|
||||
负载平衡器还为你提供了灵活性。也许你现有的网络服务器不够强大，无法满足一年中繁忙时期的峰值需求，你想增加一个，但只是暂时的。也许你想增加一些冗余，以防一个服务器出现故障。有了 HAProxy，你可以在需要时向后端池添加更多的服务器，在不需要时删除它们。
|
||||
|
||||
你还可以根据情况将请求路由到不同的服务器。例如，你可能想用几个缓存服务器（如 [Varnish][4]）来处理你的静态内容，但把任何需要动态内容的东西，如 API 端点，路由到一个更强大的机器。
|
||||
|
||||
在这篇文章中，我将通过设置一个非常基本的 HAProxy 环境，使用 HTTPS 来监听安全端口 443，并利用几个后端 Web 服务器。它甚至会将所有进入预定义 URL（如 `/api/`）的流量发送到不同的服务器或服务器池。
|
||||
|
||||
### 安装 HAProxy
|
||||
|
||||
要开始安装，请启动一个新的 CentOS 8 服务器或实例，并使系统达到最新状态：
|
||||
|
||||
```
|
||||
$ sudo yum update -y
|
||||
```
|
||||
|
||||
这通常会持续一段时间。在等待的时候给自己拿杯咖啡。
|
||||
|
||||
这个安装有两部分：第一部分是安装 yum 版本的 HAProxy，第二部分是编译和安装你的二进制文件，用最新的版本覆盖以前的 HAProxy。用 yum 安装，在生成 systemd 启动脚本等方面做了很多繁重的工作，所以运行 `yum install`，然后从源代码编译，用最新的版本覆盖 HAProxy 二进制：
|
||||
|
||||
```
|
||||
$ sudo yum install -y haproxy
|
||||
```
|
||||
|
||||
启用 HAProxy 服务：
|
||||
|
||||
```
|
||||
$ sudo systemctl enable haproxy
|
||||
```
|
||||
|
||||
要升级到最新版本（[版本 2.2][5]，截至本文写作为止），请编译源代码。许多人认为从源代码编译和安装一个程序需要很高的技术能力，但这是一个相当简单的过程。首先，使用 `yum` 安装一些提供编译代码工具的软件包：
|
||||
|
||||
```
|
||||
$ sudo yum install dnf-plugins-core
|
||||
$ sudo yum config-manager --set-enabled PowerTools
|
||||
$ sudo yum install -y git ca-certificates gcc glibc-devel \
|
||||
lua-devel pcre-devel openssl-devel systemd-devel \
|
||||
make curl zlib-devel
|
||||
```
|
||||
|
||||
使用 `git` 获得最新的源代码，并改变到 `haproxy` 目录：
|
||||
|
||||
```
|
||||
$ git clone http://git.haproxy.org/git/ haproxy
|
||||
$ cd haproxy
|
||||
```
|
||||
|
||||
运行以下三个命令来构建和安装具有集成了 Prometheus 支持的 HAProxy：
|
||||
|
||||
```
|
||||
$ make TARGET=linux-glibc USE_LUA=1 USE_OPENSSL=1 USE_PCRE=1 \
|
||||
PCREDIR= USE_ZLIB=1 USE_SYSTEMD=1 \
|
||||
EXTRA_OBJS="contrib/prometheus-exporter/service-prometheus.o"
|
||||
|
||||
$ sudo make PREFIX=/usr install # 安装到 /usr/sbin/haproxy
|
||||
```
|
||||
|
||||
通过查询版本来测试它：
|
||||
|
||||
```
|
||||
$ haproxy -v
|
||||
```
|
||||
|
||||
你应该看到以下输出：
|
||||
|
||||
```
|
||||
HA-Proxy version 2.2.4-b16390-23 2020/10/09 - https://haproxy.org/
|
||||
```
|
||||
|
||||
### 创建后端服务器
|
||||
|
||||
HAProxy 并不直接提供任何流量，这是后端服务器的工作，它们通常是网络或应用服务器。在这个练习中，我使用一个叫做 [Ncat][6] 的工具，它是网络领域的“瑞士军刀”，用来创建一些极其简单的服务器。安装它：
|
||||
|
||||
```
|
||||
$ sudo yum install nc -y
|
||||
```
|
||||
|
||||
如果你的系统启用了 [SELinux][7]，你需要启用端口 8404，这是用于访问 HAProxy 统计页面的端口（下面有解释），以及你的后端服务器的端口：
|
||||
|
||||
```
|
||||
$ sudo dnf install policycoreutils-python-utils
|
||||
$ sudo semanage port -a -t http_port_t -p tcp 8404
|
||||
$ sudo semanage port -a -t http_port_t -p tcp 10080
|
||||
$ sudo semanage port -a -t http_port_t -p tcp 10081
|
||||
$ sudo semanage port -a -t http_port_t -p tcp 10082
|
||||
```
|
||||
|
||||
创建两个 Ncat 网络服务器和一个 API 服务器：
|
||||
|
||||
```
|
||||
$ while true ;
|
||||
do
|
||||
nc -l -p 10080 -c 'echo -e "HTTP/1.1 200 OK\n\n This is Server ONE"' ;
|
||||
done &
|
||||
|
||||
$ while true ;
|
||||
do
|
||||
nc -l -p 10081 -c 'echo -e "HTTP/1.1 200 OK\n\n This is Server TWO"' ;
|
||||
done &
|
||||
|
||||
$ while true ;
|
||||
do
|
||||
nc -l -p 10082 -c 'echo -e "HTTP/1.1 200 OK\nContent-Type: application/json\n\n { \"Message\" :\"Hello, World!\" }"' ;
|
||||
done &
|
||||
```
|
||||
|
||||
这些简单的服务器打印出一条信息（如“This is Server ONE”），并运行到服务器停止为止。在现实环境中，你会使用实际的网络和应用程序服务器。
|
||||
|
||||
### 修改 HAProxy 的配置文件
|
||||
|
||||
HAProxy 的配置文件是 `/etc/haproxy/haproxy.cfg`。你在这里进行修改以定义你的负载平衡器。这个 [基本配置][8] 将让你从一个工作的服务器开始：
|
||||
|
||||
```
|
||||
global
|
||||
log 127.0.0.1 local2
|
||||
user haproxy
|
||||
group haproxy
|
||||
|
||||
defaults
|
||||
mode http
|
||||
log global
|
||||
option httplog
|
||||
|
||||
frontend main
|
||||
bind *:80
|
||||
|
||||
default_backend web
|
||||
use_backend api if { path_beg -i /api/ }
|
||||
|
||||
#-------------------------
|
||||
# SSL termination - HAProxy handles the encryption.
|
||||
# To use it, put your PEM file in /etc/haproxy/certs
|
||||
# then edit and uncomment the bind line (75)
|
||||
#-------------------------
|
||||
# bind *:443 ssl crt /etc/haproxy/certs/haproxy.pem ssl-min-ver TLSv1.2
|
||||
# redirect scheme https if !{ ssl_fc }
|
||||
|
||||
#-----------------------------
|
||||
# Enable stats at http://test.local:8404/stats
|
||||
#-----------------------------
|
||||
|
||||
frontend stats
|
||||
bind *:8404
|
||||
stats enable
|
||||
stats uri /stats
|
||||
#-----------------------------
|
||||
# round robin balancing between the various backends
|
||||
#-----------------------------
|
||||
|
||||
backend web
|
||||
server web1 127.0.0.1:10080 check
|
||||
server web2 127.0.0.1:10081 check
|
||||
|
||||
#-----------------------------
|
||||
|
||||
# API backend for serving up API content
|
||||
#-----------------------------
|
||||
backend api
|
||||
server api1 127.0.0.1:10082 check
|
||||
```
|
||||
|
||||
### 重启并重新加载 HAProxy
|
||||
|
||||
HAProxy 可能还没有运行，所以发出命令 `sudo systemctl restart haproxy` 来启动（或重新启动）它。“重启” 的方法在非生产情况下是很好的，但是一旦你开始运行，你要养成使用 `sudo systemctl reload haproxy` 的习惯，以避免服务中断，即使你的配置中出现了错误。
|
||||
|
||||
例如，当你对 `/etc/haproxy/haproxy.cfg` 进行修改后，你需要用 `sudo systemctl reload haproxy` 来重新加载守护进程，使修改生效。如果有错误，它会让你知道，但继续用以前的配置运行。用 `sudo systemctl status haproxy` 检查 HAProxy 的状态。
|
||||
|
||||
如果它没有报告任何错误，你就有一个正在运行的服务器。在服务器上用 `curl` 测试，在命令行输入 `curl http://localhost/`。如果你看到 “This is Server ONE”，那就说明一切都成功了！运行 `curl` 几次，看着它在你的后端池中循环，然后看看当你输入 `curl http://localhost/api/` 时会发生什么。在 URL 的末尾添加 `/api/` 将把所有的流量发送到你池子里的第三个服务器。至此，你就有了一个正常运作的负载平衡器
|
||||
|
||||
### 检查你的统计资料
|
||||
|
||||
你可能已经注意到，配置中定义了一个叫做 `stats` 的前端，它的监听端口是 8404：
|
||||
|
||||
```
|
||||
frontend stats
|
||||
bind *:8404
|
||||
stats uri /stats
|
||||
stats enable
|
||||
```
|
||||
|
||||
在你的浏览器中，加载 `http://localhost:8404/stats`。阅读 HAProxy 的博客 [学习 HAProxy 的统计页面][9]，了解你在这里可以做什么。
|
||||
|
||||
### 一个强大的负载平衡器
|
||||
|
||||
虽然我只介绍了 HAProxy 的几个功能，但你现在有了一个服务器，它可以监听 80 和 443 端口，将 HTTP 流量重定向到 HTTPS，在几个后端服务器之间平衡流量，甚至将匹配特定 URL 模式的流量发送到不同的后端服务器。你还解锁了非常强大的 HAProxy 统计页面，让你对你的系统有一个很好的概览。
|
||||
|
||||
这个练习可能看起来很简单，不要搞错了，你刚刚建立和配置了一个非常强大的负载均衡器，能够处理大量的流量。
|
||||
|
||||
为了你方便，我把本文中的所有命令放在了 [GitHub Gist][10] 中。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/20/11/load-balancing-haproxy
|
||||
|
||||
作者：[Jim O'Connell][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[wxy](https://github.com/wxy)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/jimoconnell
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/water-stone-balance-eight-8.png?itok=1aht_V5V (eight stones balancing)
|
||||
[2]: https://www.haproxy.org/
|
||||
[3]: https://en.wikipedia.org/wiki/Transmission_Control_Protocol
|
||||
[4]: https://varnish-cache.org/
|
||||
[5]: https://www.haproxy.com/blog/announcing-haproxy-2-2/
|
||||
[6]: https://nmap.org/ncat
|
||||
[7]: https://www.redhat.com/en/topics/linux/what-is-selinux
|
||||
[8]: https://gist.github.com/haproxytechblog/38ef4b7d42f16cfe5c30f28ee3304dce
|
||||
[9]: https://www.haproxy.com/blog/exploring-the-haproxy-stats-page/
|
||||
[10]: https://gist.github.com/haproxytechblog/d656422754f1b5eb1f7bbeb1452d261e
|
||||
Loading…
Reference in New Issue
Block a user