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

feat(scheduler): Scale down server logic #6246

Draft
wants to merge 13 commits into
base: v2
Choose a base branch
from

Conversation

sakoush
Copy link
Member

@sakoush sakoush commented Feb 7, 2025

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

@sakoush sakoush added the v2 label Feb 7, 2025
@sakoush sakoush force-pushed the INFRA-1234/server_scale_down_policy branch from 2393553 to 3ed62cd Compare February 10, 2025 13:19
@sakoush sakoush force-pushed the INFRA-1234/server_scale_down_policy branch from 3ebc37f to a9145c8 Compare February 11, 2025 12:36
return
}

if event.UpdateContext == coordinator.SERVER_SCALE {
Copy link
Member Author

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.

Copy link
Member Author

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant