GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
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
This scheduler tries to disperse the adjacent region.
*: add adjacent region balance
--wip-- [skip ci]
*: adjust scheduler interface
*: change resource kind
add disperse by leader
Merge branch 'master' into shuning/adjacent-region-2
change should balance condition
adjust limit for two kind
set operator priority
PTAL @disksing @zhangjinpeng1987 @Connor1996
add cache and choice the max length adjacent region
The stores should be updated everytime Schedule is called. If the namespace feature is enabled, the stores may change.
the assigned store id is the exclude id.
Can you add some comments about why these regions will move like this?
This seems not right, for example, if maxLen = 0, len(adjacentRegions) = 2, then adjacentRegions will be clear, but what if the next region is also adjacent?
BTW, the flow in this for loop seems not straight.
maxLen = 0, len(adjacentRegions) = 2
if next region is also adjacent, thelen(adjacentRegions) will be 3 not 2. I mean it will not execute to here because of continue in L174. here we Intention to record max length adjacent regions.
Got it, but it seems not Intuitive :(
Merge branch 'master' into shuning/adjacent-region