mcdullbloom

> My above assumption was correct. Each new `POST` call will reset the healthchecks. Closing this ticket. I also have a ingress controller to change my usptream node, then health...

I found the answer by debuging `lua-resty-lock`. There is a bug in `pcall` which has been fixed. **fix(lock) handle all resty.lock failure modes (https://github.com/Kong/lua-resty-healthcheck/pull/112)** > Kong `2.8.1` uses `lua-resty-healthcheck =...

There're not any error logs.Just set max_body_size failed. plugin: "plugins": { "client-control":{ "max_body_size": 100 } } (gdb) p max_body_size $1 = 0 Detail debug info： ``` (gdb) (gdb) b ngx_http_read_client_request_body...

not yet. > @mcdullbloom have you solved your problem?

> Hi @mcdullbloom are you talking about this only ? correct me if I have misunderstood it.  @Abhijeetmishr It seems that your requet header is bad and apisix returns...

@hardikpatel9 It seems the bug of asynch nginx and doesn't mater with qatengine and openssl.You can reproduce it by constraining `SSL_get_error ` return `SSL_ERROR_WANT_READ` in the mode of `qat-sw`.

 @weeweetan I meet the problem too. `ngx_ssl_shutdown` lead to single cpu core high usage.Is it the same?

how to reproduce?

I don't get it.What does the client should do after receive the response? Can you give more details?

@hardikpatel9 @weeweetan not only stream but also http. Condition 1: asynch ssl server { listen 443 ssl asynch; Condition2: ssl_shutdown return -1 ``` for ( ;; ) { /* *...