Re: Possible limitation of ngx_http_limit_req_module

2015-05-12 Thread Maxim Dounin
Hello! On Tue, May 12, 2015 at 12:33:11PM -0400, jwroblewski wrote: > 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, > > > theref

Re: Possible limitation of ngx_http_limit_req_module

2015-05-12 Thread Valentin V. Bartenev
On Tuesday 12 May 2015 12:33:11 jwroblewski wrote: > 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

Re: Possible limitation of ngx_http_limit_req_module

2015-05-12 Thread jwroblewski
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

Re: Possible limitation of ngx_http_limit_req_module

2015-05-12 Thread Valentin V. Bartenev
On Tuesday 12 May 2015 16:46:29 B.R. wrote: > I do not necessarily have a say on what is discussed here, but: > >1. I believe putting known limitations in the docs makes sense. Who >defined the docs as sticking to the most common use cases? Technical docs >are technical docs. I'm agre

Re: Possible limitation of ngx_http_limit_req_module

2015-05-12 Thread B.R.
I do not necessarily have a say on what is discussed here, but: 1. I believe putting known limitations in the docs makes sense. Who defined the docs as sticking to the most common use cases? Technical docs are technical docs. 2. Using burst answers a specific need which has not been ex

Re: Possible limitation of ngx_http_limit_req_module

2015-05-12 Thread Valentin V. Bartenev
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 > apparently it is not the righ

Re: Possible limitation of ngx_http_limit_req_module

2015-05-12 Thread jwroblewski
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-precisi

Re: Possible limitation of ngx_http_limit_req_module

2015-05-12 Thread Valentin V. Bartenev
On Monday 11 May 2015 10:59:46 jwroblewski wrote: > 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 > limi

Possible limitation of ngx_http_limit_req_module

2015-05-11 Thread jwroblewski
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 {