-
Notifications
You must be signed in to change notification settings - Fork 727
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
schedule: fix store maybe always overloaded #1586
Conversation
ooh, IMO the solution looks too tricky to understand. Is it possible to simply add a method |
Hmmm... Do we still need the overloaded state in store? If so, we may still need to reset this state. |
No need the state. Just use |
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.
rest LGTM
Signed-off-by: Ryan Leung <[email protected]>
Signed-off-by: Ryan Leung <[email protected]>
Signed-off-by: Ryan Leung <[email protected]>
Signed-off-by: Ryan Leung <[email protected]>
Signed-off-by: Ryan Leung <[email protected]>
* fix store maybe always overloaded Signed-off-by: Ryan Leung <[email protected]>
* fix store maybe always overloaded Signed-off-by: Ryan Leung <[email protected]>
What problem does this PR solve?
There are some cases which will cause the PD cannot generate operator since the store could be always overloaded and be filtered in the end.
What is changed and how it works?
This PR fixes this problem by removing reset logic.
Check List
Tests
Related changes