If a cluster can process current traffic without fully utilizing its resources, you can scale in the cluster to cut costs.
Scaling in a Logstash cluster means to randomly remove some of its nodes, so that it is less costly to keep it running.
Scale-in process: Random remove cluster nodes and modify the cluster configuration.
For a pay-per-use cluster, you can see its new price when confirming the scale-in on the console. After the scale-out or scale-up is complete, the new price will apply. For pricing details, see .
Before the change, learn about possible impacts and operation suggestions, and develop a plan to minimize these impacts.
Taking Logstash nodes offline usually does not interrupt services. However, jobs that are running on these will be stopped, causing the cluster throughput to decrease.
Once started, a scaling task cannot be stopped until it succeeds or fails.
The following formula can be used to estimate how long a scale-in operation will take:
Scale-in duration (min) = 5 (min) x Number of nodes to be removed
where, 5 minutes is the duration per node. It is an empirical value.
The cluster status is Available, and there are no ongoing tasks.
Parameter | Description |
|---|---|
Action | Select Scale in. |
Resources | Quantities of resources reduced. |
Nodes | Reduce the number of nodes in the Nodes column. |
To optimize costs, you may also reduce the capacity of a Logstash cluster by downgrading node specifications. For details, see Changing the Node Specifications of a Logstash Cluster.