All Products
Search
Document Center

ApsaraDB for Redis:Enable bandwidth auto scaling

Last Updated:Feb 27, 2024

When your business is facing an unexpected or anticipated surge in traffic, you can use the bandwidth auto scaling feature provided by ApsaraDB for Redis. This feature continuously monitors the average bandwidth usage of an instance in real time and automatically scales the instance bandwidth based on the bandwidth usage. It enables you to easily handle various traffic spikes, allowing you to focus on business improvement.

Prerequisites

  • The instance is an ApsaraDB for Redis Community Edition instance or a Tair DRAM-based instance.

  • The instance uses local disks.

Common scenarios

The bandwidth of an instance varies based on the instance type. If the bandwidth in use reaches the allocated bandwidth, network congestion may occur and instance performance may deteriorate. To prevent these situations, you can enable the bandwidth auto scaling feature. A bandwidth adjustment helps you increase bandwidth at a lower cost than an instance specification change and can help prevent transient connections.

Note

If the instance is a Community Edition instance that requires a sharp bandwidth increase, we recommend that you change the instance into an Enhanced Edition (Tair) instance. This is because a Tair instance can support a bandwidth of 96 Mbit/s or more.

Scenario

Description

Handle traffic spikes

You can adjust the bandwidth of the instance to handle traffic spikes during promotional events such as a flash sale. After these events end, you can decrease the bandwidth of the instance to reduce costs.

Mitigate impacts on your business

If a large number of read and write operations are performed on large keys within a short period of time, you must temporarily increase the bandwidth of the instance to mitigate impacts on your business and reserve time to process these operations.

Deal with skewed requests at low costs

If your instance uses the cluster or read/write splitting architecture, specific data shards or read replicas of the instance are more frequently accessed than others. As a result, the bandwidth consumption of these data shards or read replicas frequently reaches the allocated bandwidths. However, the usage of the bandwidths that are allocated to other data shards or read replicas is low.

After you enable the bandwidth auto scaling feature, the system identifies the data shards or read replicas whose allocated bandwidths are insufficient and increases the bandwidths for them. You do not need to manually increase the bandwidth or change the configurations of the instance to which these data shards or read replicas belong. This reduces costs and facilitates O&M.

Bandwidth scaling process

After you enable the bandwidth auto scaling feature, the system performs the following operations based on the auto scaling policy and observation window that you configure. The increment or decrement is calculated by the system.

  • If the bandwidth increase threshold of an instance is reached, the system increases the bandwidth and continues to monitor bandwidth usage. If the threshold is reached again, the system increases the bandwidth again. The bandwidth can be increased up to three times the default bandwidth of the instance type. If you want to increase this bandwidth limit, you can upgrade the specifications of your instance and then adjust the bandwidth.

  • If the bandwidth decrease threshold of an instance is reached, the system decreases the bandwidth and continues to monitor bandwidth usage. If the threshold is reached again, the system decreases the bandwidth again. The bandwidth can be decreased to the default bandwidth of the instance type.

Note
  • If your instance uses the cluster or read/write splitting architecture, the system monitors the bandwidth usage of data shards and read replicas and increases the bandwidth only for the data shards or read replicas whose allocated bandwidths are insufficient.

  • If you enable the subscription service, you are notified of every increase or decrease by the notification method that you select, such as email. For more information about how to enable the subscription service, see the "Procedure" section in this topic.

  • To ensure that DAS can access resources of your instance, the system authorizes DAS to assume the AliyunServiceRoleForDAS role after you enable this feature.

Limits

  • If an instance has unexpired bandwidth plans, you cannot enable bandwidth auto scaling for the instance. In this case, you must unsubscribe from the bandwidth plans. For more information, see Refund management.

  • The bandwidth of an instance can be increased to up to three times the bandwidth that is provided for the instance type. For example, the default bandwidth of a 2 GB DRAM-based master-replica instance is 96 MB/s. In this case, the bandwidth of the instance can be increased to up to 288 MB/s.

    To further increase the bandwidth of the instance, you can change the instance configurations or instance architecture, for example, from the standard architecture to the cluster architecture. For more information, see Overview.

  • We recommend that you do not manually adjust the instance bandwidth and enable bandwidth auto scaling for the instance at the same time.

    If these operations are performed at the same time, bandwidth auto scaling takes precedence. When the bandwidth is scaled back, the instance is scaled back to the default bandwidth of the instance type.

  • If you perform one of the following operations, bandwidth auto scaling is disabled for your instance. You must re-enable this feature for the instance based on your needs.

    Operation

    Exception

    Upgrade the major version

    N/A

    Change the configurations of an instance

    If the instance uses the standard architecture, the bandwidth settings remain valid after you change the configurations of the instance.

    Migrate an instance across zones

    If the instance uses the standard architecture, the bandwidth settings remain valid.

