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

   ### Current Behavior
   
   We find that sometimes Apisix access upstream got 502 bad gateway error even 
if upstream exist.
   Error Rate: 
   - 1/42458 in 15 minutes
   - 500+ times in 1 day
   
   ![CleanShot 2024-10-11 at 19 23 
34@2x](https://github.com/user-attachments/assets/4649bbef-81c8-41c7-a224-954c24fc87b3)
   
   ![CleanShot 2024-10-11 at 19 24 
05@2x](https://github.com/user-attachments/assets/5813a1c3-4b02-43d1-8fcd-8be94d6b2e77)
   
   ![CleanShot 2024-10-11 at 19 25 
56@2x](https://github.com/user-attachments/assets/d8ef35e0-7de7-4b94-b839-2ebd1cded9bd)
   
   
   
   ### Expected Behavior
   
   _No response_
   
   ### Error Logs
   
   _No response_
   
   ### Steps to Reproduce
   
   1. access upstream through apisix
   
   ### Environment
   
   - APISIX version (run `apisix version`): 3.2.2
   - Operating system (run `uname -a`): Linux apisix-9d7bb89b8-2cv6k 
5.10.134-16.1.al8.x86_64 #1 SMP Thu Dec 7 14:11:24 UTC 2023 x86_64 GNU/Linux
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`):  
openresty/1.21.4.1
   - etcd version, if relevant (run `curl 
http://127.0.0.1:9090/v1/server_info`): 3.5.10
   - 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: [email protected]

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

Reply via email to