Valentin V. Bartenev Wrote: ------------------------------------------------------- > On Tuesday 12 May 2015 09:25:05 jwroblewski wrote: > > My use case is that upstreams are supposed to return within ~100ms, > > therefore using burst is not an option. I wanted to use limit_req to > filter > > out traffic which is exceeds my backend's processing capacity, but > &gby jwroblewski - Nginx Mailing List - English
My use case is that upstreams are supposed to return within ~100ms, therefore using burst is not an option. I wanted to use limit_req to filter out traffic which is exceeds my backend's processing capacity, but apparently it is not the right tool to use, if it only operates with millisecond-precision... Could you please document this limitation?by jwroblewski - Nginx Mailing List - English
Hi, I'm not sure if this is the right place to report this issue, but perhaps someone has already run across it and has some insights... Basically, the "nginx_upstream_check_module" (versions 0.1.9 and 0.3.0) doesn't seem to be working with nginx 1.7 greater than 1.7.6. Upstreams don't get pinged for status, and calling check_status directive results in the following error: &quby jwroblewski - Nginx Mailing List - English
Hi, I'm observing an inconsistent behavior of ngx_http_limit_req_module in nginx 1.7.12. The relevant excerpts from my config: http { ... # A fixed string used as a key, to make all requests fall into the same zone limit_req_zone test_zone zone=test_zone:1m rate=5r/s; ... server { ... location /limit { root /test limit_req zone=test_zoby jwroblewski - Nginx Mailing List - English