ahmet.yildirim/distributed-cache-service
1
0
Fork 0
forked from docs/distributed-cache-service
Code Issues Pull Requests Packages Projects Releases Wiki Activity
distributed-cache-service/umn/source/operation_guide/modifying_dcs_instance_specifications.rst

3.3 KiB
Raw Blame History

original_name

en-us_topic_0063519673.html

Modifying DCS Instance Specifications

Scenario

On the DCS console, you can modify a DCS Redis instance to the desired specification.

Important

  • After you change the specifications of a Proxy Cluster DCS instance, you cannot restore the files backed up before the modification. You are advised to back up your data as soon as possible after changing the specifications.
  • It takes 5 to 30 minutes to change the specifications of single-node or master/standby DCS instances. Changing the specifications of a Proxy Cluster DCS instance takes a longer time because data must be redistributed in the cluster. During the specification modification, services are interrupted for seconds. You are advised to modify the specifications during off-peak hours.
  • Normally during the specification modification, single-node, master/standby, and Proxy Cluster DCS instances can be read from and written into. However, writing data into single-node or master/standby instances may be temporarily unsupported until the specification modification is completed.

Prerequisites

The DCS instance you want to change the specification for is in the Running state.

Procedure

  1. Log in to the management console.

  2. Click image1 in the upper left corner of the management console and select a region.

  3. Click Service List, and choose Database > Distributed Cache Service to launch the DCS console.

  4. In the navigation pane, choose Cache Manager.

  5. Choose More > Modify Specifications in the same row as the DCS instance.

  6. On the Modify Specifications page, select the desired specification.

    The maximum storage space is 64 GB for single-node and master/standby instances, and 512 GB for Proxy Cluster instances.

  7. Click Next.

  8. Click Submit.

    It takes 5 to 30 minutes to scale up a DCS instance. After scale-up is successful, the DCS instance enters the Running state.

    The Background Tasks page then appears. On this page, you can view the scale-up status. For more information, see Managing Background Tasks <dcs-en-ug-180312009>.

    Note

    • If the specification modification of a single-node DCS instance fails, the instance is temporarily unavailable for use. The specification remains unchanged. Some management operations (such as parameter configuration and specification modification) are temporarily not supported. After the specification modification is completed in the backend, the instance changes to the new specification and becomes available for use again.
    • If the specification modification of a master/standby or Proxy Cluster DCS instance fails, the instance is still available for use with its original specifications. Some management operations (such as parameter configuration, backup, restoration, and specification modification) are temporarily not supported. Remember not to read or write more data than allowed by the original specifications; otherwise, data loss may occur.
    • After the specification modification is successful, the new specification of the instance takes effect.