-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: when a domain name exists in the upstream node configuration, roundrobin is abnormal #4047
Labels
bug
Something isn't working
Comments
@spacewander @membphis Please take a look. |
nice job @Firstsawyou we need to fix this bug ^_^ |
Got it. |
spacewander
added a commit
to spacewander/incubator-apisix
that referenced
this issue
Apr 15, 2021
Fix apache#4047 Signed-off-by: spacewander <spacewanderlzx@gmail.com>
4 tasks
spacewander
added a commit
to spacewander/incubator-apisix
that referenced
this issue
Apr 15, 2021
Fix apache#4047 Signed-off-by: spacewander <spacewanderlzx@gmail.com>
spacewander
added a commit
that referenced
this issue
Apr 16, 2021
Fix #4047 Signed-off-by: spacewander <spacewanderlzx@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue description
When configuring upstream, "upstream.type" is "roundrobin". When there is a domain name in the upstream
node
(ip and domain name are mixed use/all are configuration domain names), then only the node with the largestweight
value will be hit. When there are multiple maximumweight
nodes, multiple nodes will be accessed inroundrobin
mode.Environment
apisix version
): 2.5uname -a
): Linuxnginx -V
oropenresty -V
): nginx version: openresty/1.19.3.1curl http://127.0.0.1:9090/v1/server_info
to get the info from server-info API): 3.4.0Minimal test code / Steps to reproduce the issue
After the request is successful, the upstream will return the corresponding port number.
weight
is the same.Test:
localhost.localdomain
domain name node has the largestweight
.Test:
localhost.localdomain
domain name node has the largestweight
.Test:
What's the expected result?
When there is a domain name configuration in upstream and the domain name node has the maximum
weight
value, it should be able to roundrobin all nodes.The text was updated successfully, but these errors were encountered: