检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
The migration task uses a tenant IP address (Migration ECS displayed on the Basic Information page of the task). If the target Redis has an IP whitelist, this IP address must be added to the whitelist.
The migration task uses a tenant IP address (Migration ECS displayed on the Basic Information page of the task). If the target Redis has an IP whitelist, this IP address must be added to the whitelist.
The online migration task uses a tenant IP address (Migration ECS displayed on the Basic Information page of the task.) If a whitelist is configured for the source or target instance, add the migration IP address to the whitelist or disable the whitelist.
The online migration task uses a tenant IP address (Migration ECS displayed on the Basic Information page of the task.) If a whitelist is configured for the source or target instance, add the migration IP address to the whitelist or disable the whitelist.
DCS Metrics Introduction This section describes DCS metrics reported to Cloud Eye as well as their namespaces and dimensions. You can use the Cloud Eye console or call APIs to query the DCS metrics and alarms. Different types of instances are monitored on different dimensions. Table
Ranking with DCS Overview Ranking is a function commonly used on web pages and apps. It is implemented by listing key-values in descending order. However, a huge number of concurrent operation and query requests can result in a performance bottleneck, significantly increasing latency
Restarting DCS Instances or Clearing DCS Instance Data Function This API is used to restart a running DCS instance. Data clearance operations cannot be undone on DCS Redis 4.0 and later instances. Calling Method For details, see Calling APIs. URI PUT /v2/{project_id}/instances/status
Restarting DCS Instances or Clearing DCS Instance Data Function This API is used to restart a running DCS instance. Data clearance operations cannot be undone on DCS Redis 4.0 and 5.0 instances. URI PUT /v1.0/{project_id}/instances/status Table 1 describes the parameter. Table 1 Parameter
Restoring DCS Instances This section describes how to restore instances on the DCS console. This function helps restore instances deleted by mistake. To migrate backup data to other DCS instances, see Backup Import Between DCS Redis Instances. Notes and Constraints You can enable
Viewing DCS Metrics The Cloud Eye service monitors the running performance your DCS instances. Procedure Log in to the DCS console. Click in the upper left corner of the console and select the region where your instance is located. In the navigation pane, choose Cache Manager. Click
Process of Using DCS How to Manage DCS Instances You can access Distributed Cache Service (DCS) from the web-based management console or by using RESTful application programming interfaces (APIs) through HTTPS requests. Using the console You can sign up and log in to the console,
Restarting a DCS Instance To recover an instance in cases such as high memory fragmentation ratio or fault occurrence, try restarting the instance on the DCS console. DCS instances can be restarted in batches. Notes and Constraints The DCS instances must be in the Running or Faulty
Deleting a DCS Instance On the DCS console, you can delete one or multiple DCS instances at a time. You can also delete all instance creation tasks that have failed to run. Notes and Constraints The DCS instances exist, and must be in the Running, Faulty, or Stopped state. Deleting
Common DCS Metrics This section describes common Redis metrics. Table 1 Common metrics Metric Description CPU Usage This metric indicates the maximum value in each measurement period (minute-level: every minute; second-level: every 5 seconds). For a single-node or master/standby instance
DCS Instance Types Single-Node Redis Master/Standby Redis Proxy Cluster Redis Redis Cluster Read/Write Splitting Redis Comparing DCS Redis Instance Types Single-Node Memcached (Discontinued) Master/Standby Memcached (Discontinued)
DCS Instance Specifications Redis 4.0/5.0/6.0/7.0 Redis 6.0 Enterprise Edition Redis 3.0 Instance Specifications (Discontinued) Memcached Instance Specifications (Discontinued)
What Is DCS? Huawei Cloud Distributed Cache Service (DCS) is an online, distributed, fast in-memory cache service compatible with Redis. It is reliable, scalable, usable out of the box, and easy to manage, meeting your requirements for high read/write performance and fast data access
Auto-renewing a DCS Instance Auto-renewal is easier and prevents DCS instances from being automatically deleted if you forget to manually renew them. The auto-renewal rules are as follows: The first auto-renewal date and billing period are calculated based on the expiration date of
DCS Best Practices This section summarizes best practices of Distributed Cache Service (DCS) in common scenarios. Each practice is given a description and procedure. Table 1 DCS best practices Best Practice Description Serializing Access to Frequently Accessed Resources Describes
Suggestions on Using DCS Service Usage Principle Description Remarks Deploy services nearby to reduce latency. If your service and DCS instance are deployed far from each other (not in the same region) or with a high latency (connected through public networks), the read/write performance