Scaling Out/Up

For a pay-per-use cluster, you can see its new price when confirming the scale-out or scale-up on the console. After the change is complete, the cluster will be billed based on the new price.

• The node storage capacity of a cluster can only be increased—not decreased. Select an appropriate node storage capacity based on the data volume and projected data growth.
• The storage capacity of the master and client nodes in a cluster cannot be expanded.
• The storage capacity of data nodes that use local disks cannot be expanded.
• For a multi-AZ cluster, the total number of client nodes must be greater than or equal to the number of AZs. (For a cluster spanning two AZs, this means a minimum of two client nodes; for a three-AZ deployment, a minimum of three client nodes.)
• Principles for adding cold data nodes to a multi-AZ cluster:
  • Node quantity requirement: A two-AZ cluster must have at least four cold data nodes (two in each AZ); and a three-AZ cluster must have at least three cold data nodes (one in each AZ).
  • Performance enhancement: To prevent uneven data distribution and ensure optimal query and ingestion performance, the number of cold data nodes should be an integer multiple of the number of AZs.
• For the range of node quantities supported by each node type, see Table 2.

  Table 2 Node quantity ranges

  Node Type	Value Range
  Data nodes	Without master nodes: 1 to 32 With master nodes: 1 to 200
  Master nodes	3, 5, 7, or 9 (must be an odd number from 3 to 9)
  Client nodes	1~64
  Cold data nodes	1–32

Before the change, learn about possible impacts and operation suggestions, and develop a plan to minimize these impacts.

Expanding the storage capacity of cluster nodes (vertical scaling) does not impact services, whereas adding new nodes or new node types (horizontal scaling) may have the following impacts:

• Impact on performance

  Adding new nodes does not interrupt services. However, after new nodes are added, data shards need to be redistributed to these nodes to balance the load, and this process will consume I/O performance. This is why you are advised to perform the operation during off-peak hours.

  To minimize this impact, it is advisable to adjust the data migration rate based on the cluster's traffic cycle: increase the data migration rate during off-peak hours to shorten the task duration, and decrease it before peak hours arrive to ensure optimal cluster performance. The data migration rate is determined by the indices.recovery.max_bytes_per_sec parameter. The default value of this parameter is the number of vCPUs multiplied by 8 MB. For example, for four vCPUs, the data migration rate is 32 MB/s. You can adjust it based on the service requirements.

  PUT /_cluster/settings  
  {  
    "transient": {  
      "indices.recovery.max_bytes_per_sec": "128MB"  
    }  
  }
  
  

• Characteristics of this process

  Once started, a scaling task cannot be stopped until it succeeds or fails.

• It takes 10 to 30 minutes to add new nodes or new node types (horizontal scaling), depending on the cluster's scheduling capabilities.
• It takes 10 to 15 minutes to expand the storage capacity of cluster nodes (vertical scaling).

• The cluster status is Available, and there are no ongoing tasks.
• Your CSS resource quotas are sufficient for the capacity expansion you are about to perform. You can check available resources on the Modify Configuration page.

If a cluster experiences rapid data growth or sustained high memory usage, you may add more nodes to it or increase the cluster nodes' storage capacity. This helps to improve service and data availability and durability.

1. Log in to the CSS management console.
2. In the navigation pane on the left, choose Clusters > Elasticsearch.
3. In the cluster list, find the target cluster, and choose More > Modify Configuration in the Operation column. The Modify Configuration page is displayed.
4. Click the Scale Cluster tab.
5. Set the necessary parameters.

   Table 3 Adding more nodes or increasing node storage capacity

   Parameter	Description
   Action	Select Scale out.
   Resources	Quantities of resources added.
   Nodes	Increase the number of nodes and node storage capacity in the Nodes and Node Storage Type columns. You can change multiple node types at the same time. For the range of node quantities supported by each node type, see Constraints. The value range of node storage capacity is determined by the node flavor you select. The value must be divisible by 20.

6. Click Next.
7. Confirm the information and click Submit.
8. Click Back to Cluster List to go back to the Clusters page. The Task Status is Scaling out. When Cluster Status changes to Available, the cluster has been successfully scaled out.

For a cluster that has no dedicated master, client, or cold data nodes, as the load on its data plane increases, you may dynamically add such nodes to it to share the load of the data nodes.

1. Log in to the CSS management console.
2. In the navigation pane on the left, choose Clusters > Elasticsearch.
3. In the cluster list, find the target cluster, and choose More > Modify Configuration in the Operation column. The Modify Configuration page is displayed.
4. Click the Add Node Types tab.

   If a cluster already has dedicated master, client, and cold data nodes, the Add Node Types tab is unavailable.

5. On the Add Node Types tab, configure the nodes.

   Table 4 Adding new node types

   Parameter	Description
   Node types	Select the type of nodes you want to add. Only the node types that the cluster does not already have are displayed. For example, if the cluster already has dedicated master nodes, only Client Node and Cold Data Node are displayed. Only one node type can be added at a time. For example, if you need to add both master and client nodes, you need to perform this task twice.
   Node Specifications	Select node specifications based on site requirements.
   Nodes	Set the number of nodes to add. For the value range, see Constraints.
   Node Storage Type	Set the node storage type. The storage capacity per master or client node is fixed to 40 GB.

6. Click Next.
7. Confirm the information and click Submit.

   Return to the cluster list page. The Task Status of the cluster is Scaling out. When Cluster Status changes to Available, nodes have been added successfully.

   • When adding master nodes for a cluster whose version is earlier than 7.x, restart data nodes and cold data nodes after Cluster Status changes to Available to make the configuration of the new master nodes take effect. Otherwise, the cluster status may be displayed as unavailable due to delayed status synchronization (when in fact the cluster services are available).
   • When adding client nodes, you can choose whether to restart data nodes and cold data nodes and bring the Cerebro and Kibana processes offline after Cluster Status changes to Available. This helps avoid conflicts.
   • When adding cold data nodes, you must restart data nodes to activate the hot tag after Cluster Status changes to Available. This ensures that the cold data nodes function properly. After cold data nodes are added, manually migrate historical data to them. For details, see Switching Between Hot and Cold Data.

   For details about the restart operation, see Restarting a Cluster.

• You can also upgrade the node specifications and change the EVS disk type of an Elasticsearch cluster. For details, see Changing Node Specifications.
• During a capacity expansion, if the resources in an AZ become insufficient, you can migrate the nodes in this AZ to another that has sufficient resources, and then perform the capacity expansion in the new AZ. For details, see Switching AZs.