Help Center/ Cloud Search Service/ User Guide/ Using Logstash for Data Migration/ Scaling a Logstash Cluster/ Scaling In a Logstash Cluster
Updated on 2025-01-23 GMT+08:00
View PDF
Share

Scaling In a Logstash Cluster

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.

Prerequisites

The cluster is in the Available state and has no ongoing tasks.

Constraints

  • To reduce the impact on services, you are advised to perform scale-in during off-peak hours.
  • In a cross-AZ cluster, the difference between the numbers of the same type nodes in different AZs cannot exceed 1.

Reducing the Nodes of a Logstash Cluster

  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 in to set parameters.
    Table 1 Reducing nodes randomly

    Parameter

    Description

    Action

    Select Scale in.

    Resources

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

    Agency

    When a node is deleted, NICs are released. This means you need to have VPC permissions. Select an IAM agency to grant the current account the permission to access and use VPC.

    • This parameter is available only when the new IAM plane is connected.
    • If you are configuring an agency for the first time, click Automatically Create IAM Agency to create css-upgrade-agency.
    • If there is an IAM agency automatically created earlier, you can click One-click authorization to have the permissions associated with the VPC Administrator role or the VPC FullAccess system policy deleted automatically, and have the following custom policies added automatically instead to implement more refined permissions control. 
      "vpc:subnets:get",
"vpc:ports:*"
    • To use Automatically Create IAM Agency and One-click authorization, the following minimum permissions are required: 
      "iam:agencies:listAgencies",
"iam:roles:listRoles",
"iam:agencies:getAgency",
"iam:agencies:createAgency",
"iam:permissions:listRolesForAgency",
"iam:permissions:grantRoleToAgency",
"iam:permissions:listRolesForAgencyOnProject",
"iam:permissions:revokeRoleFromAgency",
"iam:roles:createRole"
    • To use an IAM agency, the following minimum permissions are required: 
      "iam:agencies:listAgencies",
"iam:agencies:getAgency",
"iam:permissions:listRolesForAgencyOnProject",
"iam:permissions:listRolesForAgency"

    Nodes

    Reduce the number of nodes in the Nodes column.
    Figure 1 Reducing 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 in. When Cluster Status changes to Available, the cluster has been successfully scaled in.