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

server/region: add pending peers #421

Merged
merged 41 commits into from
Dec 13, 2016
Merged

Conversation

huachaohuang
Copy link
Contributor

This PR filters region with down/pending peers from schedule, we also
need to check pending peers in operator, but I will do that later.

@huachaohuang huachaohuang changed the base branch from huachao/check-busy to master December 8, 2016 10:11
@huachaohuang huachaohuang changed the base branch from master to huachao/check-busy December 8, 2016 10:11
@huachaohuang huachaohuang changed the base branch from huachao/check-busy to master December 8, 2016 10:17
@huachaohuang huachaohuang changed the title [DNM] server/region: add pending peers server/region: add pending peers Dec 9, 2016
@huachaohuang
Copy link
Contributor Author

PTAL @siddontang @overvenus

@siddontang
Copy link
Contributor

LGTM

@huachaohuang
Copy link
Contributor Author

PTAL @overvenus

I think the score things are too complicated, we can calculate
the scores more easily.
I think the score things are too complicated, we can calculate
the scores more easily.
Coordinator can control the speed of different schedulers.

Every scheduler has a unique name, we can add API to run or stop any
schedulers dynamically, and different schedulers can run concurrently.
I think the score things are too complicated, we can calculate
the scores more easily.
Coordinator can control the speed of different schedulers.

Every scheduler has a unique name, we can add API to run or stop any
schedulers dynamically, and different schedulers can run concurrently.
I think the score things are too complicated, we can calculate
the scores more easily.
Coordinator can control the speed of different schedulers.

Every scheduler has a unique name, we can add API to run or stop any
schedulers dynamically, and different schedulers can run concurrently.
I think the score things are too complicated, we can calculate
the scores more easily.
I think the score things are too complicated, we can calculate
the scores more easily.
I think the score things are too complicated, we can calculate
the scores more easily.
I think the score things are too complicated, we can calculate
the scores more easily.
Coordinator can control the speed of different schedulers.

Every scheduler has a unique name, we can add API to run or stop any
schedulers dynamically, and different schedulers can run concurrently.
I think the score things are too complicated, we can calculate
the scores more easily.
I think the score things are too complicated, we can calculate
the scores more easily.
I think the score things are too complicated, we can calculate
the scores more easily.
Copy link
Member

@overvenus overvenus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@huachaohuang huachaohuang merged commit 4ddeae5 into master Dec 13, 2016
@huachaohuang huachaohuang deleted the huachao/check-pending-peers branch December 13, 2016 10:09
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

Successfully merging this pull request may close these issues.

None yet

3 participants