充值积分
下载资源前端资源详情
nginx_upstream_check_module-master.zip
大小:172.93KB
价格:14积分
下载量:0
评分:
5.0
上传者:m0_60821938
更新日期:2024-10-22

nginx-upstream-fair-master

资源文件列表(大概)

文件名
大小
nginx_upstream_check_module-master/
-
nginx_upstream_check_module-master/CHANGES
-
nginx_upstream_check_module-master/README
11.24KB
nginx_upstream_check_module-master/check.patch
6.78KB
nginx_upstream_check_module-master/check_1.11.1+.patch
7.74KB
nginx_upstream_check_module-master/check_1.11.5+.patch
8.13KB
nginx_upstream_check_module-master/check_1.12.1+.patch
7.87KB
nginx_upstream_check_module-master/check_1.14.0+.patch
7.87KB
nginx_upstream_check_module-master/check_1.16.1+.patch
8.21KB
nginx_upstream_check_module-master/check_1.2.1.patch
5.35KB
nginx_upstream_check_module-master/check_1.2.2+.patch
6.96KB
nginx_upstream_check_module-master/check_1.2.6+.patch
6.93KB
nginx_upstream_check_module-master/check_1.20.1+.patch
8.22KB
nginx_upstream_check_module-master/check_1.5.12+.patch
6.63KB
nginx_upstream_check_module-master/check_1.7.2+.patch
8.1KB
nginx_upstream_check_module-master/check_1.7.5+.patch
8.15KB
nginx_upstream_check_module-master/check_1.9.2+.patch
8.31KB
nginx_upstream_check_module-master/config
769B
nginx_upstream_check_module-master/doc/
-
nginx_upstream_check_module-master/doc/README.txt
11.24KB
nginx_upstream_check_module-master/doc/README.wiki
11.14KB
nginx_upstream_check_module-master/nginx-sticky-module.patch
1.67KB
nginx_upstream_check_module-master/nginx-tests/
-
nginx_upstream_check_module-master/nginx-tests/fastcgi_check.t
8.44KB
nginx_upstream_check_module-master/ngx_http_upstream_check_module.c
109.46KB
nginx_upstream_check_module-master/ngx_http_upstream_check_module.h
529B
nginx_upstream_check_module-master/ngx_http_upstream_jvm_route_module.patch
2.78KB
nginx_upstream_check_module-master/test/
-
nginx_upstream_check_module-master/test/README
9.66KB
nginx_upstream_check_module-master/test/inc/
-
nginx_upstream_check_module-master/test/inc/Module/
-
nginx_upstream_check_module-master/test/inc/Module/AutoInstall.pm
24.63KB
nginx_upstream_check_module-master/test/inc/Module/Install.pm
12.09KB
nginx_upstream_check_module-master/test/inc/Module/Install/
-
nginx_upstream_check_module-master/test/inc/Module/Install/AutoInstall.pm
2.11KB
nginx_upstream_check_module-master/test/inc/Module/Install/Base.pm
1.1KB
nginx_upstream_check_module-master/test/inc/Module/Install/Can.pm
1.71KB
nginx_upstream_check_module-master/test/inc/Module/Install/Fetch.pm
2.4KB
nginx_upstream_check_module-master/test/inc/Module/Install/Include.pm
525B
nginx_upstream_check_module-master/test/inc/Module/Install/Makefile.pm
11.51KB
nginx_upstream_check_module-master/test/inc/Module/Install/Metadata.pm
17.69KB
nginx_upstream_check_module-master/test/inc/Module/Install/TestBase.pm
539B
nginx_upstream_check_module-master/test/inc/Module/Install/Win32.pm
1.75KB
nginx_upstream_check_module-master/test/inc/Module/Install/WriteAll.pm
1.25KB
nginx_upstream_check_module-master/test/inc/Spiffy.pm
15.15KB
nginx_upstream_check_module-master/test/inc/Test/
-
nginx_upstream_check_module-master/test/inc/Test/Base.pm
17.55KB
nginx_upstream_check_module-master/test/inc/Test/Base/
-
nginx_upstream_check_module-master/test/inc/Test/Base/Filter.pm
6.99KB
nginx_upstream_check_module-master/test/inc/Test/Builder.pm
29.99KB
nginx_upstream_check_module-master/test/inc/Test/Builder/
-
nginx_upstream_check_module-master/test/inc/Test/Builder/Module.pm
1.39KB
nginx_upstream_check_module-master/test/inc/Test/More.pm
16.35KB
nginx_upstream_check_module-master/test/lib/
-
nginx_upstream_check_module-master/test/lib/Test/
-
nginx_upstream_check_module-master/test/lib/Test/Nginx.pm
9.31KB
nginx_upstream_check_module-master/test/lib/Test/Nginx/
-
nginx_upstream_check_module-master/test/lib/Test/Nginx/LWP.pm
13.14KB
nginx_upstream_check_module-master/test/lib/Test/Nginx/Socket.pm
59.03KB
nginx_upstream_check_module-master/test/lib/Test/Nginx/Util.pm
25.68KB
nginx_upstream_check_module-master/test/ragel/
-
nginx_upstream_check_module-master/test/ragel/Makefile
330B
nginx_upstream_check_module-master/test/ragel/http11.c
14.79KB
nginx_upstream_check_module-master/test/ragel/http11_parser.c
23.61KB
nginx_upstream_check_module-master/test/ragel/http11_parser.h
1.14KB
nginx_upstream_check_module-master/test/ragel/http11_parser.rl
3.47KB
nginx_upstream_check_module-master/test/ragel/http11_parser_common.rl
1.85KB
nginx_upstream_check_module-master/test/ragel/http11_response.c
7.98KB
nginx_upstream_check_module-master/test/ragel/http11_response.h
974B
nginx_upstream_check_module-master/test/ragel/http11_response.rl
2.84KB
nginx_upstream_check_module-master/test/ragel/http11_response_common.rl
883B
nginx_upstream_check_module-master/test/ragel/ragel_http_client.c
2.6KB
nginx_upstream_check_module-master/test/ragel/ragel_http_server.c
2.66KB
nginx_upstream_check_module-master/test/t/
-
nginx_upstream_check_module-master/test/t/check_interface.t
10.52KB
nginx_upstream_check_module-master/test/t/http_check.t
10.35KB
nginx_upstream_check_module-master/test/t/ssl_hello_check.t
3.38KB
nginx_upstream_check_module-master/test/t/tcp_check.t
3.57KB
nginx_upstream_check_module-master/test/test.sh
101B
nginx_upstream_check_module-master/upstream_fair.patch
3.26KB
nginx_upstream_check_module-master/util/
-
nginx_upstream_check_module-master/util/chomp.rb
90B
nginx_upstream_check_module-master/util/chomp.sh
166B
nginx_upstream_check_module-master/util/update-readme.sh
129B
nginx_upstream_check_module-master/util/wiki2pod.pl
3.05KB

