Tair (Redis® OSS-Compatible):Schedule temporary bandwidth upgrades for Tair and Redis

Background information

Scheduled bandwidth upgrades have the following features:

• Scheduled triggers: Automatically upgrade bandwidth at a preset date and time based on your business requirements.

• Automatic recovery: After the specified duration, bandwidth automatically returns to the original configuration, preventing unnecessary costs during off-peak hours.

• Cost optimization: Upgrading bandwidth only when needed significantly reduces operational costs while maintaining service quality.

• Streamlined operation: Configure bandwidth upgrades in just a few steps through a user-friendly interface.

The following table compares the features and use cases of the three bandwidth upgrade methods supported by Tair and Redis.

Prerequisites

You must create a RAM role for OOS to access your Tair instances. For more information, see Set a RAM role for OOS and grant permissions.

• You can grant the AliyunKvstoreFullAccess system policy to the RAM role. This allows the RAM role to manage all Tair resources.

• Alternatively, create a custom policy with the minimum required permissions for this task. This policy must allow OOS to call the DescribeInstances and EnableAdditionalBandwidth API operations for Tair.

  The following is a sample RAM role policy:

  {
      "Version": "1",
      "Statement": [
          {
              "Effect": "Allow",
              "Action": [
                  "kvstore:DescribeInstances",
                  "kvstore:EnableAdditionalBandwidth"
              ],
              "Resource": "*"
          }
      ]
  }

Procedure

1. Go to the OOS console.

2. In the left-side navigation pane, choose Automated Task > Common O&M Tasks.

3. Select Temporary Bandwidth Upgrade and click Create.

4. Configure the automated task.

   Note

   This topic describes only the key parameters. For information about other parameters, see CloudOps Orchestration Service.

   Select resource type

   Select Redis instance.

   Parameter settings

   1. Select a Scheduled Task Type.

      In this example, Executed Periodically is selected. The task is configured to run at 11:00 every day, between a specified start and end date.

   2. Set the Additional Bandwidth in MB/s.

      • For a standard architecture instance, you do not need to specify a data shard ID.

      • If the instance uses a cluster or read/write splitting architecture, the default value for the data shard ID is ALL. This means the specified bandwidth is added to each shard or node. The total bandwidth increase is: Additional Bandwidth × Number of shards (or nodes).

        To increase bandwidth for specific shards, enter their comma-separated IDs. You must also provide a corresponding bandwidth array with values listed in the same order.

   3. Set the Duration of Bandwidth Upgrade in hours.

      The minimum duration is 1 hour. After the duration ends, the instance bandwidth is restored to its original configuration.

   4. For Permissions, select the RAM role that you created in the Prerequisites section.

   Select instances

   Select the region where your instance is located, and then select the target instance.

   Control options (optional)

   You can keep the default settings on this tab.

   Execution settings (optional)

   You can keep the default settings on this tab.

5. Click Create, and then click OK in the dialog box that appears.

   An Execution Status of In Effect means the task will run automatically based on the Set Scheduled Task.

   On the task details page, you can view historical executions, upcoming executions, and Execution Logs.

References

ACS-Redis-ScheduleToUpgradeInstanceBandwidth template information