You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2021/07/08 11:12:42 UTC
[GitHub] [apisix] tokers commented on issue #4461: request help: How much lua_max_pending_timers should be set to
tokers commented on issue #4461:
URL: https://github.com/apache/apisix/issues/4461#issuecomment-876350778
> I only caught the exception refer this #3169. Because without it, my user will get a 500 error when the timer is insufficient.
>
> I not use v2.7. I reproduced this problem in v2.3. In addition, I found that the code of balancer.lua has been rewritten in v2.3. In the error log, I only saw one line of error message:
>
> ```
> 2021/07/08 16:46:17 [error] 31019#31019: *166383 [lua] upstream.lua:88: fetch_healthchecker(): fail to create healthcheck instance: failed to create 'healthy' timer: too many pending timers, client: 127.0.0.1, server: , request: "POST /rpc/account HTTP/1.1", host: "test.xxx.com", referrer: "https://test.xxx.com/circle/"
> ```
>
> The way I reproduce the problem:
>
> 1. Reduce the number of timers. like this
>
> ```
> lua_max_pending_timers 15;
> lua_max_running_timers 12;
> ```
>
> 2.Open a page with a large number of requests, and then constantly force a refresh
Seems that `15` is too small for APISIX as the max pending number of timers.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org