Hi there,
I have combined the client ip concurrency and cluster concurrency(total
requests) together as below ,seems it works as expected.
limit_req_zone $binary_remote_addr zone=one:10m rate=10r/s; # one client ip
concurrency
limit_req_zone "all" zone=all:20m rate=2000r/s; #cluster concurrency
On Sun, Dec 03, 2017 at 11:58:16AM +0800, tongshus...@migu.cn wrote:
Hi there,
> I might have misunderstood some concepts and rectify them here:
> burst--bucket size;
Yes.
> rate--water leaks speed (not requests sent speed)
Yes.
The server can control how long it waits before starting to proc
