-
Notifications
You must be signed in to change notification settings - Fork 837
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
feat(scheduler): Scale down server logic #6246
base: v2
Are you sure you want to change the base?
Conversation
2393553
to
3ed62cd
Compare
3ebc37f
to
a9145c8
Compare
return | ||
} | ||
|
||
if event.UpdateContext == coordinator.SERVER_SCALE { |
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.
@driev this is the current proposed location to consume server scale (up / down) events and decide on whether actually to change server replicas. Open to suggestions if there are better places for this logic to be defined.
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.
For example SchedulerServer
could be extended with a ServerScaler
utility where the logic of scaling up and down could be defined. This is perhaps something we can consider as a follow up PR after we get scale up / down done?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer: