-
Notifications
You must be signed in to change notification settings - Fork 384
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
Use resize API to scale running clusters #1541
Conversation
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.
Please see comments inline
Codecov Report
@@ Coverage Diff @@
## master #1541 +/- ##
==========================================
- Coverage 90.17% 90.07% -0.10%
==========================================
Files 132 132
Lines 10560 10585 +25
==========================================
+ Hits 9522 9534 +12
- Misses 663 669 +6
- Partials 375 382 +7
|
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.
please also run go fmt
on changed files
… await for resizing clusters)
570dd81
to
37144f5
Compare
…tate from PENDING / RESIZING / RESTARTING states
…d to waitForClusterStatus, now we no longer wait and see whether resize api can be used, only call it if the cluster is in a running state
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.
logic simplification requested
TODO: Confirm that adding omitempty for num_workers does not cause serialisability issues for single node clusters (ie num_workers = 0) |
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.
And please use newer testing shorthands
Resize API has the advantage of not restarting the cluster incase of manual scaling (
num_workers
) / autoscale parameter change (min_workers
,max_workers
)Tested using