Help Center/ Cloud Search Service/ User Guide/ Using Logstash for Data Migration/ Managing Logstash Clusters/ Changing the Node Specifications of a Logstash Cluster
Updated on 2025-09-05 GMT+08:00
View PDF
Share

Changing the Node Specifications of a Logstash Cluster

If the workloads on the data plane of a Logstash cluster change, you can scale the cluster vertically by changing its node specifications.

Typically, you increase node specifications instead of decreasing them. Common scenarios include:

  • In the face of fast data growth, node specifications can be increased for a Logstash cluster to increase data processing and storage capacities, thus enhancing overall performance.
  • During peak hours, node specifications can be increased for a Logstash cluster to handle the extra load.

Decreasing node specifications will reduce the cluster's data processing and storage capacities. Exercise caution.

The process of changing node specifications is as follows:

  1. Bring a node offline.
  2. Change the node specifications.
  3. Restart the node.
  4. After the node recovers, proceed to another node and repeat the steps above. This goes on until all nodes are changed.

The node specifications are changed one node at a time. This is to ensure that there are sufficient resources to keep services running.

Prerequisites

  • 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.
    Figure 1 Checking available resources

Impact on Billing

For a pay-per-use cluster, you can see its new price when confirming the node specifications or storage type change on the console. After the scale-out or scale-up is complete, the new price will apply. For pricing details, see Cloud Search Service Price Calculator.

For a yearly/monthly cluster, you can also see the new price when you confirm the change. In the case of an upgrade, a new order is triggered when you confirm the change; and in the case of a downgrade, a refund request is triggered when you do so.

Constraints

Node specifications can be changed only for clusters that have at least two nodes.

Change Impact

Before changing a cluster's node specifications, it is essential to assess the potential impacts and review operational recommendations. This enables proper scheduling of the change, minimizing service interruptions.

  • Impact on cluster throughput

    Taking nodes offline one at a time usually does not interrupt services. However, jobs that are running on these will be stopped, causing the cluster throughput to decrease. To minimize this impact, perform this operation when the Logstash cluster has no ongoing tasks or after temporarily suspending all its tasks.

  • Characteristics of this process

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

Change Duration

The following formulas can be used to estimate how long the node specifications change will take:

Change duration (min) = 10 (min) x Number of nodes

where, 10 minutes is the duration per node. It is an empirical value.

Changing Node Specifications

  1. Log in to the CSS management console.
  2. In the navigation pane on the left, choose Clusters > Logstash.
  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. Select the Scale Cluster tab, and click Change specifications to set parameters.
    Table 1 Changing node specifications

    Parameter

    Description

    Action

    Select Change specifications.

    Resources

    Shows the change of resources for this operation.

    Nodes

    Configure the changes you want to make.

    1. Select Logstash Nodes in the Node Type column.
    2. In the Node Specifications column, select a new node flavor.
    Figure 2 Changing cluster specifications
  5. Click Next.
  6. Confirm the information and click Submit.
  7. In the dialog box that is displayed, choose whether to select Cluster status check, and click OK to start the specifications change.

    Cluster status check: The cluster status is checked by default before a node specifications change. The specifications of nodes are changed one by one to ensure success and data security. If the cluster is overloaded and services are faulty, the request for a node specifications change may fail to be delivered. In this case, you can disable cluster status check. Note that if you ignore cluster status check before the node specifications change, the cluster may become faulty and services may be interrupted without your knowledge. Exercise caution.

  8. Click Back to Cluster List to go back to the Clusters page. The Cluster Status is Configuration modified. When Cluster Status changes to Available, the cluster node specifications have been successfully changed.