dream110fly opened a new issue, #9547:
URL: https://github.com/apache/apisix/issues/9547

   ### Current Behavior
   
   we run apisix base on apisix-base,  can not close upstream keepalive even 
set apisix/conf/config.yaml keepalive_timeout to 0 or set  upstream config 
option keepalive_pool.idle_timeout to 0  as here 
https://apisix.apache.org/docs/apisix/2.13/admin-api/#upstream。 maybe because 
https://github.com/api7/apisix-nginx-module/blob/main/patch/1.21.4/lua-resty-core-enable_keepalive.patch#L177
  
         if not idle_timeout then
               idle_timeout = DEFAULT_KEEPALIVE_IDLE_TIMEOUT
   
   
   
   ### Expected Behavior
   
   set idle_timeout to one value such as 0 to close upstream keepalive
   
   ### Error Logs
   
   _No response_
   
   ### Steps to Reproduce
   
   1. config your route and upstream 
   2. set apisix/conf/config.yaml keepalive_timeout to 0 or set  upstream 
config option keepalive_pool.idle_timeout to 0
   3. catch network package to see wether keepalive is closed
   
   ### Environment
   
   - APISIX version (run `apisix version`):  2.13.1
   - Operating system (run `uname -a`): 3.10.0-514.el7.x86_64
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`): nginx 
version: openresty/1.19.3.1
   built by gcc 8.3.1 20190311 (Red Hat 8.3.1-3) (GCC)
   built with OpenSSL 1.1.1n  15 Mar 2022
   TLS SNI support enabled
   configure arguments: --prefix=/usr/local/openresty/nginx --with-cc-opt='-O2 
-DAPISIX_BASE_VER=0.0.0 -DNGX_SECURE_MEM -I/usr/local/openssl/include 
-I/usr/local/pcre/include -I/usr/local/zlib/include 
-Wno-error=deprecated-declarations' --add-module=../ngx_devel_kit-0.3.1 
--add-module=../echo-nginx-module-0.62 --add-module=../xss-nginx-module-0.06
   - LuaRocks version, for installation issues (run `luarocks --version`): 
/usr/bin/luarocks 2.3.0
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to