Wow, it is a great workaround. If the upstream response times are contained
proxy_cache_lock_timeout, this should work perfectly.
Thank you for the help.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,276344,276350#msg-276350
___
nginx maili
On Wed, Sep 13, 2017 at 07:47:25AM -0400, sivasara wrote:
> Ah.. thanks for the reply.
> 500ms seems too large. Is there any way to decrease this wait time?
Currently there's no way to change 500ms to a different value. What you can do
is reduce proxy_cache_lock_timeout (5s by default) to make t
Ah.. thanks for the reply.
500ms seems too large. Is there any way to decrease this wait time?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,276344,276347#msg-276347
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/l
Hello,
On Wed, Sep 13, 2017 at 06:07:34AM -0400, sivasara wrote:
> Greetings everbody,
>
> I have the following config. I give 3 simulatneous requests and 1 goes back
> to the upstream and the 2 of them are in proxy_cache_lock. After the first
> request completes, I am always seeing 500ms delay w
