共计 3904 个字符，预计需要花费 10 分钟才能阅读完成。
在咱们日常应用高可用集群时，都会应用到负载平衡工具对多个节点的负载进行转发。这里就不得不提到咱们罕用的一个负载平衡工具 Nginx，Nginx 官网提供的收费版本性能绝对简略，大部分状况下咱们都是用其进行负载平衡，对于利用的状态次要是依赖于其余的监控工具。如果对于小型的团队来说，部署专门的监控工具还须要资源，应用 Nginx 对利用进行探活监控能够节约这部分老本。
首先装置 Nginx
应用 yum 装置 nginx 我这里应用的是 1.16.1 版本
yum install nginx
装置实现后能够获取源码装置命令
nginx -V
装置 Nginx 探活插件
下载源码与探活插件
wget https://nginx.org/download/ng…
wget https://github.com/yaoweibin/…
Nginx 应用源码编译装置相干的依赖包
yum install pcre pcre-devel openssl openssl-devel gd gd-devel zlib patch libxml2-devel libxslt-devel perl-devel perl-ExtUtils-Embed perl zlib-devel patch
解压源码和插件包，我这里将两个软件包全副放到 /opt 上面进行解压
tar zxvf nginx-1.16.1.tar.gz
unzip nginx_upstream_check_module.zip
patch 探活插件到 Nginx 源码中
cd /opt/nginx-1.16.1
patch -p1 < /opt/nginx_upstream_check_module-master/check_1.16.1+.patch
执行源码编译装置，增加 http 探活插件
./configure \
–prefix=/usr/share/nginx \
–sbin-path=/usr/sbin/nginx \
–modules-path=/usr/lib64/nginx/modules \
–conf-path=/etc/nginx/nginx.conf \
–error-log-path=/var/log/nginx/error.log \
–http-log-path=/var/log/nginx/access.log \
–http-client-body-temp-path=/var/lib/nginx/tmp/client_body \
–http-proxy-temp-path=/var/lib/nginx/tmp/proxy \
–http-fastcgi-temp-path=/var/lib/nginx/tmp/fastcgi \
–http-uwsgi-temp-path=/var/lib/nginx/tmp/uwsgi \
–http-scgi-temp-path=/var/lib/nginx/tmp/scgi \
–pid-path=/run/nginx.pid \
–lock-path=/run/lock/subsys/nginx \
–user=nginx \
–group=nginx \
–with-file-aio \
–with-ipv6 \
–with-http_ssl_module \
–with-http_v2_module \
–with-http_realip_module \
–with-stream_ssl_preread_module \
–with-http_addition_module \
–with-http_xslt_module=dynamic \
–with-http_image_filter_module=dynamic \
–with-http_sub_module \
–with-http_dav_module \
–with-http_flv_module \
–with-http_mp4_module \
–with-http_gunzip_module \
–with-http_gzip_static_module \
–with-http_random_index_module \
–with-http_secure_link_module \
–with-http_degradation_module \
–with-http_slice_module \
–with-http_stub_status_module \
–with-http_perl_module=dynamic \
–with-http_auth_request_module \
–with-mail=dynamic \
–with-mail_ssl_module \
–with-pcre \
–with-pcre-jit \
–with-stream=dynamic \
–with-stream_ssl_module \
–with-debug \
–with-cc-opt=’-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong –param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic’ \
–with-ld-opt=’-Wl,-z,relro -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -Wl,-E’ \
–add-module=/opt/nginx_upstream_check_module-master/
应用 Nginx 负载 Artifactory
Nginx 能够作为 Artifactory 制品库的负载均衡器，用来负载 Artifactory 多个节点间的申请，Artifactory 也能够主动生成 Nginx 配置文件，具体操作参考下图
配置探活
生成配置文件后，应用探活插件的配置办法，在 Nginx 的 config 文件中进行配置。具体样例如下：
upstream artifactory {
server 192.168.1.2:8082;
server 192.168.1.3:8082;
check interval=2000 rise=2 fall=2 timeout=1000 type=http;
check_http_send "HEAD / HTTP/1.0\r\n\r\n";
check_http_expect_alive http_2xx http_3xx}
upstream artifactory-direct {
server 192.168.1.2:8081;
server 192.168.1.3:8081;
check interval=2000 rise=2 fall=2 timeout=1000 type=http;
check_http_send "HEAD / HTTP/1.0\r\n\r\n";
check_http_expect_alive http_2xx http_3xx}
server {
listen 80 ;
server_name artifactory.external.io;
if ($http_x_forwarded_proto = '') {set $http_x_forwarded_proto $scheme;}
## Application specific logs
## access_log /var/log/nginx/artifactory.external.io -access.log timing;
## error_log /var/log/nginx/artifactory.external.io -error.log;
rewrite ^/$ /ui/ redirect;
rewrite ^/ui$ /ui/ redirect;
chunked_transfer_encoding on;
client_max_body_size 0;
location / {
proxy_read_timeout 2400s;
proxy_pass_header Server;
proxy_cookie_path ~*^/.* /;
proxy_buffer_size 128k;
proxy_buffers 40 128k;
proxy_busy_buffers_size 128k;
proxy_pass http://artifactory;
proxy_set_header X-JFrog-Override-Base-Url $http_x_forwarded_proto://$host:$server_port;
proxy_set_header X-Forwarded-Port $server_port;
proxy_set_header X-Forwarded-Proto $http_x_forwarded_proto;
proxy_set_header Host $http_host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
location ~ ^/artifactory/ {proxy_pass http://artifactory-direct;}
}
location /status {
check_status;
access_log off;
}}
探活配置胜利之后拜访，预置的 location 能够看到以后负载利用节点的衰弱状态
并且还反对 json 格局查看，不便咱们进行数据采集
