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/getting_started/creating_a_dcs_instance.rst

22 KiB
Raw Permalink Blame History

original_name

en-us_topic_0054235810.html

Creating a DCS Instance

Scenario

DCS can be used only after DCS instances are created. DCS supports three types of DCS instances: single-node, master/standby, and Proxy Cluster.

Important

DCS does not provide built-in encryption. Encrypt any sensitive data before transmitting or storing it. The purpose, scope, processing method, and time limits of data processed by DCS must comply with local laws and regulations.

Prerequisites

  • The VPC where the DCS instance to be created is available. Security groups and subnets have been configured for the VPC.
  • For more information on how to create VPCs, security groups, and subnets, see Setting Up Environments <en-us_topic_0077665192> or the Virtual Private Cloud User Guide.

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. Click Create DCS Instance.

  5. Specify DCS instance parameters, such as the name, AZ, VPC, security group, and subnet. The following table describes the parameters.

    Table 1 DCS instance parameters
    Parameter Description
    Region Region in which DCS is located. To select a different region, use the region selector at the upper left of the main menu bar.
    Cache Engine Cache engine used. Currently supported: Redis.
    Version Currently, only Redis 3.0 is supported.
    Instance Type

    Type of the DCS instance being created.

    Single-node, master/standby, and Proxy Cluster types are supported.
    AZ AZ in which the new DCS instance resides. If the instance type is master/standby or Proxy Cluster, this parameter is displayed as Master AZ.
    Standby AZ

    Standby AZ in which the new DCS instance resides.

    If the instance type is master/standby or Proxy Cluster, Standby AZ is displayed. Select a standby AZ for the standby node of the instance.
    Instance Specification

    Total memory of the new DCS instance.

    • 2, 4, 8, 16, 32, or 64 GB if the DCS instance is in single-node or master/standby mode
    • 64, 128, 256 or 512 GB if the DCS instance is in Proxy Cluster mode

    When creating a DCS instance on the DCS console, available free memory is listed below the Instance Specification field. If you need more memory, click Increase quota below the Instance Specification field and contact customer service.
    VPC Select a created VPC, subnet, and specify the IP address.
    Security Group

    Security group that controls access to the new DCS instance.

    A security group is a set of access control rules that implements access control for mutually trusted ECSs with the same security protection requirements in the same VPC.
    Password

    Password required for accessing the new DCS instance.

    NOTE:

    For security purposes, the system prompts you to enter an instance-specific password when you are accessing the DCS instance. Keep your instance password secure and change it periodically.

    Passwords cannot be left unspecified and must:

    • Consist of 8 to 32 characters.
    • Contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters (\`~!@#$^&*()-_=+\\|{}:,<.>/?).
    More Settings
    Name

    Name of the new DCS instance.

    A DCS instance name cannot be left unspecified and must:

    • Consist of 4 to 64 characters.
    • Consist of only letters, digits, hyphens (-), and underscores (_).
    • Start with an uppercase or lowercase letter.
    Description Description of the new DCS instance.
    Auto Backup Data backup policy. This parameter is displayed only when the instance type is master/standby or Proxy Cluster. For more information on how to configure a backup policy, see Configuring a Backup Policy <en-us_topic_0062866097>.
    Maintenance

    Time range for any scheduled maintenance activities to occur for cache nodes of this DCS instance.

    Values:

    • 02:00-06:00
    • 06:00-10:00
    • 10:00-14:00
    • 14:00-18:00
    • 18:00-22:00
    • 22:00-02:00

  6. Click Buy Now.

    The displayed page shows the instance information you have specified.

  7. Confirm the instance information and click Submit.

  8. After the new DCS instance has been created, return to the Cache Manager page to view and manage your DCS instances.

    It takes 5 to 15 minutes to create a DCS instance. However, it will take up to approximately 30 minutes if the DCS instance is in Proxy Cluster mode.

    After a DCS instance has been successfully created, it enters the Running state by default.

    Note

    • If the new DCS instance failed to be created, delete the unsuccessful instance creation task by following the procedure in Deleting Instance Creation Tasks That Have Failed to Run <en-us_topic_0054235819>. Then, create the DCS instance again. If the DCS instance still fails to be created, contact customer service.
    • There is the management plane and the tenant plane. The tenant plane is also called the pod zone. During the creation of a DCS instance, a VM is created in the pod zone. If the instance creation fails, the instance status changes to Faulty, and the error message "Failed to connect to the instance. Network exceptions may have occurred in the pod zone." is displayed, indicating that the management plane cannot be connected to the tenant plane.