You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@apisix.apache.org by "shuosiw (via GitHub)" <gi...@apache.org> on 2026/01/19 10:34:49 UTC

Re: [I] help request: why apisix dont update healthcheck upstream ip when upstream ip is no use [apisix]

shuosiw commented on issue #12803:
URL: https://github.com/apache/apisix/issues/12803#issuecomment-3767618550

   oh, we found that all of these errors are coming from the same APISIX pod.
   
   Currently, the APISIX gateway is deployed on Kubernetes and its configuration is managed via etcd. There are 10 pods running in the production environment, and we’ve found that all 503 errors are coming from just one of these pods.
   
   From the overall APISIX architecture perspective, when scaling down an upstream backend whose weight has already been set to 0, 503 errors theoretically should not occur. At the moment we don’t have any clear ideas, so we’d like to ask for help and see if there are any possible explanations or guesses.
   


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