-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Comments
2/3 |
Hi, |
2/(1+2) |
Hi, I Using LB like this: Traffic is always coming from one source, and always one upstream is chosen. this is normal process or I miss something? |
this is the feature of commercial edition |
I bought license :) |
I thin weight logic is not clear for me :( |
wrong |
Hi,
thank you.
can you recommend how to do correctly?
…On Mon, Oct 14, 2024 at 1:14 PM snail007 ***@***.***> wrote:
wrong
—
Reply to this email directly, view it on GitHub
<#570 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AR5RCJLYXPHUNICYEJMV56TZ3ODPVAVCNFSM6AAAAABPMF4HG6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJQGU2DCOJUGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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!
The text was updated successfully, but these errors were encountered: