Help Center/ Cloud Search Service/ User Guide/ Using Logstash for Data Migration/ Scaling a Logstash Cluster/ Scaling Out a Logstash Cluster
Updated on 2024-10-12 GMT+08:00
View PDF
Share

Scaling Out a Logstash Cluster

If the workloads on the data plane of a Logstash cluster increase, you can scale out the cluster by increasing the quantity or capacity of its nodes.

Scenario

Table 1 Scaling out a Logstash cluster

Scenario

Description

Related Documents

Adding new nodes

Use this option if only the number of nodes of a cluster can be increased. Applicable scenarios:

  • To ensure continuous data availability, more nodes can be added to a Logstash cluster to enhance fault tolerance.
  • In the face of fast data growth, more nodes can be added to a Logstash cluster to increase data processing capacity.
  • More nodes can be added to a Logstash cluster to execute more complex data processing tasks, such as data enrichment and ETL.

Adding New Nodes

Changing node specifications

Use this option if only the node specifications of a cluster can be increased. Modification of node specifications is a rolling process, meaning nodes are stopped and restarted one at a time, not all at the same time. Applicable scenarios:

  • 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.

Changing Node Specifications

Prerequisites

  • The target cluster is available and has no tasks in progress.
  • CSS has sufficient resources to expand cluster capacity.

Constraints

  • Decreasing node specifications will decrease the cluster's data processing and storage capacities. Exercise caution.
  • Node specifications can be changed only for clusters that have at least two nodes.

Adding New Nodes

  1. Log in to the CSS management console.
  2. In the navigation pane on the left, choose Clusters > Logstash. The Clusters page is displayed.
  3. In the cluster list, select the target cluster, and choose More > Modify Configuration in the Operation column. The Modify Configuration page is displayed.
  4. On the Modify Configuration page, choose the Scale Cluster tab and click Scale out to set parameters.
    Table 2 Adding new nodes

    Parameter

    Description

    Action

    Select Scale out.

    Resources

    Shows the change of resources for this scale-out operation.

    Nodes

    Increase the number of nodes in the Nodes column.
    Figure 1 Adding more nodes
  5. Click Next.
  6. Confirm the information and click Submit.
  7. Click Back to Cluster List to switch to the Clusters page. The Task Status is Scaling out. When Cluster Status changes to Available, the cluster has been successfully scaled out.

Changing Node Specifications

  1. Log in to the CSS management console.
  2. In the navigation pane on the left, choose Clusters > Logstash. The Clusters page is displayed.
  3. In the cluster list, select the target cluster, and choose More > Modify Configuration in the Operation column. The Modify Configuration page is displayed.
  4. On the Modify Configuration page, click Change Specifications to set parameters.
    Table 3 Changing node specifications

    Parameter

    Description

    Action

    Select Change specifications.

    Resources

    Shows the change of resources for this operation.

    Nodes

    Select Data node in the Node Type column. The Logstash cluster has data nodes only. In the Node Specifications column, select new specifications.
    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 a cluster is overloaded and services are faulty, the request for a specifications change may fail to be delivered. In this case, you can disable cluster status check. Note that if you ignore the cluster status check before the specifications change, the cluster may become faulty and services may be interrupted without your knowledge. Exercise caution.

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