Help Center/ Cloud Search Service_KooSearch/ User Guide/ Upgrading a KooSearch Service
Updated on 2025-08-14 GMT+08:00
View PDF
Share

Upgrading a KooSearch Service

This task updates kernel patches for KooSearch clusters.

Scenarios

How It Works

Cluster nodes are upgraded one at a time. During the upgrade, you remove a node from a cluster, change the node's OS image, then mount the node's original NIC port back to reuse its old IP address. Then you initialize the node to start its processes. After this node's information is updated, you proceed to another node and repeat these steps. During the upgrade, nodes are removed and then brought back one at time, which may cause service interruptions. Therefore, perform the upgrade during off-peak hours.

Upgrade Process

  1. Perform the pre-upgrade check: Pre-Upgrade Check.

    The pre-upgrade check is mostly automated. A few of the items need to be checked manually.

  2. Create an upgrade task and start the upgrade: Creating an Upgrade Task.

Constraints

  • A maximum of 20 clusters can be upgraded simultaneously. You are advised to perform the upgrade during off-peak hours.
  • Clusters that have ongoing tasks cannot be upgraded.
  • Once started, an upgrade task cannot be stopped until it succeeds or fails.

Pre-Upgrade Check

To ensure a successful upgrade, you must check the items listed in the following table before performing an upgrade.

Table 1 Pre-upgrade checklist

Check Item

Check Method

Description

Normal Status

Cluster status

System check

After an upgrade task is started, the system automatically checks the cluster status. If the cluster status is Available, the cluster can provide services properly.

The cluster status is Available.

Resources

System check

After an upgrade task is started, the system automatically checks resources. During the upgrade, the OS image is changed for each node. Make sure the required resources are available.

Sufficient resources are available.

Non-standard operations

Manual check

Check whether non-standard operations have been performed in the cluster. Non-standard operations refer to manual operations that are not recorded. These operations cannot be automatically passed on through the upgrade, for example, modification of system settings and return routes.

Changes caused by non-standard operations will be lost upon an upgrade. To avoid potential impact on your services, manually back up these changes before the upgrade starts.

Creating an Upgrade Task

  1. Go to the details page of a KooSearch service.
    1. Log in to the CSS management console.
    2. In the navigation pane on the left, choose KooSearch > KooSearch Document Q&A.
    3. Click the name of the target service to go to the service details page.
  2. Click the Upgrade tab.
  3. On the displayed page, set upgrade parameters.
    Table 2 Upgrade parameters

    Parameter

    Description

    Target Image

    Image of the target version. After you select an image, the image name and target version details are displayed below.

    The supported target versions are displayed in the Target Image drop-down list. If the target image cannot be selected, the possible causes are as follows:

    • The current cluster is already using the latest version.
    • The new image is not yet available in the current region.

    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.

    • 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"
  4. After setting the parameters, click Submit.
  5. Check the upgrade task in the task list. If the task status is Running, you can expand the task list and click View Progress to view the upgrade progress.

    If the task status is Failed, you can retry or terminate the task.

    • Retry the task: Click Retry in the Operation column.
    • Terminate the task: Click Terminate in the Operation column.

      After an upgrade task is terminated, contact technical support to handle failed items.