资源内容介绍

nginx-upstream-fair-master
Name nginx_http_upstream_check_module - support upstream health check with NginxSynopsis http { upstream cluster { # simple round-robin server 192.168.0.1:80; server 192.168.0.2:80; check interval=5000 rise=1 fall=3 timeout=4000; #check interval=3000 rise=2 fall=5 timeout=1000 type=ssl_hello; #check interval=3000 rise=2 fall=5 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; location / { proxy_pass http://cluster; } location /status { check_status; access_log off; allow SOME.IP.ADD.RESS; deny all; } } }Description Add the support of health check with the upstream servers.Directives check syntax: *check interval=milliseconds [fall=count] [rise=count] [timeout=milliseconds] [default_down=true|false] [type=tcp|http|ssl_hello|mysql|ajp|fastcgi]* default: *none, if parameters omitted, default parameters are interval=30000 fall=5 rise=2 timeout=1000 default_down=true type=tcp* context: *upstream* description: Add the health check for the upstream servers. The parameters' meanings are: * *interval*: the check request's interval time. * *fall*(fall_count): After fall_count check failures, the server is marked down. * *rise*(rise_count): After rise_count check success, the server is marked up. * *timeout*: the check request's timeout. * *default_down*: set initial state of backend server, default is down. * *port*: specify the check port in the backend servers. It can be different with the original servers port. Default the port is 0 and it means the same as the original backend server. * *type*: the check protocol type: 1. *tcp* is a simple tcp socket connect and peek one byte. 2. *ssl_hello* sends a client ssl hello packet and receives the server ssl hello packet. 3. *http* sends a http request packet, receives and parses the http response to diagnose if the upstream server is alive. 4. *mysql* connects to the mysql server, receives the greeting response to diagnose if the upstream server is alive. 5. *ajp* sends a AJP Cping packet, receives and parses the AJP Cpong response to diagnose if the upstream server is alive. 6. *fastcgi* send a fastcgi request, receives and parses the fastcgi response to diagnose if the upstream server is alive. check_http_send syntax: *check_http_send http_packet* default: *"GET / HTTP/1.0\r\n\r\n"* context: *upstream* description: If you set the check type is http, then the check function will sends this http packet to check the upstream server. check_http_expect_alive syntax: *check_http_expect_alive [ http_2xx | http_3xx | http_4xx | http_5xx ]* default: *http_2xx | http_3xx* context: *upstream* description: These status codes indicate the upstream server's http response is ok, the backend is alive. check_keepalive_requests syntax: *check_keepalive_requests num* default: *check_keepalive_requests 1* context: *upstream* description: The directive specifies the number of requests sent on a connection, the default vaule 1 indicates that nginx will certainly close the connection after a request. check_fastcgi_param Syntax: *check_fastcgi_params parameter value* default: see below context: *upstream* description: If you set the check type is fastcgi, then the check function will sends this fastcgi headers to check the upstream server. The default directive looks like: check_fastcgi_param "REQUEST_METHOD" "GET"; check_fastcgi_param "REQUEST_URI" "/"; check_fastcgi_param "SCRIPT_FILENAME" "index.php"; check_shm_size syntax: *check_shm_size size* default: *1M* context: *http* description: Default size is one megabytes. If you check thousands of servers, the shared memory for health check may be not enough, you can enlarge it with this directive. check_status syntax: *check_status [html|csv|json]* default: *none* context: *location* description: Display the health checking servers' status by HTTP. This directive should be set in the http block. You can specify the default display format. The formats can be `html`, `csv` or `json`. The default type is `html`. It also supports to specify the format by the request argument. Suppose your `check_status` location is '/status', the argument of `format` can change the display page's format. You can do like this: /status?format=html /status?format=csv /status?format=json At present, you can fetch the list of servers with the same status by the argument of `status`. For example: /status?format=html&status=down /status?format=csv&status=up Below it's the sample html page: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <title>Nginx http upstream check status</title> <h1>Nginx http upstream check status</h1> <h2>Check upstream server number: 1, generation: 3</h2> <th>Index</th> <th>Upstream</th> <th>Name</th> <th>Status</th> <th>Rise counts</th> <th>Fall counts</th> <th>Check type</th> <th>Check port</th> <td>0</td> <td>backend</td> <td>106.187.48.116:80</td> <td>up</td> <td>39</td> <td>0</td> <td>http</td> <td>80</td> Below it's the sample of csv page: 0,backend,106.187.48.116:80,up,46,0,http,80 Below it's the sample of json page: {"servers": { "total": 1, "generation": 3, "server": [ {"index": 0, "upstream": "backend", "name": "106.187.48.116:80", "status": "up", "rise": 58, "fall": 0, "type": "http", "port": 80} ] }}Installation Download the latest version of the release tarball of this module from github (<http://github.com/yaoweibin/nginx_upstream_check_module>) Grab the nginx source code from nginx.org (<http://nginx.org/>), for example, the version 1.0.14 (see nginx compatibility), and then build the source with this module: $ wget 'http://nginx.org/download/nginx-1.0.14.tar.gz' $ tar -xzvf nginx-1.0.14.tar.gz $ cd nginx-1.0.14/ $ patch -p1 < /path/to/nginx_http_upstream_check_module/check.patch $ ./configure --add-module=/path/to/nginx_http_upstream_check_module $ make $ make installNote If you use nginx-1.2.1 or nginx-1.3.0, the nginx upstream round robin module changed greatly. You should use the patch named 'check_1.2.1.patch'. If you use nginx-1.2.2+ or nginx-1.3.1+, It added the upstream least_conn module. You should use the patch named 'check_1.2.2+.patch'. If you use nginx-1.2.6+ or nginx-1.3.9+, It adjusted the round robin module. You should use the patch named 'check_1.2.6+.patch'. If you use nginx-1.5.12+, You should use the patch named 'check_1.5.12+.patch'. If you use nginx-1.7.2+, You should use the patch named 'check_1.7.2+.patch'. The patch just adds the support for the official Round-Robin, Ip_hash and least_conn upstream modu

用户评论 (0)

发表评论

captcha

相关资源

NodeJS期刊投稿信息查询系统-毕业设计源码06128（源码+数据库）

基于微信小程序的期刊投稿信息查询系统有注册用户和管理员两个用户角色，下面针对两个用户角色的功能需求进行分析：1.注册用户：登录注册：用户可以注册新账号或使用已有账号登录。首页：展示系统的主要信息和功能入口。期刊信息：提供期刊的相关信息，包括期刊名称、投稿要求等。投稿信息：用户可以查看投稿相关的信息和要求。网站公告：显示系统发布的重要通知信息。我的：基本信息：用户可以查看和管理自己的基本信息。投稿信息：用户可以查看自己的投稿记录和状态。通知提醒：用户可以接收系统通知和提醒。2.管理员：后台首页：展示系统数据统计和管理入口。系统用户：管理系统中的各类用户。期刊信息管理：管理系统中期刊的相关信息。投稿信息管理：管理用户的投稿信息和处理投稿状态。通知提醒管理：发布、编辑和删除系统通知和提醒。轮播图管理：管理系统首页的轮播图内容。系统通知管理：管理系统发布的通知信息。权限管理：管理系统用户的权限和角色设置。这个系统旨在为投稿者和管理员提供一个便捷的投稿信息查询平台，同时管理员可以管理系统中的期刊信息、投稿信息和系统通知等内容，确保系统运行顺畅。

14.78MB39积分

时间序列异常检测相关代码

时间序列异常检测代码

1.72MB44积分

java swing项目购物系统mysql数据库-java课程设计毕业设计期末大作业

本资源为Java Swing项目购物系统，采用MySQL数据库，适用于Java课程设计、毕业设计以及期末大作业的学习参考。该系统使用Java Swing构建用户界面，结合JDBC与MySQL数据库实现商品查询、购物车管理等功能模块。该项目非常适合在校大学生进行参考与学习，同时为Java技术爱好者提供了极好的学习资源。通过本项目，用户可以深入学习Java图形界面编程和数据库操作的综合应用。

1.16MB16积分

java swing项目汽车租赁系统mysql数据库-java课程设计毕业设计期末大作业

本资源为Java Swing项目汽车租赁系统，基于MySQL数据库，适用于Java课程设计、毕业设计和期末大作业的学习参考。系统采用Java Swing构建用户友好的图形界面，结合JDBC和MySQL数据库实现车辆信息管理功能。该系统功能丰富，结构清晰，具有良好的可扩展性，便于学习与理解。非常适合在校大学生作为课程设计或毕业设计的参考项目，同时也是Java技术爱好者进行编程实践的理想素材。本项目可以帮助用户掌握Java图形界面编程和数据库交互的技术要点。

1.19MB35积分