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

Attempt partial scale down when maxDisruption is set and unprocessed jobs < target #90

Merged
merged 4 commits into from
Jul 7, 2020

Conversation

alok87
Copy link
Contributor

@alok87 alok87 commented Jul 3, 2020

Fixes #89

Also, adds verbosity level for few important calls.

Result after this PR was made live at 20:32:
Screenshot 2020-07-03 at 8 47 32 PM

@alok87 alok87 changed the title Debug V(4), Extended V(3) and Resonable V(1) levels Attempt partial scale down when maxDisruption is set and unprocessed jobs < target Jul 3, 2020
@alok87 alok87 force-pushed the fix-89 branch 3 times, most recently from 70a4762 to cc9fc43 Compare July 3, 2020 11:40
@alok87 alok87 self-assigned this Jul 3, 2020
@alok87 alok87 requested a review from justjkk July 3, 2020 11:41
@alok87 alok87 added the bug Something isn't working label Jul 3, 2020
Exposed GetDesiredWorkers for test cases
Added Test Case for #89
@alok87 alok87 merged commit 7e8044c into master Jul 7, 2020
@alok87 alok87 deleted the fix-89 branch August 13, 2020 07:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Partial scale down is not happening in one scenario
2 participants