Skip to content
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

Upstream load balance weight #570

Open
vgabunia opened this issue Oct 4, 2024 · 9 comments
Open

Upstream load balance weight #570

vgabunia opened this issue Oct 4, 2024 · 9 comments

Comments

@vgabunia
Copy link

vgabunia commented Oct 4, 2024

Hi,
What is weight login in upstream/parent proxy , less means better of lower priority? In the following example:

1.1.1.1:33080?w=1 -P 2.1.1.1:33080?w=2

upstream 2.1.1.1 will receives more or less traffic? Distribution would be 2/1?
Thank you!

@snail007
Copy link
Owner

snail007 commented Oct 5, 2024

2/3

@vgabunia
Copy link
Author

vgabunia commented Oct 5, 2024

Hi,
Thank you for reply.
Can you explain me logic, it is important for me.
Why 2/3?
Thank you

@snail007
Copy link
Owner

snail007 commented Oct 6, 2024

2/(1+2)

@vgabunia
Copy link
Author

Hi, I Using LB like this:
proxy http --lb-method=weight -T tcp -P 1.1.1.1:33080?w=1 -P 2.1.1.1:33080?w=2 -P 3.1.1.1:33080?w=1 -t tcp - p :33080

Traffic is always coming from one source, and always one upstream is chosen. this is normal process or I miss something?

@snail007
Copy link
Owner

this is the feature of commercial edition

@vgabunia
Copy link
Author

I bought license :)
I have 6 licenses :)

@vgabunia
Copy link
Author

I thin weight logic is not clear for me :(
Let me ask you:
if on one server i have 30 IP and on another i have 60 , if i will use weight ?w=30 for first and ?w=60 it would be correct?

@snail007
Copy link
Owner

wrong

@vgabunia
Copy link
Author

vgabunia commented Oct 14, 2024 via email

Repository owner deleted a comment Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants