Closed sandy420 closed 3 years ago
Is there any basic monitoring data, such as the number of TCP connections and IO throughput on each node? In addition, is the Kernel configuration on each node consistent?
What data is your analysis based on in the question? Is the log of upstream eureka? Have you analyzed the access.log data of apisix?
I see you have health_check configured, just a reminder that health_check affects roundrobin. Can you be sure that the back-end node is always healthy?
I see you have health_check configured, just a reminder that health_check affects roundrobin. Can you be sure that the back-end node is always healthy?
all back-end nodes are normal
Is there any basic monitoring data, such as the number of TCP connections and IO throughput on each node? In addition, is the Kernel configuration on each node consistent? A: all back-end node Kernel configure are consistent. What data is your analysis based on in the question? Is the log of upstream eureka? Have you analyzed the access.log data of apisix? A: The apisix cluster configuration is consistent with the kernel parameters. The following chart is based on apisix log analysis. In the chart, the request for each apisix assigned to the back-end node is very different.
Is there a personalized strategy for different requests? Is it possible to filter a specific API log analysis request and whether the load is balanced?
Issue description
My upstream's type is RoundRobin,priority is 10,and my config.yaml See below:
The back-end node is Eureka gateway. During peak hours, some back-end nodes reach 400 million QPS, some 200 million QPS and some 300 million QPS, which is very unbalanced. All my requests are short connections. Has anyone encountered them? Please let us know the solution, thank you!!!
Environment
apisix version
):2.10.0uname -a
):centos 7.3nginx -V
oropenresty -V
):curl http://127.0.0.1:9090/v1/server_info
to get the info from server-info API):luarocks --version
):