You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by "imtzw (via GitHub)" <gi...@apache.org> on 2024/04/11 01:11:38 UTC

[I] help request: upstream reset when client rate limited [apisix]

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

   ### Description
   
   when client has rate limit (such as 50k/s) , in apisix's connection with upstream appears zero window , then it turns out apisix reset tcp connection with upstream then ( not immediately) sends a FIN to client , even if client tries to keep alive.
   it seems for me, modifying http.send_timeout in config.yaml will resolve this , but im concerned about the reason and what is best method? 
   
   ### Environment
   
   - APISIX version (run `apisix version`):
   - Operating system (run `uname -a`):
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`):
   - etcd version, if relevant (run `curl http://127.0.0.1:9090/v1/server_info`):
   - APISIX Dashboard version, if relevant:
   - Plugin runner version, for issues related to plugin runners:
   - LuaRocks version, for installation issues (run `luarocks --version`):
   


-- 
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.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] help request: upstream reset when client rate limited [apisix]

Posted by "imtzw (via GitHub)" <gi...@apache.org>.
imtzw commented on issue #11142:
URL: https://github.com/apache/apisix/issues/11142#issuecomment-2081750183

   This seems not a bug. 
   when a socket receives faster from nginx than it sends to client, it will not be ready for a while.
   if nginx doesnot permit buffer body, it may for such a while recv nothing from upstream. thus upstream's sending is blocked for just such a while ( if the upstream sends healthily , its send-queue is fullfilled instantly) 


-- 
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


Re: [I] help request: upstream reset when client rate limited [apisix]

Posted by "imtzw (via GitHub)" <gi...@apache.org>.
imtzw closed issue #11142: help request: upstream reset when client rate limited
URL: https://github.com/apache/apisix/issues/11142


-- 
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


Re: [I] help request: upstream reset when client rate limited [apisix]

Posted by "shreemaan-abhishek (via GitHub)" <gi...@apache.org>.
shreemaan-abhishek commented on issue #11142:
URL: https://github.com/apache/apisix/issues/11142#issuecomment-2051435312

   > 2.10.1
   
   The version is too old, please consider upgrading or check if the bug exists in newer versions. If possible please share the steps on how to reproduce this issue thanks>


-- 
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