-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[improvement](backend balance) adjust the capacity cofficient of be load score #26874
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
[improvement](backend balance) adjust the capacity cofficient of be load score #26874
Conversation
|
run buildall |
1 similar comment
|
run buildall |
|
(From new machine)TeamCity pipeline, clickbench performance test result: |
TPC-H test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
dataroaring
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
deardeng
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
Be load score = replica num / avg replica num * replica num coef + used percent / avg used percent * capacity coef
And replica num coef = 1.0 - capacity coef
If capacity coef = 1.0, then replica num coef = 0, then the balance will ignore tablet num, only considering tablet size.
So the be balance will not move a empty tablet from high load backend to low load backend. Because moving this tablet, these two backends' load score will not change. And if there are lots of empty tablets, the balance may always pick them, but move failed.
So we let capacity coef <= 0.99, then the balance will always considering the tablet num. Then will make balance moving a tablet become possible.
Proposed changes
Issue Number: close #xxx
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...