http://www.jackxiang.com/index.php zh-cn http://www.jackxiang.com/post// jack <xdy108@126.com> Thu, 22 Oct 2015 05:16:10 +0000 http://www.jackxiang.com/post// 一）nginx从前端域名支向代理并负载均衡代理到其他ip并配置了域名的机器，这儿得有proxy_set_header Host $host;相当于以域名访问IP:
    upstream backend_jackxiang {//均衡负载+备机         server   16.76.39.28:80 weight=1 max_fails=2 fail_timeout=5s;         server   16.76.39.29:80 weight=1 max_fails=2 fail_timeout=5s;         server   16.76.39.20:80 weight=1 max_fails=2 fail_timeout=5s;         server   16.76.39.21:80 weight=1 max_fails=2 fail_timeout=5s;         server   10.70.56.65:81 backup;         server   10.70.56.66:81 backup;         server   10.70.56.67:81 backup;         server   10.70.56.68:81 backup;     } {         listen       80;         server_name  jackxiang.jackxiang.com;         index index.html index.htm index.php;         location / {             proxy_set_header Host $host;             proxy_set_header X-Real-IP $remote_addr;             proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;             proxy_pass http://backend_jackxiang;             client_body_buffer_size  512k;             proxy_connect_timeout    30;             proxy_read_timeout       60;             proxy_send_timeout       30;             proxy_buffer_size        256k;             proxy_buffers            4 256k;             proxy_busy_buffers_size 256k;


经测试，这个Nginx的七层代理感觉还是比Lvs差一点，压力测试时这块儿还是有点卡：
upstream lua {     server 10.70.**.1** weight=1;     #server 10.70.**.134 weight=1;     #server 10.70.**.135 weight=1;     #server 10.70.**.136 weight=1;     #server 10.70.**.137 weight=1;     #server 10.70.**.138 weight=1;     #server 10.70.**.139 weight=1; } server {     listen 80 default_server;     server_name 10.7*.6*.102;     location / {         proxy_pass                 http://lua;         proxy_next_upstream        http_502 http_504 error timeout invalid_header;         proxy_connect_timeout      60;         proxy_read_timeout         3600;         proxy_send_timeout         3600;         proxy_temp_file_write_size 64k;         proxy_redirect             off;         #proxy_set_header           Host $host;         proxy_set_header           X-Forwarded-For $remote_addr;     }     access_log /data/logs/nginx/access.log main; }

二）如nginx暴露出域名反向代理到一台tomcat的以IP指向的8080端口：
    upstream backend_tomcat {//8080 一般是tomcat服务器，这儿没有暴露出域名而是直接物理机IP，以权重进行负载。（特别是有些业务要落全落一台的，这样配置才行，否则散开了会出现数据不完整：28，29，30，31各放sqllite数据库分别记录如果不权重分开在调用时会出现业务逻辑问题）         server   16.76.39.28:8080 weight=100 max_fails=2 fail_timeout=5s;         server   16.76.39.29:8080 weight=90 max_fails=2 fail_timeout=5s;         server   16.76.39.30:8080 weight=80 max_fails=2 fail_timeout=5s;         server   10.120.0.31:8080 weight=70 max_fails=2 fail_timeout=5s; }     server     {         listen       80;         server_name  upload.jackxiang.com;         index index.html;         # Max file size         client_max_body_size 1048m;         location / {             proxy_set_header Host $host;             proxy_set_header X-Real-IP $remote_addr;             proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;             proxy_pass http://backend_tomcat;         }         access_log /data/logs/pcupload.log;     }
——————————————————————————————————————————
upstream  testproxy  {         server   127.0.0.1:8080;         server   192.168.1.15:8080 backup; }

只要在希望成为后备的服务器ip后面多添加一个backup参数，这台服务器就会成为备份服务器。
在平时不使用，nginx不会给它转发任何请求。只有当其他节点全部无法连接的时候，nginx才会启用这个节点。
一旦有可用的节点恢复服务，该节点则不再使用，又进入后备状态。

可以两台机子互为热备，平时各自负责各自的服务。在做上线更新的时候，关闭一台服务器的tomcat后，nginx自动把流量切换到另外一台服务的后备机子上，从而实现无痛更新，保持服务的持续性，提高服务的可靠性。

关于这个参数的官档说明：
http://wiki.nginx.org/NginxHttpUpstreamModule
backup - (0.6.7 or later) only uses this server if the non-backup servers are all down or busy (cannot be used with the directive ip_hash)

摘自：http://hillside.iteye.com/blog/703281

http://chattool.sinaapp.com/?p=1063 ]]> http://www.jackxiang.com/post//#blogcomment <user@domain.com> Thu, 01 Jan 1970 00:00:00 +0000 http://www.jackxiang.com/post//#blogcomment