Skip to content

Schedule based auto scaling decider #126855

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

Open
mielastic opened this issue Apr 15, 2025 · 1 comment
Open

Schedule based auto scaling decider #126855

mielastic opened this issue Apr 15, 2025 · 1 comment

Comments

@mielastic
Copy link

Description

Currently Elasticsearch only offers reactive or proactive storage deciders for auto scaling of data nodes. This is a feature request to add a "schedule" based decider to scale up/down based on a set schedule, peak hours, off peak hours etc. This will allow users to setup auto scaling based on predictable load changes so that they can increase or decrease Elasticsearch capacity at specific times.

For example, customer has a very large Elasticsearch cluster, where they experience a regular daily traffic pattern where load increases during regular business hours and declines toward the end of the day. They can configure a scaling schedule that aligns with this pattern to optimize costs and performance. i.e cluster has sufficient capacity to handle the day time peak traffic, but does not over-provision unneeded capacity at other times.

@mielastic mielastic added >enhancement needs:triage Requires assignment of a team area label labels Apr 15, 2025
@elasticsearchmachine elasticsearchmachine added the Team:Distributed Coordination Meta label for Distributed Coordination team label Apr 28, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination)

@elasticsearchmachine elasticsearchmachine removed the needs:triage Requires assignment of a team area label label Apr 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants