-
Notifications
You must be signed in to change notification settings - Fork 124
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
Least connection mode is not working #810
Labels
bug
Something isn't working
Comments
TrekkieCoder
added a commit
to loxilb-io/loxilb-ebpf
that referenced
this issue
Oct 1, 2024
TrekkieCoder
added a commit
to loxilb-io/loxilb-ebpf
that referenced
this issue
Oct 1, 2024
UltraInstinct14
added a commit
that referenced
this issue
Oct 2, 2024
PR: gh-810 fixes for LC selection and added more tests to LC selftests
Some issues were found and fixed. @nik-netlox Can you please reconfirm if issue is resolved ? |
TrekkieCoder
added a commit
that referenced
this issue
Oct 2, 2024
gh-810 Merge lc-fix branch to main
This test has been validated. Closing it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When LB rule is created with --select=lc then client receives connection refused on subsequent connections.
To Reproduce
Steps to reproduce the behavior:
loxilb create rule: loxicmd create lb 20.20.20.1 --tcp=2020:8080 --endpoints=31.31.31.1:1,32.32.32.1:1,33.33.33.1:1 --select=lc
Run server app from all endpoints and open multiple connections from client.
Expected behavior
Client connection request must be sent to the endpoint having least number of active connections.
Screenshots
NA
Environment (please complete the following information):
Additional context
NA
The text was updated successfully, but these errors were encountered: