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.

Sign up for GitHub

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

Jump to bottom

if we should check aliveness in load-balancer #572

Open

VendettaReborn opened this issue Sep 4, 2024 · 1 comment

Contributor

VendettaReborn commented Sep 4, 2024

we choose the proxy in load-balance group based on hash algo's direct output, without checking the chosen proxy's aliveness

is it expected to do so? clash.meta will retry if the calculated proxy is not alive

this issue is related to the feature request of sticky-sessions strategy, if the aliveness is not checked, the behavior of consistent-hash and sticky-sessions are very much alike

Member

ibigbug commented Sep 4, 2024

Good point.

Nginx does provide two approaches regarding the availability of the upstream server https://docs.nginx.com/nginx/admin-guide/load-balancer/http-load-balancer/#method

There might be some concepts we can borrow from.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment