Viewing and Modifying Basic Settings of a DCS Instance

Viewing and Modifying Basic Information of a DCS Instance

1. Log in to the DCS console.
2. Click in the upper left corner of the management console and select the region where your instance is located.
3. In the navigation pane, choose Cache Manager.
4. Search for DCS instances using any of the following methods:
   • Search by keyword.

     Enter a keyword to search.

   • Select attributes and enter their keywords to search.

     Currently, you can search by name, specification, ID, IP address, AZ, status, instance type, and cache engine.

     For example, click the search box, choose Cache Engine, and then choose Redis 3.0, Redis 4.0, Redis 5.0, or Redis 6.0.

   For more information on how to search, click the question mark to the right of the search box.

5. Click the name of the DCS instance to display more details about the DCS instance. Table 1 describes the parameters.

   Table 1 Parameters on the Basic Information page of a DCS instance

   Section	Parameter	Description
   Instance Details	Name	Name of the chosen instance. To modify the instance name, click .
   	Status	State of the chosen instance.
   	ID	ID of the chosen instance.
   	Cache Engine	Cache version of DCS. For example, Basic | Redis 4.0. The cache version is fixed once the instance is created. To use another version, create an instance again and migrate the data.
   	Minor Version	Minor version of the instance. DCS optimizes functions and fixes vulnerabilities in minor upgrades. Clicking Upgrade to obtain the latest version. NOTE: By default, a minor version cannot be viewed. To view or upgrade it, contact customer service to enable a whitelist. Perform instance upgrades during off-peak hours. Otherwise, upgrades may fail when the instance memory or CPU usage exceeds 90% or write traffic bursts. In such cases, try again during off-peak hours. The instance is upgraded by migrating nodes. During the migration, latency will increase. A migrating shard will become read-only for 1 minute and intermittently disconnected. Ensure that the client can reconnect and handle exceptions. For a Redis Cluster instance, ensure that the client can properly process the MOVED and ASK commands. Otherwise, requests will fail. This parameter is displayed only for basic edition DCS Redis 4.0 and later instances. Professional edition instances do not support minor version upgrades. If the minor version of the instance is already the latest, you cannot upgrade it. Upgrading the minor does not affect the instance connection addresses, password, whitelist, or monitoring and alarms.
   	Proxy Version	Proxy version of a DCS instance. This parameter is displayed only for Proxy Cluster and read/write splitting instances. DCS optimizes functions and fixes vulnerabilities in proxy upgrades. Clicking Upgrade to obtain the latest version. NOTE: By default, a proxy version cannot be viewed. To view or upgrade it, contact customer service to enable a whitelist. The upgrading instance will be intermittently disconnected. Ensure that the client can reconnect and handle exceptions. Perform the upgrade during off-peak hours. If the proxy version of the instance is already the latest, you cannot upgrade it. Upgrading the proxy does not affect the instance connection addresses, password, whitelist, or monitoring and alarms.
   	Instance Type	Type of the selected instance. Currently, supported types include single-node, master/standby, Proxy Cluster, read/write splitting, and Redis Cluster. To change the instance type, see Modifying DCS Instance Specifications about the supported instance types, changing notes and procedure.
   	Cache Size	Specification of the chosen instance. To change the instance specification, see Modifying DCS Instance Specifications about the changing notes and procedure.
   	Bandwidth	Bandwidth of the DCS instance. You can click Adjust Bandwidth to adjust the instance bandwidth. For details, see Adjusting DCS Instance Bandwidth.
   	Used/Available Memory (MB)	The used memory space and maximum available memory space of the chosen instance. The used memory space includes: Size of data stored on the DCS instance Size of Redis-server buffers (including client buffer and repl-backlog) and internal data structures
   	CPU	CPU architecture of the chosen instance. This parameter is displayed only for DCS Redis instances. The CPU architecture is fixed once the instance is created.
   	Enterprise Project	Enterprise project to which the new instance belongs. Click to modify the enterprise project of the instance. Enterprise projects isolate resources, personnel, and finance. Modifying an enterprise project changes isolated objectives.
   	Maintenance	Time range for any scheduled maintenance activities on cache nodes of this DCS instance. To modify the window, click . Select a new window from the drop-down list and click to save, or to cancel. The modification takes effect immediately.
   	Description	Description of the chosen DCS instance. To modify the description, click .
   Connection	Password Protected	Yes: password-protected access; No: password-free access. To change the password access mode, see Configuring a Redis Password.
   	Connection Address	The domain name and port of the Redis instance to be accessed on a client within the VPC. You can click next to Connection Address to change the port. The connection address is fixed once the instance is created. NOTE: For a master/standby DCS Redis 4.0/5.0/6.0 instance, Connection Address indicates the domain name and port number of the master node, and Read-only Address indicates those of the standby node. When connecting to such an instance, you can use the domain name and port number of the master node or the standby node. For details, see the architecture of a master/standby instance. You can change the port only for a DCS Redis 4.0, 5.0, or 6.0 basic instance, but not for a DCS Redis 3.0, 6.0 professional, or Memcached instance.
   	IP Address	The IP address and port of the DCS instance to be accessed on a client within the VPC. To change the instance port, click . The IP address is fixed once the instance is created. The domain name address is recommended.
   	Public Access	Currently, public access can be enabled by default only for Redis 3.0 instances. To enable public access to a Redis 3.0 instance, see Public Access to a DCS Redis 3.0 Instance (Discontinued). Public access cannot be enabled for instances of other versions. To enable public access to a Redis 4.0, 5.0, or 6.0 instance, contact customer service to enable the public access whitelist. Then, see Enabling Public Access to Redis 4.0/5.0/6.0 and Obtaining the Access Addresses to enable public access and obtain the addresses. Memcached (discontinued) does not support public access.
   Network	AZ	Availability zone in which the instance nodes running the selected DCS instance reside. The AZ of standby nodes can be changed for a cluster multi-replica instance in a single AZ. For details, see Changing Cluster DCS Instances to be Across AZs. AZs cannot be changed in other scenarios.
   	VPC	VPC in which the chosen instance resides. The VPC is fixed once the instance is created.
   	Subnet	Subnet in which the chosen instance resides. The subnet is fixed once the instance is created.
   	Security Group	Security group that controls access to the chosen instance. To modify the security group, click . Select a new security group from the drop-down list and click to save, or to cancel. The modification takes effect immediately. Security group access control is supported only by DCS Redis 3.0, professional edition DCS Redis 6.0, and Memcached instances. Basic edition DCS for Redis 4.0/5.0/6.0 is based on VPC Endpoint, does not support security groups, and Configuring DCS Redis Access Whitelist is suggested. NOTE: Only the security groups that have been created can be selected from the drop-down list. If you need to create a security group, follow the procedure described in How Do I Configure a Security Group?
   Instance Topology	-	Hover over a node to view its metrics, or click the icon of a node to view its historical metrics. Single-node instances do not display the instance topology.
   Billing	Billing Mode	Billing mode of the instance. To change the billing mode, see Billing Mode Changes.
   	Created	Time at which the chosen instance started to be created.
   	Run	Time at which the instance was created.