You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A user at OSC hit this limit in NGINX. While I think the limit is OK and should definitely be there, I wonder how they hit this? Could it be that something in our code is making run away requests filling up this queue? I doubt we have rate limiting in any of our client side javascript, so that could be the case.
App 20573 output: [2021-07-13 16:00:28 -0400 ] INFO "method=GET path=/pun/sys/dashboard/files/fs/somefile format=html controller=FilesController action=fs status=200 duration=173589.09 view=51566.48"
[ W 2021-07-13 16:02:51.7054 56016/Ty age/Cor/Con/CheckoutSession.cpp:260 ]: [Client 14-14] Returning HTTP 503 due to: Request queue full (configured max. size: 100)
[ W 2021-07-13 16:02:58.1125 56016/T10 age/Cor/Con/CheckoutSession.cpp:260 ]: [Client 15-14] Returning HTTP 503 due to: Request queue full (configured max. size: 100)
App 20573 output: [2021-07-13 16:03:21 -0400 ] INFO "method=GET path=/pun/sys/dashboard/files/fs/somefile format=html controller=FilesController action=fs status=200 duration=172767.20 view=51266.80"
[ W 2021-07-13 16:05:19.6208 56016/T8 age/Cor/Con/CheckoutSession.cpp:260 ]: [Client 1-15] Returning HTTP 503 due to: Request queue full (configured max. size: 100)
A user at OSC hit this limit in NGINX. While I think the limit is OK and should definitely be there, I wonder how they hit this? Could it be that something in our code is making run away requests filling up this queue? I doubt we have rate limiting in any of our client side javascript, so that could be the case.
┆Issue is synchronized with this Asana task by Unito
The text was updated successfully, but these errors were encountered: