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

used size and available are zero after adding scatter region scheduler #3598

Open
lhy1024 opened this issue Apr 15, 2021 · 6 comments
Open
Assignees
Labels
severity/moderate type/bug The issue is confirmed as a bug.

Comments

@lhy1024
Copy link
Contributor

lhy1024 commented Apr 15, 2021

Bug Report

What did you do?

add scatter region scheduler

What did you expect to see?

work

What did you see instead?

image

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

5.0.0

@cosven
Copy link
Member

cosven commented Apr 16, 2021

/remove-severity major
/severity moderate

Can you explain more about what is influenced by this issue? @lhy1024
BTW, feel free to modify the severity.

@lhy1024
Copy link
Contributor Author

lhy1024 commented Apr 16, 2021

@cosven it will only influence scatter scheduler.I think it's more suitable as moderate.

@ti-chi-bot
Copy link
Member

@cosven: These labels are not set on the issue: severity/major.

In response to this:

/remove-severity major
/severity moderate

Can you explain more about what is influenced by this issue? @lhy1024
BTW, feel free to modify the severity.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

@lhy1024
Copy link
Contributor Author

lhy1024 commented Apr 23, 2021

#3593 Fixes unsuspected stat changes, but still investigating why range cluster data is wrong

@nolouch
Copy link
Contributor

nolouch commented Jun 2, 2021

fixed.

@nolouch nolouch closed this as completed Jun 2, 2021
@lhy1024
Copy link
Contributor Author

lhy1024 commented Jun 3, 2021

I think we need to investigate further, #3593 only fixes the anomalous data overwrite but does not learn why the range cluster data is wrong

@lhy1024 lhy1024 reopened this Jun 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/moderate type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

4 participants