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

unbalanced bytes and keys rate between auto scaling node with others #3098

Open
Tracked by #5691
CheneyDing opened this issue Oct 22, 2020 · 3 comments
Open
Tracked by #5691
Labels
component/schedule Scheduling logic. type/enhancement The issue or PR belongs to an enhancement.

Comments

@CheneyDing
Copy link
Contributor

CheneyDing commented Oct 22, 2020

Bug Report

What did you do?

test hot region

TiDB 16 core 8GB 3 nodes
TiKV 8 core 4GB 3 nodes

go-ycsb config

workload=core
recordcount=2500000000
operationcount=100000000000
threadcount=800 
insertstart=0
fieldcount=2
fieldlength=512
readallfields=true
writeallfields=true
fieldlengthdistribution=constant
readproportion=1
updateproportion=0
insertproportion=0
readmodifywriteproportion=0
scanproportion=0
maxscanlength=200
scanlengthdistribution=uniform
requestdistribution=zipfian
table=usertable

What did you expect to see?

balanced read rate bytes and keys between auto scaling node with others

What did you see instead?

unbalanced read bytes and keys rate
image

What version of PD are you using (pd-server -V)?

ai-sche-4ea1991
todo: test on master
todo: check auto scaling node config

@CheneyDing CheneyDing added the type/bug The issue is confirmed as a bug. label Oct 22, 2020
@CheneyDing CheneyDing changed the title new node bytes rate is different with others unbalanced bytes and keys rate between auto scaling node with others Oct 22, 2020
@lhy1024
Copy link
Contributor

lhy1024 commented Oct 23, 2020

Maybe we should test it on the master branch

@CheneyDing
Copy link
Contributor Author

test result on master-4252d7e , almost the same as before.
image
image

@nolouch nolouch added type/enhancement The issue or PR belongs to an enhancement. component/schedule Scheduling logic. and removed type/bug The issue is confirmed as a bug. labels Dec 10, 2020
@nolouch
Copy link
Contributor

nolouch commented Dec 10, 2020

We should improve the balance algorithm, and let it converge better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/schedule Scheduling logic. type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Development

No branches or pull requests

3 participants