Billing

You are charged per hour based on the amount and usage duration of the extra bandwidth that you purchase. The fees vary based on the region that you select. For more information, see Billable items.

Note

You are not charged for the default bandwidth that is provided for the instance type. You are charged only for the extra bandwidth that you purchase.

Procedure

  1. Log on to the ApsaraDB for Redis console and go to the Instances page. In the top navigation bar, select the region in which the instance that you want to manage resides. Then, find the instance and click the instance ID.

  2. In the Basic Information section, turn on Bandwidth Auto Scaling.

    Note

    The first time you log on to the DAS console, follow the instructions to grant permissions to your account.

  3. In the DAS console, configure the policy for bandwidth auto scaling and event subscription.

    1. Set the parameters that are described in the following table to configure the policy for bandwidth auto scaling.

      Section/Tab

      Parameter

      Description

      Automatic Bandwidth Upgrade

      Automatic Bandwidth Upgrade

      Select the check box to enable the feature.

      Average Bandwidth Usage

      Select the threshold of average bandwidth usage for triggering an automatic scale-up. Valid values: 50% to 95%.

      Note
      • The system compares the bandwidth usage of inbound traffic and that of outbound traffic, and takes the larger value as the average bandwidth usage.

      • The bandwidth of an instance can be increased to up to three times the default bandwidth of the instance type. You can also view the message about this limit in the panel.

      Observation Window

      Select the length of the observation window. Unit: minutes.

      For example, you can set Average Bandwidth Usage to 70% and Observation Window to 15 minutes. If the average bandwidth usage is greater than or equal to 70% in this 15-minute observation window, the system increases the bandwidth. The increment is automatically calculated, and the bandwidth can be increased to up to three times the default bandwidth of the instance type. If the average bandwidth usage is less than or equal to 30%, the system decreases the bandwidth. The decrement is automatically calculated, and the bandwidth can be decreased to the default bandwidth of the instance type.

      Automatic Bandwidth Downgrade

      Automatic Bandwidth Downgrade

      Select the check box to enable the feature. Before you enable this feature, make sure that the Automatic Bandwidth Upgrade feature is enabled.

      Average Bandwidth Usage

      Select the threshold of average bandwidth usage for triggering an automatic scale-down. Valid values: 10% to 30%.

      Note

      The system compares the bandwidth usage of inbound traffic and that of outbound traffic, and takes the smaller value as the average bandwidth usage.

    2. Optional: Click the Event Subscription Settings tab. On the Event Subscription Settings tab, configure the parameters that are described in the following table.

      Parameter

      Description

      Enable Subscription Service

      Turn on Enable Subscription Service to enable the feature. If an event of the specified level or a higher level occurs, DAS uses the specified method such as email to send you a notification. This ensures that you are notified when events occur on your instance.

      Urgency

      Select the lowest level of events for which DAS sends notifications. If an event of the specified level or a higher level occurs, DAS sends a notification. Valid values:

      • Critical: events that affect the operation of databases.

      • Warning: events that may affect the operation of databases.

      • Optimize: events about optimization suggestions that are generated based on the status of your databases.

      • Notification: basic events and events related to performance snapshots.

      Note

      To subscribe to bandwidth auto scaling events, select the Notification level.

      Select Contacts/Contact Groups

      Select contacts or contact groups in the Existing Contacts/Contact Groups section and click the 向右箭头 icon to move them to the Selected Contacts/Contact Groups section.

      Note

      If no contacts or contact groups are available, you must create a contact or contact group. For more information, see Manage alert contacts.

      Notification Method

      Select a notification method. You can select one or more methods. We recommend that you select at least SMS to ensure timeliness.

      Notification Language

      Select a notification language. Valid values: Chinese and English.

      Minimum Notification Interval

      Select the minimum interval between two notifications about the same event. For example, you can set the interval to 5 minutes. In this case, if the event occurs again after you receive the first notification about the event, you are notified again 5 minutes later.

  4. Click OK.

Result

In the ApsaraDB for Redis console, Bandwidth Auto Scaling is turned on.