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

   ### Description
   
   Hello, APISIX team.
   in our prd env, we suffered a very strange scenario.
   we have a cluster which have 9 apisix instances.
   
   the upstream is using service discovery, which is eureka.
   our microservice is registerd in eureka, it deployed in k8s, use eureka 
exposed to apisix, the microservice has 150 instance.
   
   we deployed it in July this year, but recently, we find that the latency is 
increase(normal latency is about 100ms, but some latency is beyond 200ms), when 
we send a request directly to one of the microservice instance, it latency is 
about 100ms,but when the request proxy by apisix, it increased.
   
   we opened active healthcheck(use tcp way), when we closed the healthcheck, 
the latency suddenly recoverd to about 100ms.
   
   also we find the prometheus metrics may have some odd things. the following 
metrics is 0:
   `
   
       apisix_shared_dict_free_space_bytes{name="worker-events"} 0
       apisix_shared_dict_free_space_bytes{name="prometheus-metrics"} 0
   `
   the shared_dict **worker-events** and **prometheus-metrics** both are **10m**
   
   I want to know if the above shared_dict used up could result in healthcheck 
increase the latency.
   
   **I tried reopen it in our dev env, but failed, the error log indicate the 
prometheus has no memory**
   
   I find a other issue metioned : but seems no activity. #11345 
   
   hope your answer, thanks.
   
   
   
   ### Environment
   
   - APISIX version (run `apisix version`):2.15.3
   - 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`):3.5.0
   - 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