Type to search.

Autoscaling

Serverless

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Serverless interfaces and procedures might differ from classic Elastic Stack deployments.

ECH

Elastic Cloud Hosted lets you manage and configure one or more deployments of the versioned Elastic Stack, hosted on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

ECK

Elastic Cloud on Kubernetes extends Kubernetes orchestration capabilities to allow you to deploy and manage components of the Elastic Stack.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

ECE

Elastic Cloud Enterprise is a self-managed orchestration platform for deploying and managing the Elastic Stack at scale.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

The autoscaling feature adjusts resources based on demand. A deployment can use autoscaling to scale resources as needed, ensuring sufficient capacity to meet workload requirements. In Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and Elastic Cloud Hosted deployments, autoscaling follows predefined policies, while in Serverless, it is fully managed and automatic.

Tip - Serverless handles autoscaling for you

By default, Elastic Cloud Serverless automatically scales your Elasticsearch resources based on your usage. You don't need to enable autoscaling.

Indirect use only

This feature is designed for indirect use by Elastic Cloud Hosted, Elastic Cloud Enterprise, and Elastic Cloud on Kubernetes. Direct use is not supported.

Cluster autoscaling allows an operator to create tiers of nodes that monitor themselves and determine if scaling is needed based on an operator-defined policy. An Elasticsearch cluster can use the autoscaling API to report when additional resources are required. For example, an operator can define a policy that scales a warm tier based on available disk space. Elasticsearch monitors disk space in the warm tier. If it predicts low disk space for current and future shard copies, the autoscaling API reports that the cluster needs to scale. It remains the responsibility of the operator to add the additional resources that the cluster signals it requires.

A policy is composed of a list of roles and a list of deciders. The policy governs the nodes matching the roles. The deciders provide independent estimates of the capacity required. See Autoscaling deciders for details on available deciders.

Cluster autoscaling supports:

  • Scaling machine learning nodes up and down.
  • Scaling data nodes up based on storage.

Autoscaling only scales data nodes up and doesn't scale them down. If you delete data and want to reduce the size of a data tier in Elastic Cloud Hosted or Elastic Cloud Enterprise, adjust its size manually.

In Elastic Cloud on Kubernetes, storage can't be scaled down. For more information, refer to the storage restrictions for ECK autoscaling.

Trained model auto-scaling for self-managed deployments

The available resources of self-managed deployments are static, so trained model autoscaling is not applicable. However, available resources are still segmented based on the settings described in this section.

Trained model autoscaling automatically adjusts the resources allocated to trained model deployments based on demand. This feature is available on all cloud deployments (ECE, ECK, ECH) and Serverless. Refer to Trained model autoscaling for details.

To ensure availability and avoid unnecessary scaling, trained model deployments operate with defined cooldown periods.

Trained model autoscaling supports:

  • Scaling trained model deployments
Note

Autoscaling is not supported on Debian 8.

Find instructions on setting up and managing autoscaling, including supported environments, configuration options, and examples: