-
Notifications
You must be signed in to change notification settings - Fork 188
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
Create task cleanups for scale down at request update time #1811
Conversation
@@ -149,6 +151,24 @@ private void submitRequest(SingularityRequest request, Optional<SingularityReque | |||
requestState = oldRequestWithState.get().getState(); | |||
} | |||
|
|||
if (oldRequest.isPresent() && oldRequest.get().getInstancesSafe() < request.getInstancesSafe()) { |
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.
I think we want to swap the operands on this comparison.
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.
We do indeed, hadn’t actually gotten a chance to finish unit test and testing in staging in this one yet
PR all fixed up and working in QA |
🚢 |
We can run into a certain sate where consistent continuous instance numbers are not kept. If a cleanup is created between a request scaling down and the scheduler processing the pending request update, this can occur. This PR creates the task cleanups for the specific instances that need to be cleaned up at request update time to avoid that possible window.