diff --git a/docs/dcs/umn/ALL_META.TXT.json b/docs/dcs/umn/ALL_META.TXT.json index 0aa813e28..2fa3a6929 100644 --- a/docs/dcs/umn/ALL_META.TXT.json +++ b/docs/dcs/umn/ALL_META.TXT.json @@ -91,7 +91,7 @@ "node_id":"cachesinglenode.xml", "product_code":"dcs", "code":"5", - "des":"Single-node DCS Redis instances are available in versions 3.0/4.0/5.0/6.0.You cannot upgrade the Redis version for an instance. For example, a single-node DCS Redis 4.0 i", + "des":"A single-node DCS Redis instance has only one node and does not support data persistence. They are suitable for cache services that do not require data reliability.You ca", "doc_type":"usermanual", "kw":"Single-Node Redis,DCS Instance Types,User Guide", "search_title":"", @@ -112,7 +112,7 @@ "node_id":"cachemasterslave.xml", "product_code":"dcs", "code":"6", - "des":"This section describes master/standby DCS Redis instances. Redis versions available for master/standby DCS Redis instances include Redis 3.0, 4.0, 5.0, and 6.0.You cannot", + "des":"This section describes master/standby DCS Redis instances.You cannot upgrade the Redis version for an instance. For example, a master/standby DCS Redis 4.0 instance canno", "doc_type":"usermanual", "kw":"Master/Standby Redis,DCS Instance Types,User Guide", "search_title":"", @@ -3163,7 +3163,7 @@ "node_id":"dcs-faq-0730020.xml", "product_code":"dcs", "code":"154", - "des":"Yes. DCS for Redis 4.0 and 5.0 support Redis Clusters. DCS for Redis 3.0 supports Proxy Clusters.", + "des":"Yes. DCS for Redis 4.0 and later support Redis Clusters. DCS for Redis 3.0 supports Proxy Clusters.", "doc_type":"usermanual", "kw":"Does DCS for Redis Support Redis Clusters?,Redis Usage,User Guide", "search_title":"", @@ -3184,7 +3184,7 @@ "node_id":"dcs-faq-0730021.xml", "product_code":"dcs", "code":"155", - "des":"Cluster instances and master/standby DCS Redis 4.0/5.0/6.0 instances support Sentinels. Sentinels monitor the running status of both the master and standby nodes of a mas", + "des":"Cluster instances and master/standby DCS Redis 4.0 and later instances support Sentinels. Sentinels monitor the running status of both the master and standby nodes of a m", "doc_type":"usermanual", "kw":"Does DCS for Redis Support Sentinel?,Redis Usage,User Guide", "search_title":"", @@ -3310,7 +3310,7 @@ "node_id":"dcs-faq-0730029.xml", "product_code":"dcs", "code":"161", - "des":"Master/Standby and cluster DCS Redis instances can be deployed across availability zones (AZs).If instances nodes in an AZ are faulty, nodes in other AZs will not be affe", + "des":"Master/Standby and cluster DCS Redis instances can be deployed across availability zones (AZs).If instance nodes in an AZ are faulty, nodes in other AZs will not be affec", "doc_type":"usermanual", "kw":"Does DCS Support Cross-AZ Deployment?,Redis Usage,User Guide", "search_title":"", @@ -3457,7 +3457,7 @@ "node_id":"dcs-faq-0220330.xml", "product_code":"dcs", "code":"168", - "des":"After a single-node DCS instance is restarted, data in the instance is deleted.Master/standby and cluster instances (except single-replica clusters) support AOF persisten", + "des":"After a single-node DCS instance is restarted, data in the instance is deleted.Master/Standby and cluster instances (except single-replica clusters) support AOF persisten", "doc_type":"usermanual", "kw":"Will Cached Data Be Retained After an Instance Is Restarted?,Redis Usage,User Guide", "search_title":"", @@ -3919,7 +3919,7 @@ "node_id":"dcs-faq-0220721.xml", "product_code":"dcs", "code":"190", - "des":"Flow control is triggered when the traffic used by a Redis instance in a period exceeds the maximum bandwidth.For details about the maximum allowed bandwidth, see the \"As", + "des":"Flow control is triggered when the traffic used by a Redis instance in a period exceeds the maximum bandwidth.For details about the maximum bandwidth of an instance flavo", "doc_type":"usermanual", "kw":"Why Is Flow Control Triggered? How Do I Handle It?,Monitoring and Alarm,User Guide", "search_title":"", @@ -4024,7 +4024,7 @@ "node_id":"dcs-faq-210706001.xml", "product_code":"dcs", "code":"195", - "des":"AOF rewrites involve the following concepts:Rewrite window, which is currently 01:00 to 04:59Disk usage threshold, which is 50%AOF rewrites are triggered in the following", + "des":"AOF rewrites involve the following concepts:Rewrite window, which is currently 01:00 to 04:59Disk usage threshold, which is 50%Dataset memory, which is the percentage of ", "doc_type":"usermanual", "kw":"When Will AOF Rewrites Be Triggered?,Data Backup, Export, and Migration,User Guide", "search_title":"", diff --git a/docs/dcs/umn/CLASS.TXT.json b/docs/dcs/umn/CLASS.TXT.json index 5cee0ebf5..0e0126c02 100644 --- a/docs/dcs/umn/CLASS.TXT.json +++ b/docs/dcs/umn/CLASS.TXT.json @@ -36,7 +36,7 @@ "code":"4" }, { - "desc":"Single-node DCS Redis instances are available in versions 3.0/4.0/5.0/6.0.You cannot upgrade the Redis version for an instance. For example, a single-node DCS Redis 4.0 i", + "desc":"A single-node DCS Redis instance has only one node and does not support data persistence. They are suitable for cache services that do not require data reliability.You ca", "product_code":"dcs", "title":"Single-Node Redis", "uri":"CacheSingleNode.html", @@ -45,7 +45,7 @@ "code":"5" }, { - "desc":"This section describes master/standby DCS Redis instances. Redis versions available for master/standby DCS Redis instances include Redis 3.0, 4.0, 5.0, and 6.0.You cannot", + "desc":"This section describes master/standby DCS Redis instances.You cannot upgrade the Redis version for an instance. For example, a master/standby DCS Redis 4.0 instance canno", "product_code":"dcs", "title":"Master/Standby Redis", "uri":"CacheMasterSlave.html", @@ -1377,7 +1377,7 @@ "code":"153" }, { - "desc":"Yes. DCS for Redis 4.0 and 5.0 support Redis Clusters. DCS for Redis 3.0 supports Proxy Clusters.", + "desc":"Yes. DCS for Redis 4.0 and later support Redis Clusters. DCS for Redis 3.0 supports Proxy Clusters.", "product_code":"dcs", "title":"Does DCS for Redis Support Redis Clusters?", "uri":"dcs-faq-0730020.html", @@ -1386,7 +1386,7 @@ "code":"154" }, { - "desc":"Cluster instances and master/standby DCS Redis 4.0/5.0/6.0 instances support Sentinels. Sentinels monitor the running status of both the master and standby nodes of a mas", + "desc":"Cluster instances and master/standby DCS Redis 4.0 and later instances support Sentinels. Sentinels monitor the running status of both the master and standby nodes of a m", "product_code":"dcs", "title":"Does DCS for Redis Support Sentinel?", "uri":"dcs-faq-0730021.html", @@ -1440,7 +1440,7 @@ "code":"160" }, { - "desc":"Master/Standby and cluster DCS Redis instances can be deployed across availability zones (AZs).If instances nodes in an AZ are faulty, nodes in other AZs will not be affe", + "desc":"Master/Standby and cluster DCS Redis instances can be deployed across availability zones (AZs).If instance nodes in an AZ are faulty, nodes in other AZs will not be affec", "product_code":"dcs", "title":"Does DCS Support Cross-AZ Deployment?", "uri":"dcs-faq-0730029.html", @@ -1503,7 +1503,7 @@ "code":"167" }, { - "desc":"After a single-node DCS instance is restarted, data in the instance is deleted.Master/standby and cluster instances (except single-replica clusters) support AOF persisten", + "desc":"After a single-node DCS instance is restarted, data in the instance is deleted.Master/Standby and cluster instances (except single-replica clusters) support AOF persisten", "product_code":"dcs", "title":"Will Cached Data Be Retained After an Instance Is Restarted?", "uri":"dcs-faq-0220330.html", @@ -1701,7 +1701,7 @@ "code":"189" }, { - "desc":"Flow control is triggered when the traffic used by a Redis instance in a period exceeds the maximum bandwidth.For details about the maximum allowed bandwidth, see the \"As", + "desc":"Flow control is triggered when the traffic used by a Redis instance in a period exceeds the maximum bandwidth.For details about the maximum bandwidth of an instance flavo", "product_code":"dcs", "title":"Why Is Flow Control Triggered? How Do I Handle It?", "uri":"dcs-faq-0220721.html", @@ -1746,7 +1746,7 @@ "code":"194" }, { - "desc":"AOF rewrites involve the following concepts:Rewrite window, which is currently 01:00 to 04:59Disk usage threshold, which is 50%AOF rewrites are triggered in the following", + "desc":"AOF rewrites involve the following concepts:Rewrite window, which is currently 01:00 to 04:59Disk usage threshold, which is 50%Dataset memory, which is the percentage of ", "product_code":"dcs", "title":"When Will AOF Rewrites Be Triggered?", "uri":"dcs-faq-210706001.html", diff --git a/docs/dcs/umn/CacheCluster.html b/docs/dcs/umn/CacheCluster.html index 3fcc2db2c..baa9dfd44 100644 --- a/docs/dcs/umn/CacheCluster.html +++ b/docs/dcs/umn/CacheCluster.html @@ -5,10 +5,10 @@
-

Proxy Cluster DCS Redis 3.0 Instances

Proxy Cluster DCS Redis 3.0 instances are compatible with codis. The specifications range from 64 GB to 1024 GB, meeting requirements for millions of concurrent connections and massive data cache. Distributed data storage and access is implemented by DCS, without requiring development or maintenance.

+

Proxy Cluster DCS Redis 3.0 Instances

Proxy Cluster DCS Redis 3.0 instances are compatible with codis. The specifications range from 64 GB to 1024 GB, meeting requirements for millions of concurrent connections and massive data cache. Distributed data storage and access is implemented by DCS, without requiring development or maintenance.

Each Proxy Cluster instance consists of load balancers, proxies, cluster managers, and shards.

-
-
Table 1 Specifications of Proxy Cluster DCS Redis 3.0 instances

Total Memory

+
diff --git a/docs/dcs/umn/CacheMasterSlave.html b/docs/dcs/umn/CacheMasterSlave.html index 8657b7d61..945ed7e4b 100644 --- a/docs/dcs/umn/CacheMasterSlave.html +++ b/docs/dcs/umn/CacheMasterSlave.html @@ -1,7 +1,7 @@

Master/Standby Redis

-

This section describes master/standby DCS Redis instances. Redis versions available for master/standby DCS Redis instances include Redis 3.0, 4.0, 5.0, and 6.0.

+

This section describes master/standby DCS Redis instances.

You cannot upgrade the Redis version for an instance. For example, a master/standby DCS Redis 4.0 instance cannot be upgraded to a master/standby DCS Redis 5.0 instance. If your service requires the features of higher Redis versions, create a DCS Redis instance of a higher version and then migrate data from the old instance to the new one.

Features

Master/Standby DCS instances have higher availability and reliability than single-node DCS instances.

diff --git a/docs/dcs/umn/CacheSingleNode.html b/docs/dcs/umn/CacheSingleNode.html index 1a20291c4..287da6345 100644 --- a/docs/dcs/umn/CacheSingleNode.html +++ b/docs/dcs/umn/CacheSingleNode.html @@ -1,8 +1,8 @@

Single-Node Redis

-

Single-node DCS Redis instances are available in versions 3.0/4.0/5.0/6.0.

-

You cannot upgrade the Redis version for an instance. For example, a single-node DCS Redis 4.0 instance cannot be upgraded to a single-node DCS Redis 5.0 instance. If your service requires the features of higher Redis versions, create a DCS Redis instance of a higher version and then migrate data from the old instance to the new one.

+

A single-node DCS Redis instance has only one node and does not support data persistence. They are suitable for cache services that do not require data reliability.

+
  • You cannot upgrade the Redis version of an instance. For example, a single-node DCS instance cannot be upgraded from Redis 4.0 to Redis 5.0. If you need Redis features of later versions, create a DCS Redis instance of a later version and then migrate data from the earlier instance to the new one.
  • Single-node instances cannot ensure data persistence and do not support manual or scheduled data backup. Exercise caution before using them.

Features

  1. Low system overhead and high QPS

    Single-node instances do not support data synchronization or data persistence, reducing system overhead and supporting higher concurrency. QPS of single-node DCS Redis instances reaches up to 100,000.

  2. Process monitoring and automatic fault recovery

    With an HA monitoring mechanism, if a single-node DCS instance becomes faulty, a new process is started within 30 seconds to resume service provisioning.

    diff --git a/docs/dcs/umn/cache-instance-password.html b/docs/dcs/umn/cache-instance-password.html index 1a5d2d9bf..22280245b 100644 --- a/docs/dcs/umn/cache-instance-password.html +++ b/docs/dcs/umn/cache-instance-password.html @@ -9,7 +9,7 @@

Using Passwords Securely

  1. Hide the password when using redis-cli.

    If the -a <password> option is used in redis-cli in Linux, the password is prone to leakage because it is logged and kept in the history. You are advised not to use -a <password> when running commands in redis-cli. After connecting to Redis, run the auth command to complete authentication as shown in the following example:

    $ redis-cli -h 192.168.0.148 -p 6379
-redis 192.168.0.148:6379>auth yourPassword
+redis 192.168.0.148:6379>auth {yourPassword}
 OK
 redis 192.168.0.148:6379>
  2. Use interactive password authentication or switch between users with different permissions.

    If the script involves DCS instance access, use interactive password authentication. To enable automatic script execution, manage the script as another user and authorize execution using sudo.

    diff --git a/docs/dcs/umn/dcs-faq-0220330.html b/docs/dcs/umn/dcs-faq-0220330.html index 562958e6a..faeba5b4d 100644 --- a/docs/dcs/umn/dcs-faq-0220330.html +++ b/docs/dcs/umn/dcs-faq-0220330.html @@ -4,7 +4,7 @@

    Will Cached Data Be Retained After an Instance Is Restarted?

    After a single-node DCS instance is restarted, data in the instance is deleted.

    -

    Master/standby and cluster instances (except single-replica clusters) support AOF persistence by default. Data is retained after these instances are restarted.

    +

    Master/Standby and cluster instances (except single-replica clusters) support AOF persistence by default. Data is retained after these instances are restarted.

    If AOF persistence is disabled (appendonly is set to no), data is deleted after the instances are restarted.

    diff --git a/docs/dcs/umn/dcs-faq-0220721.html b/docs/dcs/umn/dcs-faq-0220721.html index 804913de0..7f47ef67b 100644 --- a/docs/dcs/umn/dcs-faq-0220721.html +++ b/docs/dcs/umn/dcs-faq-0220721.html @@ -2,7 +2,7 @@

    Why Is Flow Control Triggered? How Do I Handle It?

    Flow control is triggered when the traffic used by a Redis instance in a period exceeds the maximum bandwidth.

    -

    For details about the maximum allowed bandwidth, see the "Assured/Maximum Bandwidth" column of different instance types listed in DCS Instance Specifications.

    +

    For details about the maximum bandwidth of an instance flavor, see Instance Specifications, or refer to the page of creating an instance on the console.

    Even if the bandwidth usage is low, flow control may still be triggered. The real-time bandwidth usage is reported once in each reporting period. Flow controls are checked every second. The traffic may surge within seconds and then fall back between reporting periods. By the time the bandwidth usage is reported, it may have already restored to the normal level.

    For master/standby instances:

    diff --git a/docs/dcs/umn/dcs-faq-0427081.html b/docs/dcs/umn/dcs-faq-0427081.html index 16eda5dbf..d362408be 100644 --- a/docs/dcs/umn/dcs-faq-0427081.html +++ b/docs/dcs/umn/dcs-faq-0427081.html @@ -10,7 +10,8 @@

    Impact of AOF Persistence

    After AOF persistence is enabled, the Redis-Server process needs to record operations in the AOF file for data persistence.
    • If the disk or I/O of the underlying compute node is faulty, the latency may increase or a master/standby switchover may occur.
    • Redis-Server periodically rewrites the AOF. During a rewrite, the latency may be high for a short time. For details about the AOF rewriting rules, see When Will AOF Rewrites Be Triggered?
    -

    If DCS instances are used to accelerate applications, you are advised to disable persistence for higher performance and stability. Exercise caution when disabling persistence. Without persistence, cached data may be lost in extreme scenarios (for example, when both the master and standby nodes are faulty).

    +

    If DCS instances are used for application acceleration, you are advised to disable AOF persistence for higher performance and stability.

    +

    Exercise caution when disabling AOF persistence. After it is disabled, cached data may be lost in extreme scenarios, for example, when both the master and standby nodes are faulty.

    To disable AOF persistence, set parameter appendonly to no on the instance details page.

    diff --git a/docs/dcs/umn/dcs-faq-0513001.html b/docs/dcs/umn/dcs-faq-0513001.html index 5ea0624bf..44c7265ca 100644 --- a/docs/dcs/umn/dcs-faq-0513001.html +++ b/docs/dcs/umn/dcs-faq-0513001.html @@ -37,8 +37,8 @@
Table 1 Total memory, proxies, and shards of Proxy Cluster DCS Redis 3.0 instances

Total Memory

Proxies
-

Bandwidth usage = (Input flow + Output flow)/(2 x Maximum bandwidth) x 100%

-

According to the formula, the bandwidth usage counts in the input flow and output flow, which include the traffic for replication between the master and replicas. Therefore, the total traffic is greater than the normal service traffic.

+

Bandwidth usage = (Input flow + Output flow)/(2 x Maximum bandwidth) x 100%

+

According to the formula, the bandwidth usage counts in the input flow and output flow, which include the traffic for replication between the master and replicas. Therefore, the total bandwidth usage is larger than the normal service traffic, and may exceed 100%.

If the value of the Flow Control Times metric is larger than 0, the maximum bandwidth has been reached and flow control has been performed.

However, flow control decisions are made without considering the traffic for replication between the master and replicas. Therefore, sometimes the bandwidth usage exceeds 100% but the number of flow control times is 0.

diff --git a/docs/dcs/umn/dcs-faq-0730020.html b/docs/dcs/umn/dcs-faq-0730020.html index dc16b0c63..b58c44e37 100644 --- a/docs/dcs/umn/dcs-faq-0730020.html +++ b/docs/dcs/umn/dcs-faq-0730020.html @@ -1,7 +1,7 @@

Does DCS for Redis Support Redis Clusters?

-

Yes. DCS for Redis 4.0 and 5.0 support Redis Clusters. DCS for Redis 3.0 supports Proxy Clusters.

+

Yes. DCS for Redis 4.0 and later support Redis Clusters. DCS for Redis 3.0 supports Proxy Clusters.

diff --git a/docs/dcs/umn/dcs-faq-0730021.html b/docs/dcs/umn/dcs-faq-0730021.html index 43c3b87fc..080f5f82a 100644 --- a/docs/dcs/umn/dcs-faq-0730021.html +++ b/docs/dcs/umn/dcs-faq-0730021.html @@ -1,8 +1,8 @@

Does DCS for Redis Support Sentinel?

-

Cluster instances and master/standby DCS Redis 4.0/5.0/6.0 instances support Sentinels. Sentinels monitor the running status of both the master and standby nodes of a master/standby instance and each shard of a cluster instance. If the master node becomes faulty, a failover will be performed.

-

However, DCS for Redis 3.0 does not support Redis Sentinel. Instead, it uses keepalive to monitor master and replica nodes and to manage failovers.

+

Cluster instances and master/standby DCS Redis 4.0 and later instances support Sentinels. Sentinels monitor the running status of both the master and standby nodes of a master/standby instance and each shard of a cluster instance. If the master node becomes faulty, a failover will be performed.

+

DCS for Redis 3.0 does not support Redis Sentinel. Instead, it uses keepalive to monitor master and replica nodes and to manage failovers.

diff --git a/docs/dcs/umn/dcs-faq-0730025.html b/docs/dcs/umn/dcs-faq-0730025.html index b9501c41e..15f5dfc58 100644 --- a/docs/dcs/umn/dcs-faq-0730025.html +++ b/docs/dcs/umn/dcs-faq-0730025.html @@ -2,7 +2,7 @@

Why Is Redisson Distributed Lock Not Supported by DCS Proxy Cluster Redis 3.0 Instances?

Redisson implements lock acquisition and unlocking in the following process:

-
  1. Redisson lock acquisition and unlocking are implemented by running Lua scripts.
  2. During lock acquisition, the EXISTS, HSET, PEXPIRE, HEXISTS, HINCRBY, PEXPIRE, and PTTL commands must be executed in the Lua script.
  3. During unlocking, the EXISTS, PUBLISH, HEXISTS, PEXIPRE, and DEL commands must be executed in the Lua script.
+
  1. Redisson lock acquisition and unlocking are implemented by running Lua scripts.
  2. During lock acquisition, the EXISTS, HSET, PEXPIRE, HEXISTS, HINCRBY, PEXPIRE, and PTTL commands must be executed in the Lua script.
  3. During unlocking, the EXISTS, PUBLISH, HEXISTS, PEXPIRE, and DEL commands must be executed in the Lua script.

In a proxy-based cluster, the proxy processes PUBLISH and SUBSCRIBE commands and forwards requests to the Redis server. The PUBLISH command cannot be executed in the Lua script.

As a result, Proxy Cluster DCS Redis 3.0 instances do not support Redisson distributed locks. To use Redisson, resort to Redis 4.0 or 5.0 instead.

diff --git a/docs/dcs/umn/dcs-faq-0730029.html b/docs/dcs/umn/dcs-faq-0730029.html index 8b02e4d83..15728130e 100644 --- a/docs/dcs/umn/dcs-faq-0730029.html +++ b/docs/dcs/umn/dcs-faq-0730029.html @@ -2,7 +2,7 @@

Does DCS Support Cross-AZ Deployment?

Master/Standby and cluster DCS Redis instances can be deployed across availability zones (AZs).

-
  • If instances nodes in an AZ are faulty, nodes in other AZs will not be affected. The standby node automatically becomes the master node to continue to operate, ensuring disaster recovery (DR).
  • Cross-AZ deployment does not compromise the speed of data synchronization between the master and standby nodes.
+
  • If instance nodes in an AZ are faulty, nodes in other AZs will not be affected. The standby node automatically becomes the master node to continue to operate, ensuring disaster recovery (DR).
  • Cross-AZ deployment does not compromise the speed of data synchronization between the master and standby nodes.
diff --git a/docs/dcs/umn/dcs-faq-0730036.html b/docs/dcs/umn/dcs-faq-0730036.html index f1bab5102..f93c31b6d 100644 --- a/docs/dcs/umn/dcs-faq-0730036.html +++ b/docs/dcs/umn/dcs-faq-0730036.html @@ -5,7 +5,7 @@
  • Redis 3.0

    Data of a DCS Redis 3.0 instance cannot be cleared on the console, and can only be cleared by the FLUSHDB or FLUSHALL command in redis-cli.

    Run the FLUSHALL command to clear all the data in the instance.

    Run the FLUSHDB command to clear the data in the currently selected DB.

    -
  • Redis 4.0 and later

    To clear data of a DCS Redis 4.0 and later instance, you can run the FLUSHDB or FLUSHALL command in redis-cli, use the data clearing function on the DCS console, or run the FLUSHDB command on Web CLI.

    +
  • Redis 4.0 and later

    To clear data of a DCS Redis 4.0 and later instance, you can run the FLUSHDB or FLUSHALL command in redis-cli, use the data clearing function on the DCS console, or run the FLUSHDB command on Web CLI.

    To clear data of a Redis Cluster instance, run the FLUSHDB or FLUSHALL command on every shard of the instance. Otherwise, data may not be completely cleared.

    • Currently, only DCS Redis 4.0 and later instances support data clearing by using the DCS console and by running the FLUSHDB command on Web CLI.
    • When you run the FLUSHDB command on Web CLI, only one shard is cleared at a time. If there are multiple shards, connect to the master node of each shard and run the FLUSHDB command separately.
    • Redis Cluster data cannot be cleared by using Web CLI.
    diff --git a/docs/dcs/umn/dcs-faq-0730053.html b/docs/dcs/umn/dcs-faq-0730053.html index f15839e3f..c4eff65a7 100644 --- a/docs/dcs/umn/dcs-faq-0730053.html +++ b/docs/dcs/umn/dcs-faq-0730053.html @@ -6,8 +6,8 @@

    If your DCS instances were created a long time ago, the versions of these instances may not be advanced enough to support some new functions (such as backup and restoration). You can contact technical support to upgrade your DCS instances. After the upgrade, you can back up and restore your instances.

  • For single-node instances:

    Single-node instances do not support the backup function. You can use redis-cli to export RDB files. This operation depends on SYNC command.

    -
    • If the instance allows the SYNC command (such as a Redis 3.0 single-node instance), run the following command to export the instance data:

      redis-cli -h {source_redis_address} -p 6379 [-a password] --rdb {output.rdb}

      -
    • If the instance does not allow the SYNC command (such as a Redis 4.0 or 5.0 single-node instance), migrate the instance data to a master/standby instance and export the data by using the backup function.
    +
    • If the instance allows the SYNC command (such as a Redis 3.0 single-node instance), run the following command to export the instance data:

      redis-cli -h {source_redis_address} -p 6379 [-a password] --rdb {output.rdb}

      +
    • If the instance does not allow the SYNC command (such as a Redis 4.0 or 5.0 single-node instance), migrate the instance data to a master/standby instance and export the data by using the backup function.
diff --git a/docs/dcs/umn/dcs-faq-210531002.html b/docs/dcs/umn/dcs-faq-210531002.html index 3550f6f4f..0f39851a3 100644 --- a/docs/dcs/umn/dcs-faq-210531002.html +++ b/docs/dcs/umn/dcs-faq-210531002.html @@ -9,6 +9,8 @@

Solutions

  • Configure scheduled hot key analysis tasks by referring to Hot Key Analysis, or use the SCAN command to traverse all keys on a scheduled basis and remove expired keys from the memory.
  • Configure a scheduled task to scan all master nodes of the instance. All keys will be scanned, and Redis will determine whether the keys have expired. Expired keys will be released. For details, see Scanning Expired Keys.
+

How Do I Know Which Expired Keys Have Been Deleted?

Deleted expired keys cannot be queried.

+
diff --git a/docs/dcs/umn/dcs-faq-210706001.html b/docs/dcs/umn/dcs-faq-210706001.html index 9bf6eecd1..2064b03e2 100644 --- a/docs/dcs/umn/dcs-faq-210706001.html +++ b/docs/dcs/umn/dcs-faq-210706001.html @@ -2,9 +2,9 @@

When Will AOF Rewrites Be Triggered?

AOF rewrites involve the following concepts:

-
  • Rewrite window, which is currently 01:00 to 04:59
  • Disk usage threshold, which is 50%
+
  • Rewrite window, which is currently 01:00 to 04:59
  • Disk usage threshold, which is 50%
  • Dataset memory, which is the percentage of memory that Redis dataset has used.

AOF rewrites are triggered in the following scenarios:

-
  • If the disk usage reaches the threshold (regardless of whether the current time is within the rewrite window), rewrites will be triggered on instances whose AOF file size is larger than the memory dataset size.
  • If the disk usage is below the threshold and the current time is within the rewrite window, rewrites will be triggered on instances whose AOF file size is larger than the dataset memory multiplied by 1.5.
  • If the disk usage is below the threshold but the current time is out of the rewrite window, rewrites will be triggered on instances whose AOF file size is larger than the maximum memory multiplied by 4.5.
+
  • If the disk usage reaches the threshold (regardless of whether the current time is within the rewrite window), rewrites will be triggered on instances whose AOF file size is larger than the dataset memory.
  • If the disk usage is below the threshold and the current time is within the rewrite window, rewrites will be triggered on instances whose AOF file size is larger than the dataset memory multiplied by 1.5.
  • If the disk usage is below the threshold but the current time is out of the rewrite window, rewrites will be triggered on instances whose AOF file size is larger than the instance's maximum memory multiplied by 4.5.
diff --git a/docs/dcs/umn/dcs-faq-221222.html b/docs/dcs/umn/dcs-faq-221222.html index 517989e59..a1e87574d 100644 --- a/docs/dcs/umn/dcs-faq-221222.html +++ b/docs/dcs/umn/dcs-faq-221222.html @@ -2,9 +2,9 @@

Is the Read-only Address of a Master/Standby Instance Connected to the Master or Standby Node?

A master/standby DCS Redis 4.0/5.0/6.0 instance has a Connection Address and a Read-only Address. The connection address is used to connect to the master node of the instance, and the read-only address is used to connect to the standby node of the instance.

-

For details, see architecture of Master/Standby DCS Redis 4.0/5.0/6.0 Instances.

+

For details, see Architecture of Master/Standby DCS Redis 4.0/5.0/6.0 Instances.

Figure 1 Instance addresses
-

+

By default, the client reads and writes data on the master node. Data is synchronized to the standby node. To implement read/write splitting, ensure that your client can distinguish between read and write requests. The client directs write requests to the read/write domain name and read requests to the read-only domain name.

diff --git a/docs/dcs/umn/dcs-migrate-0220411.html b/docs/dcs/umn/dcs-migrate-0220411.html index 3ac5dfceb..f8f359a33 100644 --- a/docs/dcs/umn/dcs-migrate-0220411.html +++ b/docs/dcs/umn/dcs-migrate-0220411.html @@ -20,8 +20,8 @@ sudo systemctl enable nginx.service vi nginx.conf
  • Example forwarding configuration:
    stream {
     server {
-        listen 6379;
-        proxy_pass {source_instance_address}:{port};
+        listen 6379;
+        proxy_pass {source_instance_address}:{port};
     }
    }

    6379 is the listening port of the source forwarding server. {source_instance_address} and {port} are the connection address and port of the source Redis instance.

    @@ -29,7 +29,7 @@ vi nginx.conf

    This configuration must be added exactly where it is shown in the following figure.

    Figure 2 Configuration location
  • Restart Nginx.
    service nginx restart
    -
  • Verify whether Nginx has been started.
    netstat -an|grep 6379
    +
  • Verify whether Nginx has been started.
    netstat -an|grep 6379

    If the port is being listened, Nginx has been started successfully.

    Figure 3 Verification result
    • @@ -37,8 +37,8 @@ vi nginx.conf

    vi nginx.conf

  • Configuration example:
    stream {
     server {
-        listen 6666;
-        proxy_pass {source_ecs_address}:6379;
+        listen 6666;
+        proxy_pass {source_ecs_address}:6379;
     }
    }

    6666 is ECS's listening port, {source_ecs_address} is the public IP address of the source forwarding server, and 6379 is the listening port of the source forwarding server Nginx.

    @@ -46,11 +46,11 @@ vi nginx.conf

    This configuration must be added exactly where it is shown in the following figure.

    Figure 4 Configuration location
  • Restart Nginx.
    service nginx restart
    -
  • Verify whether Nginx has been started.
    netstat -an|grep 6666
    +
  • Verify whether Nginx has been started.
    netstat -an|grep 6666

    If the port is being listened, Nginx has been started successfully.

    Figure 5 Verification result
    • -

  • Run the following command on the ECS to test the network connection of port 6666:

    redis-cli -h {target_ecs_address} -p 6666 -a {password}
    +

  • Run the following command on the ECS to test the network connection of port 6666:

    redis-cli -h {target_ecs_address} -p 6666 -a {password}

    {target_ecs_address} is the EIP of the ECS, 6666 is the listening port of the ECS, and {password} is the source Redis password. If there is no password, leave it blank.

    Figure 6 Connection example

  • Prepare the migration tool redis-shake.

    1. Log in to the ECS.
    2. Download redis-shake. Version 2.0.3 is used as an example. You can use other redis-shake versions as required.
      wget https://github.com/tair-opensource/RedisShake/releases/download/release-v2.0.3-20200724/redis-shake-v2.0.3.tar.gz
      diff --git a/docs/dcs/umn/dcs-migrate-1117003.html b/docs/dcs/umn/dcs-migrate-1117003.html index 2ec80949b..419f872de 100644 --- a/docs/dcs/umn/dcs-migrate-1117003.html +++ b/docs/dcs/umn/dcs-migrate-1117003.html @@ -4,7 +4,6 @@

      redis-shake is an open-source tool for migrating data online or offline (by importing backup files) between Redis Clusters. If the source Redis Cluster is deployed in another cloud, and online migration is not supported, you can migrate data by importing backup files.

      The following describes how to use redis-shake for backup migration to a DCS Redis Cluster instance.

      Importing Backup Files

      If the source Redis and the destitution Redis cannot be connected, or the source Redis is deployed on other clouds, you can migrate data by importing backup files.

      -

      1. Create a Redis Cluster instance on the DCS console.

        The memory of this instance cannot be smaller than that of the source Redis.

      2. Run the following command to obtain the IP addresses and port numbers of all masters of the source Redis and target Redis:

        redis-cli -h {redis_address} -p {redis_port} -a {redis_password} cluster nodes

        In the command output similar to the following, obtain the IP addresses and ports of all masters.

        @@ -19,20 +18,22 @@
    3. Export the RDB file.
      • Edit the redis-shake.conf file by providing the following information about all the masters of both the source and the target:
        source.type = cluster
 # If there is no password, skip the following parameter.
-source.password_raw = {source_redis_password} 
+source.password_raw = {source_redis_password}
 # IP addresses and port numbers of all masters of the source Redis Cluster, which are separated by semicolons (;).
-source.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}...{masterN_ip}:{masterN_port}
        +source.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}…{masterN_ip}:{masterN_port}
      • Run the following command to export the RDB file:

        ./redis-shake -type dump -conf redis-shake.conf

        If the following information is displayed in the execution log, the backup file is exported successfully:

        execute runner[*run.CmdDump] finished!
        +

        If you cannot export the source Redis backup files using this method due to cloud vendors' restrictions on the SYNC and PSYNC commands, export the files on the source console or contact the source technical support.

        +
    4. Import the RDB file.
      1. Import the RDB file (or files) to the cloud server. The cloud server must be connected to the target DCS instance.
      2. Edit the redis-shake configuration file.
        Edit the redis-shake.conf file by providing the following information about all the masters of both the source and the target:
        target.type = cluster
 # If there is no password, skip the following parameter.
-target.password_raw = {target_redis_password} 
+target.password_raw = {target_redis_password}
 # IP addresses and port numbers of all masters of the target instance, which are separated by semicolons (;).
-target.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}...{masterN_ip}:{masterN_port}
+target.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}…{masterN_ip}:{masterN_port}
 # List the RDB files to be imported, separated by semicolons (;).
-rdb.input = local_dump.0;local_dump.1;local_dump.2;local_dump.3
        +rdb.input = {local_dump.0};{local_dump.1};{local_dump.2};{local_dump.3}

        Save and exit.

      3. Run the following command to import the RDB file to the target instance:

        ./redis-shake -type restore -conf redis-shake.conf

        diff --git a/docs/dcs/umn/dcs-migrate-demo02.html b/docs/dcs/umn/dcs-migrate-demo02.html index 08acc12c3..f7a16e9f4 100644 --- a/docs/dcs/umn/dcs-migrate-demo02.html +++ b/docs/dcs/umn/dcs-migrate-demo02.html @@ -19,14 +19,14 @@
      4. Edit the redis-shake configuration file.

        Edit the redis-shake.conf file by providing the following information about all the masters of both the source and the target:

        source.type = cluster
 # If there is no password, skip the following parameter.
-source.password_raw = {source_redis_password} 
+source.password_raw = {source_redis_password}
 # IP addresses and port numbers of all masters of the source Redis Cluster, which are separated by semicolons (;).
-source.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}...{masterN_ip}:{masterN_port}
+source.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}…{masterN_ip}:{masterN_port}
 target.type = cluster
 # If there is no password, skip the following parameter.
-target.password_raw = {target_redis_password} 
+target.password_raw = {target_redis_password}
 # IP addresses and port numbers of all masters of the target instance, which are separated by semicolons (;).
-target.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}...{masterN_ip}:{masterN_port}
        +target.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}…{masterN_ip}:{masterN_port}

        Save and exit.

      5. Migrate data online.

        Run the following command to synchronize data between the source and the target Redis:

        ./redis-shake -type sync -conf redis-shake.conf

        @@ -55,20 +55,20 @@ target.address = Export the RDB file.
        • Edit the redis-shake.conf file by providing the following information about all the masters of both the source and the target:
          source.type = cluster
 # If there is no password, skip the following parameter.
-source.password_raw = {source_redis_password} 
+source.password_raw = {source_redis_password}
 # IP addresses and port numbers of all masters of the source Redis Cluster, which are separated by semicolons (;).
-source.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}...{masterN_ip}:{masterN_port}
          +source.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}…{masterN_ip}:{masterN_port}
        • Run the following command to export the RDB file:

          ./redis-shake -type dump -conf redis-shake.conf

          If the following information is displayed in the execution log, the backup file is exported successfully:

          execute runner[*run.CmdDump] finished!
      6. Import the RDB file.
        1. Import the RDB file (or files) to the cloud server. The cloud server must be connected to the target DCS instance.
        2. Edit the redis-shake configuration file.
          Edit the redis-shake.conf file by providing the following information about all the masters of both the source and the target:
          target.type = cluster
 # If there is no password, skip the following parameter.
-target.password_raw = {target_redis_password} 
+target.password_raw = {target_redis_password}
 # IP addresses and port numbers of all masters of the target instance, which are separated by semicolons (;).
-target.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}...{masterN_ip}:{masterN_port}
+target.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}…{masterN_ip}:{masterN_port}
 # List the RDB files to be imported, separated by semicolons (;).
-rdb.input = local_dump.0;local_dump.1;local_dump.2;local_dump.3
          +rdb.input = {local_dump.0};{local_dump.1};{local_dump.2};{local_dump.3}

          Save and exit.

        3. Run the following command to import the RDB file to the target instance:

          ./redis-shake -type restore -conf redis-shake.conf

          diff --git a/docs/dcs/umn/dcs-migration-0312004.html b/docs/dcs/umn/dcs-migration-0312004.html index 7a48c6abb..398c054b0 100644 --- a/docs/dcs/umn/dcs-migration-0312004.html +++ b/docs/dcs/umn/dcs-migration-0312004.html @@ -20,9 +20,9 @@
        4. Install OBS Browser+.

          For details, see section "Installing OBS Browser+" in Object Storage Service (OBS) Tools Guide (OBS Browser+).

        5. Log in to OBS Browser+.

          For details, see section "Logging In to OBS Browser+" in Object Storage Service (OBS) Tools Guide (OBS Browser+).

        6. Create a bucket.
        7. Upload backup data.
        -

      7. On the OBS console, upload the backup data files to the OBS bucket.

        Perform the following steps if the backup file size does not exceed 5 GB:
        1. In the bucket list, click the name of the created bucket.
        2. In the navigation pane, choose Objects.
        3. On the Objects tab page, click Upload Object.
        4. Upload the objects.

          To upload objects, drag files or folders to the Upload Object area or click add file. A maximum of 100 files can be uploaded at a time. The total size cannot exceed 5 GB.

          +

        5. On the OBS console, upload the backup data files to the OBS bucket.

          Perform the following steps if the backup file size does not exceed 5 GB:
          1. In the bucket list, click the name of the created bucket.
          2. In the navigation pane, choose Objects.
          3. On the Objects tab page, click Upload Object.
          4. Upload the objects.

            To upload objects, drag files or folders to the Upload Object area or click add file. A maximum of 100 files can be uploaded at a time. The total size cannot exceed 5 GB.

            Figure 1 Uploading an object
            -
          5. (Optional) Select KMS encryption to encrypt the file you want to upload.
          6. Click Upload.
          +
        6. (Optional) Select KMS encryption to encrypt the file you want to upload.
        7. Click Upload.

    • diff --git a/docs/dcs/umn/dcs-migration-0312010.html b/docs/dcs/umn/dcs-migration-0312010.html index b2ea138bd..c20bbd86c 100644 --- a/docs/dcs/umn/dcs-migration-0312010.html +++ b/docs/dcs/umn/dcs-migration-0312010.html @@ -18,7 +18,7 @@

    Ensure that the ECS has sufficient disk space for data file decompression, and can communicate with the DCS instance. Generally, the ECS and DCS instance are configured to belong to the same VPC and subnet, and the configured security group rules do not restrict access ports. For details about how to configure a security group, see Security Group Configurations.

    -

    Step 3: Importing Data

    redis-cli -h {dcs_instance_address} -p 6379 -a {password} --pipe < appendonly.aof

    +

    Step 3: Importing Data

    redis-cli -h {dcs_instance_address} -p 6379 -a {password} --pipe < appendonly.aof

    Step 4: Verifying Migration

    After the data is imported successfully, access the DCS instance and run the info command to check whether the data has been successfully imported as required.

    If the data import fails, analyze the cause, modify the data import statement, run the flushall or flushdb command to clear the cached data in the instance, and import the data again.

    diff --git a/docs/dcs/umn/dcs-migration-0312019.html b/docs/dcs/umn/dcs-migration-0312019.html index 6991614fa..b1479e14b 100644 --- a/docs/dcs/umn/dcs-migration-0312019.html +++ b/docs/dcs/umn/dcs-migration-0312019.html @@ -8,7 +8,7 @@

    Note that:

    • If different DBs in the source Redis instance contain the same keys, values of keys in the DB with the largest ID will overwrite those in the other DBs.
    • If the source Redis instance contains multiple DBs, data is stored in the same DB after being migrated to a cluster DCS instance, and the SELECT command is not supported. In this case, modify the configurations for your services.
  • Redis Cluster instances

    Only one DB is configured for a Redis Cluster instance. Data is migrated to a Redis Cluster instance in a different way from other types of instances. Nodes in the shards of a Redis Cluster must be connected separately through clients. Data is imported to the nodes separately. Run the following command to query the IP addresses of the cluster nodes:

    -

    redis-cli -h {Redis Cluster IP} -p 6379 -a {password} cluster nodes

    +

    redis-cli -h {Redis Cluster IP} -p 6379 -a {password} cluster nodes

    In the returned list of IP addresses, record the ones marked by "master".

    • diff --git a/docs/dcs/umn/dcs-migration-1117001.html b/docs/dcs/umn/dcs-migration-1117001.html index b6dc9ed44..8fb85a14a 100644 --- a/docs/dcs/umn/dcs-migration-1117001.html +++ b/docs/dcs/umn/dcs-migration-1117001.html @@ -20,9 +20,9 @@
  • Install OBS Browser+.

    For details, see section "Installing OBS Browser+" in Object Storage Service (OBS) Tools Guide (OBS Browser+).

  • Log in to OBS Browser+.

    For details, see section "Logging In to OBS Browser+" in Object Storage Service (OBS) Tools Guide (OBS Browser+).

  • Create a bucket.
  • Upload backup data.
    • -

  • On the OBS console, upload the backup data files to the OBS bucket.

    Perform the following steps if the backup file size does not exceed 5 GB:
    1. In the bucket list, click the name of the created bucket.
    2. In the navigation pane, choose Objects.
    3. On the Objects tab page, click Upload Object.
    4. Upload the objects.

      To upload objects, drag files or folders to the Upload Object area or click add file. A maximum of 100 files can be uploaded at a time. The total size cannot exceed 5 GB.

      +

    5. On the OBS console, upload the backup data files to the OBS bucket.

      Perform the following steps if the backup file size does not exceed 5 GB:
      1. In the bucket list, click the name of the created bucket.
      2. In the navigation pane, choose Objects.
      3. On the Objects tab page, click Upload Object.
      4. Upload the objects.

        To upload objects, drag files or folders to the Upload Object area or click add file. A maximum of 100 files can be uploaded at a time. The total size cannot exceed 5 GB.

        Figure 1 Uploading an object
        -
      5. (Optional) Select KMS encryption to encrypt the file you want to upload.
      6. Click Upload.
      +
    6. (Optional) Select KMS encryption to encrypt the file you want to upload.
    7. Click Upload.

    • diff --git a/docs/dcs/umn/dcs-migration-190703002.html b/docs/dcs/umn/dcs-migration-190703002.html index a08a4444a..380cb54ec 100644 --- a/docs/dcs/umn/dcs-migration-190703002.html +++ b/docs/dcs/umn/dcs-migration-190703002.html @@ -18,9 +18,9 @@
  • Install OBS Browser+.

    For details, see section "Installing OBS Browser+" in Object Storage Service (OBS) Tools Guide (OBS Browser+).

  • Log in to OBS Browser+.

    For details, see section "Logging In to OBS Browser+" in Object Storage Service (OBS) Tools Guide (OBS Browser+).

  • Create a bucket.
  • Upload backup data.
    • -

  • On the OBS console, upload the backup data files to the OBS bucket.

    Perform the following steps if the backup file size does not exceed 5 GB:
    1. In the bucket list, click the name of the created bucket.
    2. In the navigation pane, choose Objects.
    3. On the Objects tab page, click Upload Object.
    4. Upload the objects.

      To upload objects, drag files or folders to the Upload Object area or click add file. A maximum of 100 files can be uploaded at a time. The total size cannot exceed 5 GB.

      +

    5. On the OBS console, upload the backup data files to the OBS bucket.

      Perform the following steps if the backup file size does not exceed 5 GB:
      1. In the bucket list, click the name of the created bucket.
      2. In the navigation pane, choose Objects.
      3. On the Objects tab page, click Upload Object.
      4. Upload the objects.

        To upload objects, drag files or folders to the Upload Object area or click add file. A maximum of 100 files can be uploaded at a time. The total size cannot exceed 5 GB.

        Figure 1 Uploading an object
        -
      5. (Optional) Select KMS encryption to encrypt the file you want to upload.
      6. Click Upload.
      +
    6. (Optional) Select KMS encryption to encrypt the file you want to upload.
    7. Click Upload.

    • diff --git a/docs/dcs/umn/dcs-pd-0326002.html b/docs/dcs/umn/dcs-pd-0326002.html index 7da2b6aff..17579d66f 100644 --- a/docs/dcs/umn/dcs-pd-0326002.html +++ b/docs/dcs/umn/dcs-pd-0326002.html @@ -6,7 +6,7 @@
    1. E-commerce flash sales

      E-commerce product catalogue, deals, and flash sales data can be cached to Redis.

      For example, the high-concurrency data access in flash sales can be hardly handled by traditional relational databases. It requires the hardware to have higher configuration such as disk I/O. By contrast, Redis supports 100,000 QPS per node and allows you to implement locking using simple commands such as SET, GET, DEL, and RPUSH to handle flash sales.

    2. Live video commenting

      In live streaming, online user, gift ranking, and bullet comment data can be stored as sorted sets in Redis.

      -

      For example, bullet comments can be returned using the ZREVRANGEBYSCORE command. The ZPOPMAX and ZPOPMIN commands in Redis 5.0 can further facilitate message processing.

      +

      For example, bullet comments can be returned using the ZREVRANGEBYSCORE command. The ZPOPMAX and ZPOPMIN commands in Redis 5.0 can further facilitate message processing.

    3. Game leaderboard

      In online gaming, the highest ranking players are displayed and updated in real time. The leaderboard ranking can be stored as sorted sets, which are easy to use with up to 20 commands.

    4. Social networking comments

      In web applications, queries of post comments often involve sorting by time in descending order. As comments pile up, sorting becomes less efficient.

      By using lists in Redis, a preset number of comments can be returned from the cache, rather than from disk, easing the load off the database and accelerating application responses.

      diff --git a/docs/dcs/umn/dcs-pd-0326003.html b/docs/dcs/umn/dcs-pd-0326003.html index be98125ea..00efc6dfa 100644 --- a/docs/dcs/umn/dcs-pd-0326003.html +++ b/docs/dcs/umn/dcs-pd-0326003.html @@ -23,7 +23,7 @@

    -

    Deeply engaged in the open-source community and supports the latest Redis version. Redis 3.0/4.0/5.0/6.0 are supported.

    +

    Deeply engaged in the open-source community and supports the latest Redis version. Available for Redis 3.0/4.0/5.0/6.0.

    Security

    @@ -46,7 +46,7 @@

    Provides more than 30 monitoring metrics and customizable alarm threshold and policies.

    • Various metrics
      • External metrics include the number of commands, concurrent operations, connections, clients, and denied connections.
      • Resource usage metrics include CPU usage, physical memory usage, network input throughput, and network output throughput.
      • Internal metrics include instance capacity usage, as well as the number of keys, expired keys, PubSub channels, PubSub patterns, keyspace hits, and keyspace misses.
      -
    • Custom alarm thresholds and policies for different metrics to help identify service faults.
    +
  • Customize alarm thresholds and policies for different metrics to help identify service faults.
    		•

    Backup and restoration

    diff --git a/docs/dcs/umn/dcs-pd-0916001.html b/docs/dcs/umn/dcs-pd-0916001.html index 64957eacb..45eeb16e2 100644 --- a/docs/dcs/umn/dcs-pd-0916001.html +++ b/docs/dcs/umn/dcs-pd-0916001.html @@ -1,7 +1,7 @@

    Redis 3.0 Instance Specifications

    -

    This section describes DCS Redis 3.0 instance specifications, including the total memory, available memory, maximum number of connections allowed, maximum/assured bandwidth, and reference performance.

    +

    This section describes DCS Redis 3.0 instance specifications, including the total memory, available memory, maximum number of connections allowed, maximum/assured bandwidth, and reference performance.

    The following metrics are related to the instance specifications:

    • Used memory: You can check the memory usage of an instance by viewing the Memory Usage and Used Memory metrics.
    • Maximum connections: The maximum number of connections allowed is the maximum number of clients that can be connected to an instance. To check the number of connections to an instance, view the Connected Clients metric.
    • QPS represents queries per second, which is the number of commands processed per second.
      • Single-node, master/standby, and Proxy Cluster types are available.
      • Only the x86 architecture is supported. The Arm architecture is not supported.
      diff --git a/docs/dcs/umn/dcs-pd-0916002.html b/docs/dcs/umn/dcs-pd-0916002.html index 984b21dd3..2db5d5d9a 100644 --- a/docs/dcs/umn/dcs-pd-0916002.html +++ b/docs/dcs/umn/dcs-pd-0916002.html @@ -1,7 +1,7 @@

      Redis 4.0 and 5.0 Instance Specifications

      -

      This section describes DCS Redis 4.0 and 5.0 instance specifications, including the total memory, available memory, maximum number of connections allowed, maximum/assured bandwidth, and reference performance.

      +

      This section describes DCS Redis 4.0 and 5.0 instance specifications, including the total memory, available memory, maximum number of connections allowed, maximum/assured bandwidth, and reference performance.

      The following metrics are related to the instance specifications:

      • Used memory: You can check the memory usage of an instance by viewing the Memory Usage and Used Memory metrics.
      • Maximum connections: The maximum number of connections allowed is the maximum number of clients that can be connected to an instance. To check the number of connections to an instance, view the Connected Clients metric. After an instance is created, you can change the maximum number of connections of the instance by modifying the maxclients parameter on the Instance Configuration > Parameters page on the console.
      • QPS represents queries per second, which is the number of commands processed per second.
      • Bandwidth: You can view the Flow Control Times metric to check whether the bandwidth has exceeded the limit.

        You can also check the Bandwidth Usage metric. This metric is for reference only, because it may be higher than 100%. For details, see Why Does Bandwidth Usage Exceed 100%?

      diff --git a/docs/dcs/umn/dcs-pd-200312004.html b/docs/dcs/umn/dcs-pd-200312004.html index fb207032d..f3ca08bb7 100644 --- a/docs/dcs/umn/dcs-pd-200312004.html +++ b/docs/dcs/umn/dcs-pd-200312004.html @@ -12,7 +12,7 @@

      For details, see: Modifying Maintenance Time Window.

      Cross-AZ Deployment

      Master/Standby instances are deployed across different AZs with physically isolated power supplies and networks. Applications can also be deployed across AZs to achieve HA for both data and applications.

      -

      When creating a master/standby or cluster DCS Redis instance, you can select a standby AZ for the standby node.

      +

      When creating a master/standby or cluster DCS Redis instance, you can select a standby AZ for the node.

      Shard

      A shard is a management unit of a cluster DCS Redis instance. Each shard corresponds to a redis-server process. A cluster consists of multiple shards. Each shard has multiple slots. Data is distributedly stored in the slots. The use of shards increases cache capacity and concurrent connections.

      Each cluster instance consists of multiple shards. By default, each shard is a master/standby instance with two replicas. The number of shards is equal to the number of master nodes in a cluster instance.

      diff --git a/docs/dcs/umn/dcs-pd-200713005.html b/docs/dcs/umn/dcs-pd-200713005.html index 7e23a1e9a..a9601a41d 100644 --- a/docs/dcs/umn/dcs-pd-200713005.html +++ b/docs/dcs/umn/dcs-pd-200713005.html @@ -10,7 +10,7 @@
    -
    Table 1 Commands supported by DCS Redis 3.0 instances 1

    Keys

    +
    @@ -360,7 +360,7 @@
    Table 1 Commands supported by DCS Redis 3.0 instances (1)

    Keys

    String

    -
    Table 2 Commands supported by DCS Redis 3.0 instances 2

    HyperLoglog

    +
    @@ -458,7 +458,7 @@

    Commands Disabled by DCS for Redis 3.0

    The following lists commands disabled by DCS for Redis 3.0.

    -
    Table 2 Commands supported by DCS Redis 3.0 instances (2)

    HyperLoglog

    Pub/Sub
    Table 3 Redis commands disabled in single-node and master/standby Redis 3.0 instances

    Keys

    +
    @@ -508,7 +508,7 @@
    Table 3 Redis commands disabled in single-node and master/standby DCS Redis 3.0 instances

    Keys

    Server

    -
    Table 4 Redis commands disabled in Proxy Cluster Redis 3.0 instances

    Keys

    +
    diff --git a/docs/dcs/umn/dcs-pd-200813002.html b/docs/dcs/umn/dcs-pd-200813002.html index 3468174a2..4e634f5c0 100644 --- a/docs/dcs/umn/dcs-pd-200813002.html +++ b/docs/dcs/umn/dcs-pd-200813002.html @@ -651,7 +651,7 @@
    Table 4 Redis commands disabled in Proxy Cluster DCS Redis 3.0 instances

    Keys

    Server

    -
    Table 4 Redis commands disabled in Redis Cluster Redis 5.0 instances

    Keys

    +
    diff --git a/docs/dcs/umn/dcs-pd-200813003.html b/docs/dcs/umn/dcs-pd-200813003.html index 480ed9d68..c13cbf309 100644 --- a/docs/dcs/umn/dcs-pd-200813003.html +++ b/docs/dcs/umn/dcs-pd-200813003.html @@ -124,7 +124,7 @@ - diff --git a/docs/dcs/umn/dcs-pd-200813004.html b/docs/dcs/umn/dcs-pd-200813004.html index 9b13a702d..fba32c02e 100644 --- a/docs/dcs/umn/dcs-pd-200813004.html +++ b/docs/dcs/umn/dcs-pd-200813004.html @@ -9,6 +9,8 @@

    EVAL and EVALSHA Commands

    • When the EVAL or EVALSHA command is run, at least one key must be contained in the command parameter. Otherwise, the error message "ERR eval/evalsha numkeys must be bigger than zero in redis cluster mode" is displayed.
    • When the EVAL or EVALSHA command is run, a cluster DCS Redis instance uses the first key to compute slots. Ensure that the keys to be operated in your code are in the same slot. For details, visit https://redis.io/commands.
    • For the EVAL command:
      • You are advised to learn the Lua script features of Redis before running the EVAL command. For details, see https://redis.io/commands/eval.
      • The execution timeout time of a Lua script is 5 seconds. Time-consuming statements such as long-time sleep and large loop statements should be avoided.
      • When calling a Lua script, do not use random functions to specify keys. Otherwise, the execution results are inconsistent on the master and standby nodes.
    +

    Debugging Lua Scripts

    When you debug Lua scripts for Proxy Cluster and read/write splitting instances, only the asynchronous non-blocking mode --ldb is supported. The synchronous blocking mode --ldb-sync-mode is not supported. By default, the maximum concurrency on each proxy is 2. This restriction does not apply to other instance types.

    +

    Other Restrictions

    • The time limit for executing a Redis command is 15 seconds. To prevent other services from failing, a master/replica switchover will be triggered after the command execution times out.
    diff --git a/docs/dcs/umn/dcs-pd-200916001.html b/docs/dcs/umn/dcs-pd-200916001.html index 3afb64eaf..945ae25d2 100644 --- a/docs/dcs/umn/dcs-pd-200916001.html +++ b/docs/dcs/umn/dcs-pd-200916001.html @@ -472,7 +472,7 @@

    Commands Disabled by DCS for Redis 4.0

    The following lists commands disabled by DCS for Redis 4.0.

    -
    Table 4 Redis commands disabled in Redis Cluster DCS Redis 5.0 instances

    Keys

    Server

    Multi-key commands that do not support cross-slot access

    SMOVE, SORT, BITOP, MSETNX, RENAME, RENAMENX, BLPOP, BRPOP, RPOPLPUSH, BRPOPLPUSH, PFMERGE, PFCOUNT

    +

    SMOVE, SORT, BITOP, MSETNX, RENAME, RENAMENX, BLPOP, BRPOP, RPOPLPUSH, BRPOPLPUSH, PFMERGE, PFCOUNT, BLMOVE, COPY, GEOSEARCHSTORE, LMOVE, ZRANGESTORE
    Table 3 Redis commands disabled in single-node and master/standby Redis 4.0 instances

    Keys

    +
    @@ -532,7 +532,7 @@
    Table 3 Redis commands disabled in single-node and master/standby DCS Redis 4.0 instances

    Keys

    Server

    -
    - @@ -469,7 +559,7 @@ - @@ -484,7 +574,7 @@ - @@ -499,7 +589,7 @@ - @@ -514,7 +604,7 @@ - @@ -529,7 +619,7 @@ - @@ -544,7 +634,7 @@ - @@ -559,7 +649,7 @@ - @@ -574,7 +664,7 @@ - @@ -583,65 +673,168 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 4 Redis commands disabled in Redis Cluster Redis 4.0 instances

    Keys

    +
    diff --git a/docs/dcs/umn/dcs-pd-210209002.html b/docs/dcs/umn/dcs-pd-210209002.html index 2503a4a0a..11cb6e92f 100644 --- a/docs/dcs/umn/dcs-pd-210209002.html +++ b/docs/dcs/umn/dcs-pd-210209002.html @@ -110,7 +110,7 @@ - - - - - - - - - - - - - - @@ -308,13 +308,13 @@ - - @@ -329,7 +329,7 @@ - @@ -363,11 +363,101 @@ - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 4 Redis commands disabled in Redis Cluster DCS Redis 4.0 instances

    Keys

    Server

    ZRANGEBYSCORE

    CLIENT KILL

    +

    CONFIG GET

    PTTL

    @@ -125,7 +125,7 @@

    ZRANK

    CLIENT LIST

    +

    MONITOR

    RANDOMKEY

    @@ -140,7 +140,7 @@

    ZREMRANGEBYRANK

    CLIENT GETNAME

    +

    SLOWLOG

    RENAME

    @@ -155,7 +155,7 @@

    ZREMRANGEBYCORE

    CLIENT SETNAME

    +

    ROLE

    RENAMENX

    @@ -170,7 +170,7 @@

    ZREVRANGE

    CONFIG GET

    +

    SWAPDB

    RESTORE

    @@ -185,7 +185,7 @@

    ZREVRANGEBYSCORE

    MONITOR

    +

    MEMORY

    SORT

    @@ -200,7 +200,7 @@

    ZREVRANK

    SLOWLOG

    +

    CONFIG

    TTL

    @@ -215,7 +215,7 @@

    ZSCORE

    ROLE

    +

    ACL

    TYPE

    @@ -230,7 +230,7 @@

    ZUNIONSTORE

    SWAPDB

    +

    -

    SCAN

    @@ -245,7 +245,7 @@

    ZINTERSTORE

    MEMORY

    +

    -

    OBJECT

    @@ -256,11 +256,11 @@

    RPUSH

    -

    +

    SMISMEMBER

    ZSCAN

    CONFIG

    +

    -

    PEXPIREAT

    @@ -275,7 +275,7 @@

    ZRANGEBYLEX

    -

    +

    -

    PEXPIRE

    @@ -299,7 +299,7 @@

    -

    -

    +

    BLMOVE

    -

    -

    -

    +

    COPY

    SETNX

    -

    -

    +

    LMOVE

    -

    -

    -

    +

    LPOS

    -

    -

    -

    +

    ZDIFF

    -

    -

    +

    BITFIELD_RO

    +

    -

    +

    -

    +

    -

    +

    ZDIFFSTORE

    +

    -

    +

    -

    +

    GETDEL

    +

    -

    +

    -

    +

    -

    +

    ZINTER

    +

    -

    +

    -

    +

    GETEX

    +

    -

    +

    -

    +

    -

    +

    ZMSCORE

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    ZRANDMEMBER

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    ZRANGESTORE

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    ZUNION

    +

    -

    +
    @@ -454,7 +544,7 @@

    WATCH

    SELECT

    +

    SELECT (not supported by Redis Cluster instances)

    SCRIPT KILL

    -

    -

    +

    CLIENT CACHING

    SCRIPT LOAD

    -

    -

    +

    CLIENT GETREDIR

    -

    -

    -

    +

    CLIENT INFO

    -

    -

    -

    +

    CLIENT TRACKING

    -

    -

    -

    +

    CLIENT TRACKINGINFO

    -

    -

    -

    +

    CLIENT UNPAUSE

    -

    -

    -

    +

    CLIENT KILL

    -

    -

    -

    +

    CLIENT LIST

    -

    XTRIM

    -

    +

    -

    +

    -

    +

    CLIENT GETNAME

    +

    -

    +

    -

    +

    XAUTOCLAIM

    +

    -

    +

    -

    +

    -

    +

    CLIENT SETNAME

    +

    -

    +

    -

    +

    XGROUP CREATECONSUMER

    +

    -

    +

    -

    +

    -

    +

    HELLO

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    RESET

    +

    -

    +

    -

    +

    -

    +

    Commands Disabled by DCS for Redis 6.0

    -
    - @@ -1598,7 +1598,7 @@
    NOTE:

    Slow queries caused by the MIGRATE, SLAVEOF, CONFIG, BGSAVE, and BGREWRITEAOF commands are not counted.

    - - - - - - - - - - - - - -
    Table 3 Redis commands disabled in DCS Redis 6.0 instances

    Generic (Key)

    +
    - + - - + - - + - - + - - + - - + - - + - - + - - + - - + - - + + + + + + + + + + + + + diff --git a/docs/dcs/umn/dcs-ug-0312004.html b/docs/dcs/umn/dcs-ug-0312004.html index 2857ab373..e520632f0 100644 --- a/docs/dcs/umn/dcs-ug-0312004.html +++ b/docs/dcs/umn/dcs-ug-0312004.html @@ -3,7 +3,7 @@

    Preparing Required Resources

    To access DCS instances through a Virtual Private Cloud (VPC), create a VPC and configure security groups and subnets for it before using DCS. A VPC provides an isolated virtual network environment which you can configure and manage. Using VPCs enhances cloud resource security and simplifies network deployment.

    Once you have created the required resources, you can use them for all DCS instances you subsequently create.

    -

    Creating a VPC and Subnet

    1. Log in to the management console.
    2. Click in the upper left corner and select a region and a project.
    3. Click Service List, and choose Network > Virtual Private Cloud to launch the VPC console.
    4. Click Apply for VPC.
    5. Create a VPC as prompted, retaining the default values unless otherwise required.

      For details about how to create a VPC, see Creating a VPC.

      +

      Creating a VPC and Subnet

      1. Log in to the management console.
      2. Click in the upper left corner and select a region and a project.
      3. Click Service List, and choose Network > Virtual Private Cloud to launch the VPC console.
      4. Click Apply for VPC.
      5. Create a VPC as prompted, retaining the default values unless otherwise required.

        For details about how to create a VPC, see Creating a VPC.

        After a VPC is created, a subnet is also created in the subnet. If the VPC needs more subnets, go to 6 and 7. Otherwise, go to Creating a Security Group.

        • When creating a VPC, CIDR Block indicates the IP address range of the VPC. If this parameter is set, the IP addresses of subnets in the VPC must be within the IP address range of the VPC.
        • If you create a VPC to provision DCS instances, you do not need to configure the CIDR block for the VPC.
        diff --git a/docs/dcs/umn/dcs-ug-0312009.html b/docs/dcs/umn/dcs-ug-0312009.html index 61cec1a5e..dbef1a249 100644 --- a/docs/dcs/umn/dcs-ug-0312009.html +++ b/docs/dcs/umn/dcs-ug-0312009.html @@ -32,9 +32,9 @@

        If the command output contains redis, the phpredis client environment has been set up.

    6. Access the DCS instance by using phpredis.

      1. Edit a redis.php file.
        <?php
-    $redis_host = "{redis_instance_address}";
-    $redis_port = 6379;
-    $user_pwd = "{password}";
+    $redis_host = "{redis_instance_address}";
+    $redis_port = {port};
+    $user_pwd = "{password}";
     $redis = new Redis();
     if ($redis->connect($redis_host, $redis_port) == false) {
        die($redis->getLastError());
@@ -49,7 +49,7 @@
     echo $value;
     $redis->close();
 ?>
        -

        {redis_instance_address} indicates the IP address/domain name of DCS instance and 6379 is an example port number of DCS instance. For details about how to obtain the IP address/domain name and port, see 1. Change them as required. {password} indicates the password used to log in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation. If password-free access is enabled, shield the if statement for password authentication.

        +

        {redis_instance_address} indicates the example IP address/domain name of the DCS instance and {port} indicates the port number of the DCS instance. For details about how to obtain the IP address/domain name and port, see 1. Change them as required. {password} indicates the password used to log in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation. If password-free access is enabled, shield the if statement for password authentication.

      2. Run the php redis.php command to access the DCS instance.

    diff --git a/docs/dcs/umn/dcs-ug-0312010.html b/docs/dcs/umn/dcs-ug-0312010.html index 0a84efc5d..7c87cb71c 100644 --- a/docs/dcs/umn/dcs-ug-0312010.html +++ b/docs/dcs/umn/dcs-ug-0312010.html @@ -26,7 +26,7 @@ int main(int argc, char **argv) { redisContext *conn; redisReply *reply; if (argc < 3) { - printf("Usage: example {instance_ip_address} 6379 {password}\n"); + printf("Usage: example {instance_ip_address} 6379 {password}\n"); exit(0); } const char *hostname = argv[1]; @@ -66,7 +66,7 @@ int main(int argc, char **argv) {

    If an error is reported, locate the directory where the hiredis.h file is saved and modify the compilation command.

    After the compilation, an executable connRedis file is obtained.

  • Run the following command to access the chosen DCS Redis instance:

    ./connRedis {redis_instance_address} 6379 {password}

    -

    {redis_instance_address} indicates the IP address/domain name of DCS instance and 6379 is an example port number of DCS instance. For details about how to obtain the IP address/domain name and port, see 1. Change them as required. {password} indicates the password used to log in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.

    +

    {redis_instance_address} indicates the IP address/domain name of DCS instance and 6379 is an example port number of DCS instance. For details about how to obtain the IP address/domain name and port, see 1. Change them as required. {password} indicates the password used to log in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.

    You have successfully accessed the instance if the following command output is displayed:

    AUTH: OK
 SET: OK
diff --git a/docs/dcs/umn/dcs-ug-0312011.html b/docs/dcs/umn/dcs-ug-0312011.html
index f2d2e4457..aa50e2e50 100644
--- a/docs/dcs/umn/dcs-ug-0312011.html
+++ b/docs/dcs/umn/dcs-ug-0312011.html
@@ -20,7 +20,7 @@
  • Use the redis-py client to connect to the instance. In the following steps, commands are executed in CLI mode. (Alternatively, write the commands into a Python script and then execute the script.)
    1. Run the python command to enter the CLI mode. You have entered CLI mode if the following command output is displayed:
      Figure 2 Entering the CLI mode
    2. Run the following command to access the chosen DCS Redis instance:
      r = redis.StrictRedis(host='XXX.XXX.XXX.XXX', port=6379, password='******');
      -

      XXX.XXX.XXX.XXX indicates the IP address/domain name of the DCS instance and 6379 is an example port number of the instance. For details about how to obtain the IP address/domain name and port, see 1. Change them as required. ****** indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.

      +

      XXX.XXX.XXX.XXX indicates the IP address/domain name of the DCS instance and 6379 is an example port number of the instance. For details about how to obtain the IP address/domain name and port, see 1. Change them as required. ****** indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.

      You have successfully accessed the instance if the following command output is displayed. Enter commands to perform read and write operations on the database.

      Figure 3 Redis connected successfully
    @@ -30,7 +30,7 @@
  • Go to the directory where the decompressed redis-py-cluster package is saved, and install redis-py-cluster.

    python setup.py install

  • Access the DCS Redis instance by using redis-py-cluster.

    In the following steps, commands are executed in CLI mode. (Alternatively, write the commands into a Python script and then execute the script.)

    -
    1. Run the python command to enter the CLI mode.
    2. Run the following command to access the chosen DCS Redis instance. If the instance does not have a password, exclude password='******' from the command.
      >>> from rediscluster import RedisCluster
+
      1. Run the python command to enter the CLI mode.
      2. Run the following command to access the chosen DCS Redis instance. If the instance does not have a password, exclude password='******' from the command.
        >>> from rediscluster import RedisCluster
 
 >>> startup_nodes = [{"host": "192.168.0.143", "port": "6379"},{"host": "192.168.0.144", "port": "6379"},{"host": "192.168.0.145", "port": "6379"},{"host": "192.168.0.146", "port": "6379"}]
 
diff --git a/docs/dcs/umn/dcs-ug-0312012.html b/docs/dcs/umn/dcs-ug-0312012.html
index ee6d790b2..864867dc5 100644
--- a/docs/dcs/umn/dcs-ug-0312012.html
+++ b/docs/dcs/umn/dcs-ug-0312012.html
@@ -26,7 +26,7 @@ var redis = new Redis({
   port: 6379,          // Redis port
   host: '192.168.0.196',   // Redis host
   family: 4,           // 4 (IPv4) or 6 (IPv6)
-  password: '******',
+  password: '******',
   db: 0
 }); 
 redis.set('foo', 'bar');
@@ -42,7 +42,7 @@ redis.sadd('set', 1, 3, 5, 7);
 redis.sadd('set', [1, 3, 5, 7]);
 // All arguments are passed directly to the redis server:
 redis.set('key', 100, 'EX', 10);
        
-
        host indicates the example IP address/domain name of the DCS instance and port indicates the port number of the DCS instance. For details about how to obtain the IP address/domain name and port, see 1. Change them as required. ****** indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.
        
+
        host indicates the example IP address/domain name of the DCS instance and port indicates the port number of the DCS instance. For details about how to obtain the IP address/domain name and port, see 1. Change them as required. ****** indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.
        
 
      3. Run the sample script to access the chosen DCS instance.
        node ioredisdemo.js
        
 
      
 
      
@@ -66,7 +66,7 @@ var redis = new Redis({
   port: 6379,          // Redis port
   host: '192.168.0.196',   // Redis host
   family: 4,           // 4 (IPv4) or 6 (IPv6)
-  password: '******',
+  password: '******',
   db: 0
 });
 redis.set('foo', 'bar');
@@ -82,7 +82,7 @@ redis.sadd('set', 1, 3, 5, 7);
 redis.sadd('set', [1, 3, 5, 7]); 
 // All arguments are passed directly to the redis server:
 redis.set('key', 100, 'EX', 10);
      -

      host indicates the example IP address/domain name of the DCS instance and port indicates the port number of the DCS instance. For details about how to obtain the IP address/domain name and port, see 1. Change them as required. ****** indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.

      +

      host indicates the example IP address/domain name of the DCS instance and port indicates the port number of the DCS instance. For details about how to obtain the IP address/domain name and port, see 1. Change them as required. ****** indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.

    3. Run the sample script to access the chosen DCS instance.

      node ioredisdemo.js

    • diff --git a/docs/dcs/umn/dcs-ug-0312013.html b/docs/dcs/umn/dcs-ug-0312013.html index 519743b91..9181de735 100644 --- a/docs/dcs/umn/dcs-ug-0312013.html +++ b/docs/dcs/umn/dcs-ug-0312013.html @@ -17,7 +17,7 @@ namespace redisdemo class Program { // redis config - private static ConfigurationOptions connDCS = ConfigurationOptions.Parse("10.10.38.233:6379,password=********,connectTimeout=2000"); + private static ConfigurationOptions connDCS = ConfigurationOptions.Parse("{instance_ip_address}:{port},password=********,connectTimeout=2000"); //the lock for singleton private static readonly object Locker = new object(); //singleton @@ -50,7 +50,7 @@ namespace redisdemo } } } -

    10.10.38.233:6379 contains an example IP address/domain name and port number of the DCS Redis instance. For details about how to obtain the IP address/domain name and port, see 1. Change them as required. ******** indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.

    +

    {instance_ip_address} and {port} are the IP address/domain name and port number of the DCS Redis instance. For details about how to obtain the IP address/domain name and port, see 1. Change them as required. ******** indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.

  • Run the code. You have successfully accessed the instance if the following command output is displayed:

    Hello, DCS for Redis!

    For more information about other commands of StackExchange.Redis, visit StackExchange.Redis.

    • diff --git a/docs/dcs/umn/dcs-ug-0312016.html b/docs/dcs/umn/dcs-ug-0312016.html index d92ed82b8..f83a47334 100644 --- a/docs/dcs/umn/dcs-ug-0312016.html +++ b/docs/dcs/umn/dcs-ug-0312016.html @@ -77,26 +77,26 @@ - - - - - - - - diff --git a/docs/dcs/umn/dcs-ug-0312019.html b/docs/dcs/umn/dcs-ug-0312019.html index ab1c5f040..b64cc97a3 100644 --- a/docs/dcs/umn/dcs-ug-0312019.html +++ b/docs/dcs/umn/dcs-ug-0312019.html @@ -2,7 +2,7 @@

    Exporting DCS Instance List

    On the DCS console, you can export DCS instance information in full to an Excel file.

    -

    Procedure

    1. Log in to the DCS console.
    2. Click in the upper left corner and select a region and a project.
    3. In the navigation pane, choose Cache Manager.
    4. Click above the instance list.
    +

    Procedure

    1. Log in to the DCS console.
    2. Click in the upper left corner and select a region and a project.
    3. In the navigation pane, choose Cache Manager.
    4. Click Import above the instance list to export the DCS instance list.
    diff --git a/docs/dcs/umn/dcs-ug-0312037.html b/docs/dcs/umn/dcs-ug-0312037.html index b61d2407d..09a1e7560 100644 --- a/docs/dcs/umn/dcs-ug-0312037.html +++ b/docs/dcs/umn/dcs-ug-0312037.html @@ -5,7 +5,7 @@

    Simply download the source Redis backup data and then upload the data to an OBS bucket in the same region as the target DCS Redis instance. After you have created a migration task on the DCS console, DCS will read data from the OBS bucket and data will be migrated to the target instance.

    .aof, .rbb, .zip, and .tar.gz files can be uploaded to OBS buckets. You can directly upload .aof and .rdb files or compress them into .zip or .tar.gz files before uploading.

    -

    Prerequisites

    • The OBS bucket must be in the same region as the target DCS Redis instance.
    • The data files to be uploaded must be in the .aof, .rdb, .zip, or .tar.gz format.
    • To migrate data from a single-node or master/standby Redis instance of other cloud vendors, create a backup task and download the backup file.
    • To migrate data from a cluster Redis instance of other cloud vendors, download all backup files and upload all of them to the OBS bucket. Each backup file contains data for a shard of the instance.
    • Redis Cluster instances only support .rdb files and do not support .aof files.
    +

    Prerequisites

    • The OBS bucket must be in the same region as the target DCS Redis instance.
    • The data files to be uploaded must be in .aof, .rdb, .zip, or .tar.gz formats. .zip files must contain .aof or .rdb files.
    • To migrate data from a single-node or master/standby Redis instance of other cloud vendors, create a backup task and download the backup file.
    • To migrate data from a cluster Redis instance of other cloud vendors, download all backup files and upload all of them to the OBS bucket. Each backup file contains data for a shard of the instance.
    • Redis Cluster instances only support .rdb files and do not support .aof files.

    Step 1: Prepare the Target DCS Redis Instance

    • If a DCS Redis instance is not available, create one first. For details, see Creating a DCS Redis Instance.
    • If a DCS Redis instance is available, you do not need to create a new one. However, you can clear the instance data before the migration.
      • If the target instance is Redis 4.0 and later, clear the data by referring to Clearing DCS Instance Data.
      • If the target instance is a DCS Redis 3.0 instance, run the FLUSHALL command to clear data.
      • If the target instance data is not cleared before the migration and the source and target instances contain the same key, the key in the target instance will be overwritten by the key in the source instance after the migration.
    • Redis is backward compatible. The target instance version must be the same as or later than the source instance version.
    @@ -20,9 +20,9 @@
  • Install OBS Browser+.

    For details, see section "Installing OBS Browser+" in Object Storage Service (OBS) Tools Guide (OBS Browser+).

  • Log in to OBS Browser+.

    For details, see section "Logging In to OBS Browser+" in Object Storage Service (OBS) Tools Guide (OBS Browser+).

  • Create a bucket.
  • Upload backup data.
    • -

  • On the OBS console, upload the backup data files to the OBS bucket.

    Perform the following steps if the backup file size does not exceed 5 GB:
    1. In the bucket list, click the name of the created bucket.
    2. In the navigation pane, choose Objects.
    3. On the Objects tab page, click Upload Object.
    4. Upload the objects.

      To upload objects, drag files or folders to the Upload Object area or click add file. A maximum of 100 files can be uploaded at a time. The total size cannot exceed 5 GB.

      +

    5. On the OBS console, upload the backup data files to the OBS bucket.

      Perform the following steps if the backup file size does not exceed 5 GB:
      1. In the bucket list, click the name of the created bucket.
      2. In the navigation pane, choose Objects.
      3. On the Objects tab page, click Upload Object.
      4. Upload the objects.

        To upload objects, drag files or folders to the Upload Object area or click add file. A maximum of 100 files can be uploaded at a time. The total size cannot exceed 5 GB.

        Figure 1 Uploading an object
        -
      5. (Optional) Select KMS encryption to encrypt the file you want to upload.
      6. Click Upload.
      +
    6. (Optional) Select KMS encryption to encrypt the file you want to upload.
    7. Click Upload.

    • diff --git a/docs/dcs/umn/dcs-ug-0326008.html b/docs/dcs/umn/dcs-ug-0326008.html index a7eb1c256..23bc54506 100644 --- a/docs/dcs/umn/dcs-ug-0326008.html +++ b/docs/dcs/umn/dcs-ug-0326008.html @@ -31,7 +31,7 @@
    • On the instance creation page, the default parameter templates are used by default.
    • If you use a custom template, the selected cache engine version and instance type must match those of the template. For details about using custom templates, see Creating a Custom Parameter Template.

  • Choose whether to enable Auto Backup.

    This parameter is displayed only when the instance type is master/standby or cluster. For more information on how to configure a backup policy, see Overview.

    -

  • Specify the number of instances to create.
  • Enter an instance name.

    The value of Name contains at least 4 characters. When you create multiple instances at a time, the instances are named in the format of custom name-n, where n starts from 000 and is incremented by 1. For example, if you create two instances and set name to dcs_demo, the two instances are respectively named as dcs_demo-000 and dcs_demo-001.

    +

  • Specify the number of instances to create.
  • Enter an instance name.

    The value of Name contains at least 4 characters. When you create multiple instances at a time, the instances are named in the format of custom name-n, where n starts from 000 and is incremented by 1. For example, if you create two instances and set name to dcs_demo, the two instances are respectively named as dcs_demo-000 and dcs_demo-001.

  • Click More Settings to configure more parameters.

    1. Enter a description of the instance.
    2. Rename critical commands.

      Command Renaming is displayed for Redis 4.0 and later. Currently, you can only rename the COMMAND, KEYS, FLUSHDB, FLUSHALL, HGETALL, SCAN, HSCAN, SSCAN, and ZSCAN commands.

    3. Specify the maintenance window.

      Choose a window for DCS O&M personnel to perform maintenance on your instance. You will be contacted before any maintenance activities are performed.

    diff --git a/docs/dcs/umn/dcs-ug-0326009.html b/docs/dcs/umn/dcs-ug-0326009.html index bbd6c9d7e..bf35899a1 100644 --- a/docs/dcs/umn/dcs-ug-0326009.html +++ b/docs/dcs/umn/dcs-ug-0326009.html @@ -2,14 +2,13 @@

    Accessing a DCS Redis Instance Through redis-cli

    Access a DCS Redis instance through redis-cli on an ECS in the same VPC. For more information on how to use other Redis clients, visit https://redis.io/clients.

    -
    • Redis 3.0 does not support port customization and allows only port 6379. For Redis 4.0 and later, you can specify a port or use the default port 6379. The following uses the default port 6379. If you have specified a port, replace 6379 with the actual port.
    • When connecting to a Redis Cluster instance, ensure that -c is added to the command. Otherwise, the connection will fail.
      • Run the following command to connect to a Redis Cluster instance:

        ./redis-cli -h {dcs_instance_address} -p 6379 -a {password} -c

        -
      • Run the following command to connect to a single-node, master/standby, or Proxy Cluster instance:

        ./redis-cli -h {dcs_instance_address} -p 6379 -a {password}

        +
        • Redis 3.0 does not support port customization and allows only port 6379. For Redis 4.0 and later, you can specify a port or use the default port 6379. The following uses the default port 6379. If you have specified a port, replace 6379 with the actual port.
        • When connecting to a Redis Cluster instance, ensure that -c is added to the command. Otherwise, the connection will fail.
          • Run the following command to connect to a Redis Cluster instance:

            ./redis-cli -h {dcs_instance_address} -p 6379 -a {password} -c

            +
          • Run the following command to connect to a single-node, master/standby, or Proxy Cluster instance:

            ./redis-cli -h {dcs_instance_address} -p 6379 -a {password}

          For details, see 3 and 4.

        • If SSL is enabled for a single-node or master/standby DCS Redis 6.0 instance, set an SSL certificate path.

          ./redis-cli -h {dcs_instance_address} -p 6379 -a {password} --tls --cacert {certification file path}

        • If SSL is enabled for a Redis Cluster DCS Redis 6.0 instance, set a certificate path.

          ./redis-cli -h {dcs_instance_address} -p 6379 -a {password} -c --tls --cacert {certification file path}

          -
        • To connect to Redis with SSL encryption, use redis-cli 6.x or later.

          -
        +
      • To connect to Redis with SSL encryption, use redis-cli 6.x or later.

    Prerequisites

    • The DCS Redis instance you want to access is in the Running state.
    • An ECS has been created. For more information on how to create ECSs, see the Elastic Cloud Server User Guide.
    • If the ECS runs the Linux OS, ensure that the GCC compilation environment has been installed on the ECS.
    @@ -25,11 +24,11 @@

  • Access a DCS instance of a type other than Redis Cluster.

    Perform the following procedure to access a single-node, master/standby instance.

    ./redis-cli -h ${dcs_instance_address} -p 6379 -a ${password}

    -
    1. If the instance is password-free, connect it by running the ./redis-cli -h ${dcs_instance_address} -p 6379 command.
    2. If the instance is password-protected, connect it by running the ./redis-cli -h ${dcs_instance_address} -p 6379 -a ${password} command.
    3. {dcs_instance_address} can be the Connection Address (domain name) or IP Address. Should I Use a Domain Name or an IP Address to Connect to a DCS Redis Instance?

      +
      1. If the instance is password-free, connect it by running the ./redis-cli -h ${dcs_instance_address} -p 6379 command.
      2. If the instance is password-protected, connect it by running the ./redis-cli -h ${dcs_instance_address} -p 6379 -a ${password} command.
      3. {dcs_instance_address} can be the Connection Address (domain name) or IP Address. For details, see Should I Use Domain Name or IP Address to Connect to a Redis Instance?.

      -

    4. Access a DCS instance of the Redis Cluster type.

      Perform the following procedure to access a DCS Redis 4.0 or 5.0 instance in Redis Cluster type.

      -
      1. Run the following commands to access the chosen DCS Redis instance:

        ./redis-cli -h {dcs_instance_address} -p 6379 -a {password} -c

        +

      2. Access a DCS instance of the Redis Cluster type.

        Do as follows to access a Redis Cluster instance:

        +
        1. Run the following commands to access the chosen DCS Redis instance:

          ./redis-cli -h {dcs_instance_address} -p 6379 -a {password} -c

          {dcs_instance_address} indicates the IP address/domain name of the DCS Redis instance, 6379 is the port used for accessing the instance, {password} is the password of the instance, and -c is used for accessing Redis Cluster nodes. The IP address/domain name and port number are obtained in 1.

          Example:
          root@ecs-redis:~/redis-6.2.13/src# ./redis-cli -h 192.168.0.85 -p 6379 -a ****** -c
 192.168.0.85:6379>
          diff --git a/docs/dcs/umn/dcs-ug-0326019.html b/docs/dcs/umn/dcs-ug-0326019.html index c63578ce3..230204528 100644 --- a/docs/dcs/umn/dcs-ug-0326019.html +++ b/docs/dcs/umn/dcs-ug-0326019.html @@ -596,7 +596,7 @@
          NOTE:

          Slow queries caused by the MIGRATE, SLAVEOF, CONFIG, BGSAVE, and BGREWRITEAOF commands are not counted.

          -
    • @@ -784,7 +784,7 @@ - @@ -1210,7 +1210,7 @@
    Table 3 Redis commands disabled in DCS Redis 6.0 instances

    Generic (Key)

    Server

    +

    Server

    +

    Cluster

    MIGRATE

    +

    MIGRATE

    SLAVEOF

    +

    SLAVEOF

    +

    CLUSTER MEET

    -

    +

    -

    SHUTDOWN

    +

    SHUTDOWN

    +

    CLUSTER FLUSHSLOTS

    -

    +

    -

    LASTSAVE

    +

    LASTSAVE

    +

    CLUSTER ADDSLOTS

    -

    +

    -

    DEBUG commands

    +

    DEBUG commands

    +

    CLUSTER DELSLOTS

    -

    +

    -

    COMMAND

    +

    COMMAND

    +

    CLUSTER SETSLOT

    -

    +

    -

    SAVE

    +

    SAVE

    +

    CLUSTER BUMPEPOCH

    -

    +

    -

    BGSAVE

    +

    BGSAVE

    +

    CLUSTER SAVECONFIG

    -

    +

    -

    BGREWRITEAOF

    +

    BGREWRITEAOF

    +

    CLUSTER FORGET

    -

    +

    -

    SYNC

    +

    SYNC

    +

    CLUSTER REPLICATE

    -

    +

    -

    PSYNC

    +

    PSYNC

    +

    CLUSTER COUNT-FAILURE-REPORTS

    +

    -

    +

    -

    +

    CLUSTER FAILOVER

    +

    -

    +

    -

    +

    CLUSTER SET-CONFIG-EPOCH

    +

    -

    +

    -

    +

    CLUSTER RESET

    Maintenance

    Time when maintenance takes place. To modify the time window, click the icon.

    +

    Time when maintenance takes place. To modify the time window, click the icon.

    Connection

    +

    Connection

    Password Protected

    +

    Password Protected

    Currently, password-protected access and password-free access are supported.

    +

    Currently, password-protected access and password-free access are supported.

    Connection Address

    +

    Connection Address

    Domain name and port number of the instance. You can click to change the port.

    -
    NOTE:
    • The instance has a domain name address if it was created after DCS has been interconnected with DNS. Instances created before the interconnection only have IP addresses and cannot be changed to domain name access.
    • 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 the domain name and port number 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 Architecture of Master/Standby DCS Redis 4.0/5.0/6.0 Instances.
    • You can change the port only for a DCS Redis 4.0/5.0/6.0 instance, but not for a DCS Redis 3.0 instance.
    +

    Domain name and port number of the instance. You can click to change the port.

    +
    NOTE:
    • The instance has a domain name address if it was created after DCS has been interconnected with DNS. Instances created before the interconnection only have IP addresses and cannot be changed to domain name access.
    • For a master/standby DCS Redis 4.0 and later instance, Connection Address indicates the domain name and port number of the master node, and Read-only Address indicates the domain name and port number 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 Architecture of Master/Standby DCS Redis 4.0/5.0/6.0 Instances.
    • You can change the port only for a DCS Redis 4.0 and later instance, but not for a DCS Redis 3.0 instance.

    IP Address

    +

    IP Address

    IP address and port number of the chosen instance.

    +

    IP address and port number of the chosen instance.

    Network

    @@ -119,7 +119,7 @@

    Security Group

    Security group that controls access to the DCS instance. To modify the security group, click .

    -

    This parameter is displayed only for DCS Redis 3.0 instances. DCS for Redis 4.0/5.0/6.0 are based on VPC Endpoint and do not support security groups. You can click configure the whitelist to configure the whitelist.

    +

    This parameter is displayed only for DCS Redis 3.0 instances. DCS for Redis 4.0/5.0/6.0 are based on VPC Endpoint and do not support security groups. You can click configure to configure the whitelist.
    • 1: yes
    • 0: no
    +
    • 1: yes
    • 0: no

    DCS Redis instance

    Instance Node Status

    Status of instance nodes. If the status is normal, the value is 0. If the status is abnormal, the value is 1.

    +

    Status of instance nodes. If the status is normal, the value is 0. If the status is abnormal, the value is 1.

    -

    -

    Redis Server Metrics of DCS Redis Instances

    • The Monitored Object column lists instances that support the corresponding metrics.
    +

    Redis Server Metrics of DCS Redis Instances

    • The Monitored Object column lists instances that support the corresponding metrics.
    @@ -1378,7 +1378,7 @@

    Memory Fragmentation Ratio

    Current memory fragmentation, which is the ratio between used_memory_rss/used_memory.

    +

    Current memory fragmentation, which is the ratio between used_memory_rss/used_memory.

    ≥ 0
    • 1: yes
    • 0: no
    +
    • 1: yes
    • 0: no

    Redis Server of a cluster instance

    Redis Server of a master/standby DCS Redis 4.0/5.0/6.0 instance

    @@ -1624,7 +1624,7 @@

    SADD

    Number of SADD commands processed per second

    +

    Number of SADD commands processed per second

    Unit: count/s

    0–500,000

    @@ -1639,7 +1639,7 @@

    SMEMBERS

    Number of SMEMBERS commands processed per second

    +

    Number of SMEMBERS commands processed per second

    Unit: count/s

    0–500,000

    @@ -1667,7 +1667,7 @@

    DEL

    Number of DEL commands processed per second

    +

    Number of DEL commands processed per second

    Unit: count/s

    0–500,000

    @@ -1682,7 +1682,7 @@

    EXPIRE

    Number of EXPIRE commands processed per second

    +

    Number of EXPIRE commands processed per second

    Unit: count/s

    0–500,000

    @@ -1697,7 +1697,7 @@

    GET

    Number of GET commands processed per second

    +

    Number of GET commands processed per second

    Unit: count/s

    0–500,000

    @@ -1712,7 +1712,7 @@

    HDEL

    Number of HDEL commands processed per second

    +

    Number of HDEL commands processed per second

    Unit: count/s

    0–500,000

    @@ -1727,7 +1727,7 @@

    HGET

    Number of HGET commands processed per second

    +

    Number of HGET commands processed per second

    Unit: count/s

    0–500,000

    @@ -1742,7 +1742,7 @@

    HMGET

    Number of HMGET commands processed per second

    +

    Number of HMGET commands processed per second

    Unit: count/s

    0–500,000

    @@ -1757,7 +1757,7 @@

    HMSET

    Number of HMSET commands processed per second

    +

    Number of HMSET commands processed per second

    Unit: count/s

    0–500,000

    @@ -1772,7 +1772,7 @@

    HSET

    Number of HSET commands processed per second

    +

    Number of HSET commands processed per second

    Unit: count/s

    0–500,000

    @@ -1787,7 +1787,7 @@

    MGET

    Number of MGET commands processed per second

    +

    Number of MGET commands processed per second

    Unit: count/s

    0–500,000

    @@ -1802,7 +1802,7 @@

    MSET

    Number of MSET commands processed per second

    +

    Number of MSET commands processed per second

    Unit: count/s

    0–500,000

    @@ -1817,7 +1817,7 @@

    SET

    Number of SET commands processed per second

    +

    Number of SET commands processed per second

    Unit: count/s

    0–500,000

    @@ -1861,7 +1861,7 @@
    -

    Proxy Metrics

    • The Monitored Object column lists instances that support the corresponding metrics.
    • Dimensions lists the metric dimensions.
    +

    Proxy Metrics

    • The Monitored Object column lists instances that support the corresponding metrics.
    • Dimensions lists the metric dimensions.
    - + + +
    Table 5 Proxy metrics of Proxy Cluster DCS Redis 3.0 instances

    Metric ID

    diff --git a/docs/dcs/umn/dcs-ug-0326026.html b/docs/dcs/umn/dcs-ug-0326026.html index 5bfa9bb1f..3667d0750 100644 --- a/docs/dcs/umn/dcs-ug-0326026.html +++ b/docs/dcs/umn/dcs-ug-0326026.html @@ -8,7 +8,12 @@

    2023-09-25

    +

    2024-02-17

    +

    Updated Exporting DCS Instance List and How Do I Access a DCS Redis Instance Through Redis Desktop Manager?.

    +

    2023-09-25

    Modified the following content:

    diff --git a/docs/dcs/umn/dcs-ug-0713005.html b/docs/dcs/umn/dcs-ug-0713005.html index 7996e9f8a..e3189ebe9 100644 --- a/docs/dcs/umn/dcs-ug-0713005.html +++ b/docs/dcs/umn/dcs-ug-0713005.html @@ -22,7 +22,7 @@ <dependency> <groupId>redis.clients</groupId> <artifactId>jedis</artifactId> - <version>3.6.0</version> + <version>3.10.0</version> </dependency>

    application.properties Configuration

    • Single-node, master/standby, and Proxy Cluster
      #Redis host
@@ -69,7 +69,7 @@ spring.redis.jedis.pool.max-wait=3000
 spring.redis.jedis.pool.time-between-eviction-runs=60S
    -

    Bean Configuration

    • Single-node, master/standby, and Proxy Cluster
      import java.time.Duration;
+
      Bean Configuration
      • Single-node, master/standby, and Proxy Cluster
        import java.time.Duration;
 
 import org.springframework.beans.factory.annotation.Value;
 import org.springframework.context.annotation.Bean;
@@ -277,197 +277,234 @@ public class RedisConfiguration {
     }
 }
        
 
      
-
      
+
      
+
      (Optional) Configuring SSL Connections
      If SSL is enabled for the instance, use the following content to replace the JedisClientConfiguration construction method clientConfiguration() in Bean Configuration for connecting to the instance with SSL. For details about whether your DCS Redis instances support SSL, see Configuring SSL.
      
+
      @Bean
+public JedisClientConfiguration clientConfiguration() throws Exception {
+    JedisClientConfiguration.JedisClientConfigurationBuilder configurationBuilder
+        = JedisClientConfiguration.builder()
+        .connectTimeout(Duration.ofMillis(redisConnectTimeout))
+        .readTimeout(Duration.ofMillis(redisReadTimeout));
+
+    configurationBuilder.usePooling().poolConfig(redisPoolConfig());
+    configurationBuilder.useSsl().sslSocketFactory(getTrustStoreSslSocketFactory());
+    return configurationBuilder.build();
+}
+
+private SSLSocketFactory getTrustStoreSslSocketFactory() throws Exception{
+    //Load the CA certificate in the user-defined path based on service requirements.
+    CertificateFactory cf = CertificateFactory.getInstance("X.509");
+    Certificate ca;
+    try (InputStream is = new FileInputStream("./ca.crt")) {
+        ca = cf.generateCertificate(is);
+    }
+
+    //Create keystore.
+    String keyStoreType = KeyStore.getDefaultType();
+    KeyStore keyStore = KeyStore.getInstance(keyStoreType);
+    keyStore.load(null, null);
+    keyStore.setCertificateEntry("ca", ca);
+
+    //Create TrustManager.
+    TrustManagerFactory trustManagerFactory = TrustManagerFactory.getInstance(
+        TrustManagerFactory.getDefaultAlgorithm());
+    trustManagerFactory.init(keyStore);
+
+    //Create SSLContext.
+    SSLContext context = SSLContext.getInstance("TLS");
+    context.init(null, trustManagerFactory.getTrustManagers(), new SecureRandom());
+    return context.getSocketFactory();
+}
      
 
      
 
      Parameter Description
      
-
      Table 1 RedisStandaloneConfiguration parameters
      Parameter
      
+
      
-
-
-
-
-
-
-
-
-
-
-
-
-
-
      Table 1 RedisStandaloneConfiguration parameters
      Parameter
      
 
      Default Value
      
+
      Default Value
      
 
      Description
      
+
      Description
      
       		
 
      
 
      hostName
      
+
      hostName
      
 
      localhost
      
+
      localhost
      
 
      IP address/domain name for connecting to a DCS Redis instance
      
+
      IP address/domain name for connecting to a DCS Redis instance
      
       		
 
      port
      
+
      port
      
 
      6379
      
+
      6379
      
 
      Port number
      
+
      Port number
      
       		
 
      database
      
+
      database
      
 
      0
      
+
      0
      
 
      Database number. Default: 0.
      
+
      Database number. Default: 0.
      
       		
 
      password
      
+
      password
      
 
      -
      
+
      -
      
 
      Password
      
+
      Password
      
       		
 
      
       
 
      
 
      
 
-
      Table 2 RedisClusterConfiguration parameters
      Parameter
      
+
      
-
-
-
-
-
-
-
      Table 2 RedisClusterConfiguration parameters
      Parameter
      
 
      Description
      
+
      Description
      
       		
 
      
 
      clusterNodes
      
+
      clusterNodes
      
 
      Cluster node connection information, including the node IP address and port number
      
+
      Cluster node connection information, including the node IP address and port number
      
       		
 
      maxRedirects
      
+
      maxRedirects
      
 
      Maximum redirecting times
      
+
      Maximum redirecting times
      
       		
 
      password
      
+
      password
      
 
      Password
      
+
      Password
      
       		
 
      
       
 
      
 
      
 
-
      Table 3 JedisPoolConfig parameters
      Parameter
      
+
      
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
      Table 3 JedisPoolConfig parameters
      Parameter
      
 
      Default Value
      
+
      Default Value
      
 
      Description
      
+
      Description
      
       		
 
      
 
      minIdle
      
+
      minIdle
      
 
      -
      
+
      -
      
 
      Minimum connections in the connection pool
      
+
      Minimum connections in the connection pool
      
       		
 
      maxIdle
      
+
      maxIdle
      
 
      -
      
+
      -
      
 
      Maximum idle connections in the connection pool
      
+
      Maximum idle connections in the connection pool
      
       		
 
      maxTotal
      
+
      maxTotal
      
 
      -
      
+
      -
      
 
      Maximum total connections in the connection pool
      
+
      Maximum total connections in the connection pool
      
       		
 
      blockWhenExhausted
      
+
      blockWhenExhausted
      
 
      true
      
+
      true
      
 
      Indicates whether to wait after the connection pool is exhausted. true: Wait. false: Do not wait. To validate maxWaitMillis, this parameter must be set to true.
      
+
      Indicates whether to wait after the connection pool is exhausted. true: Wait. false: Do not wait. To validate maxWaitMillis, this parameter must be set to true.
      
       		
 
      maxWaitMillis
      
+
      maxWaitMillis
      
 
      -1
      
+
      -1
      
 
      Maximum amount of time (in milliseconds) to wait for connection after the connection pool is exhausted. The default value -1 indicates to wait indefinitely.
      
+
      Maximum amount of time (in milliseconds) to wait for connection after the connection pool is exhausted. The default value -1 indicates to wait indefinitely.
      
       		
 
      testOnCreate
      
+
      testOnCreate
      
 
      false
      
+
      false
      
 
      Indicates whether to enable connectivity test on creating connections. false: Disable. true: Enable.
      
+
      Indicates whether to enable connectivity test on creating connections. false: Disable. true: Enable.
      
       		
 
      testOnBorrow
      
+
      testOnBorrow
      
 
      false
      
+
      false
      
 
      Indicates whether to enable connectivity test on obtaining connections. false: Disable. true: Enable. For heavy-traffic services, set this parameter to false to reduce overhead.
      
+
      Indicates whether to enable connectivity test on obtaining connections. false: Disable. true: Enable. For heavy-traffic services, set this parameter to false to reduce overhead.
      
       		
 
      testOnReturn
      
+
      testOnReturn
      
 
      false
      
+
      false
      
 
      Indicates whether to enable connectivity test on returning connections. false: Disable. true: Enable. For heavy-traffic services, set this parameter to false to reduce overhead.
      
+
      Indicates whether to enable connectivity test on returning connections. false: Disable. true: Enable. For heavy-traffic services, set this parameter to false to reduce overhead.
      
       		
 
      testWhileIdle
      
+
      testWhileIdle
      
 
      false
      
+
      false
      
 
      Indicates whether to check for idle connections. If this parameter is set to false, idle connections are not evicted. Recommended value: true.
      
+
      Indicates whether to check for idle connections. If this parameter is set to false, idle connections are not evicted. Recommended value: true.
      
       		
 
      softMinEvictableIdleTimeMillis
      
+
      softMinEvictableIdleTimeMillis
      
 
      1800000
      
+
      1800000
      
 
      Duration (in milliseconds) after which idle connections are evicted. If the idle duration is greater than this value and the maximum number of idle connections is reached, idle connections are directly evicted.
      
+
      Duration (in milliseconds) after which idle connections are evicted. If the idle duration is greater than this value and the maximum number of idle connections is reached, idle connections are directly evicted.
      
       		
 
      minEvictableIdleTimeMillis
      
+
      minEvictableIdleTimeMillis
      
 
      60000
      
+
      60000
      
 
      Minimum amount of time (in milliseconds) a connection may remain idle in the pool before it is eligible for eviction. The recommended value is -1, indicating that softMinEvictableIdleTimeMillis is used instead of minEvictableIdleTimeMillis.
      
+
      Minimum amount of time (in milliseconds) a connection may remain idle in the pool before it is eligible for eviction. The recommended value is -1, indicating that softMinEvictableIdleTimeMillis is used instead.
      
       		
 
      timeBetweenEvictionRunsMillis
      
+
      timeBetweenEvictionRunsMillis
      
 
      60000
      
+
      60000
      
 
      Interval (in milliseconds) for checking and evicting idle connections.
      
+
      Interval (in milliseconds) for checking and evicting idle connections.
      
       		
 
      
       
 
      
 
      
 
-
      
-
-
-
-
-
-
      Table 4 JedisClientConfiguration parameters
      Parameter
      
+
      
-
-
-
-
-
-
-
-
-
-
-
diff --git a/docs/dcs/umn/dcs-ug-1009001.html b/docs/dcs/umn/dcs-ug-1009001.html
index c0e0765dd..a720d9ce3 100644
--- a/docs/dcs/umn/dcs-ug-1009001.html
+++ b/docs/dcs/umn/dcs-ug-1009001.html
@@ -3,7 +3,7 @@
 
      Viewing Redis Run Logs
      You can create run log files on the DCS console to collect run logs of DCS Redis instances within a specified period. After the logs are collected, you can download the log files to view the logs.
      
 
      This function is supported by DCS Redis 4.0 instances and later.
      
-
      Procedure
      1. Log in to the DCS console.
      2. Click  in the upper left corner and select a region and a project.
      3. In the navigation pane, choose Cache Manager.
      4. Click the name of a DCS instance.
      5. Click the Run Logs tab.
      6. Click Create Log File.
        If the instance is the master/standby or cluster type, you can specify the shard and replica whose run logs you want to collect. If the instance is the single-node type, logs of the only node of the instance will be collected.
        
+
        Procedure
        1. Log in to the DCS console.
        2. Click  in the upper left corner and select a region and a project.
        3. In the navigation pane, choose Cache Manager.
        4. Click the name of a DCS instance.
        5. Click Run Logs. 
        6. Click Create Log File.
          For a master/standby or cluster instance, logs will be collected from the specified shard and replica. If the instance is the single-node type, logs of the only node of the instance will be collected.
          
 
          Select the collection period and click OK.
          
 
        7. After the log file is successfully collected, click Download to download it.
        
 
        
diff --git a/docs/dcs/umn/dcs-ug-190808001.html b/docs/dcs/umn/dcs-ug-190808001.html
index 12ec26cf0..00f951b4f 100644
--- a/docs/dcs/umn/dcs-ug-190808001.html
+++ b/docs/dcs/umn/dcs-ug-190808001.html
@@ -3,7 +3,7 @@
 
        Analyzing Big Keys and Hot Keys
        
 
        By performing big key analysis and hot key analysis, you will have a picture of keys that occupy a large space and keys that are the most frequently accessed.
        
 
        Notes on big key analysis:
        
-
        • All DCS Redis instances support big key analysis.
        • During big key analysis, all keys will be traversed. The larger the number of keys, the longer the analysis takes.
        • Perform big key analysis during off-peak hours and avoid automatic backup periods.
        • For a master/standby or cluster instance, the big key analysis is performed on the standby node, so the impact on the instance is minor. For a single-node instance, the big key analysis is performed on the only node of the instance and will reduce the instance access performance by up to 10%. Therefore, perform big key analysis on single-node instances during off-peak hours.
        • A maximum of 100 big key analysis records (20 for Strings and 80 for Lists/Sets/Zsets/Hashes) are retained for each instance. When this limit is reached, the oldest records will be deleted to make room for new records. You can also manually delete records you no longer need.
        
+
        • All DCS Redis instances support big key analysis.
        • During big key analysis, all keys will be traversed. The larger the number of keys, the longer the analysis takes.
        • Perform big key analysis during off-peak hours and avoid automatic backup periods.
        • For a master/standby or cluster instance, the big key analysis is performed on the standby node, so the impact on the instance is minor. For a single-node instance, the big key analysis is performed on the only node of the instance and will reduce the instance access performance by up to 10%. Therefore, perform big key analysis on single-node instances during off-peak hours.
        • A maximum of 100 big key analysis records (20 for Strings; 80 for Lists/Sets/Zsets/Hashes and max. 20 for each type) are retained for each instance. When this limit is reached, the oldest records will be deleted to make room for new records. You can also manually delete records you no longer need.
        
 
        Notes on hot key analysis:
        
 
        • Only DCS Redis 4.0/5.0/6.0 instances support hot key analysis, and the maxmemory-policy parameter of the instances must be set to allkeys-lfu or volatile-lfu.
        • During hot key analysis, all keys will be traversed. The larger the number of keys, the longer the analysis takes.
        • Perform hot key analysis shortly after peak hours to ensure the accuracy of the analysis results.
        • The hot key analysis is performed on the master node of each instance and will reduce the instance access performance by up to 10%.
        • A maximum of 100 hot key analysis records are retained for each instance. When this limit is reached, the oldest records will be deleted to make room for new records. You can also manually delete records you no longer need.
        
 
         
        Perform big key and hot key analysis during off-peak hours to avoid 100% CPU usage.
        
diff --git a/docs/dcs/umn/dcs-ug-190926001.html b/docs/dcs/umn/dcs-ug-190926001.html
index a3ef2ed25..8d3b33c83 100644
--- a/docs/dcs/umn/dcs-ug-190926001.html
+++ b/docs/dcs/umn/dcs-ug-190926001.html
@@ -8,7 +8,7 @@
 
        For details about the configuration parameters, see Modifying Configuration Parameters.
        
 
         
        You can view the slow log of a Proxy Cluster DCS Redis 3.0 instance only if the instance is created after October 14, 2019. If the instance was created earlier, contact technical support to upgrade it. The upgrade adds the slow log function to the console, and does not affect services.
        
 
        
-
        Viewing Slow Queries on the Console
        1. Log in to the DCS console.
        2. Click  in the upper left corner and select a region and a project.
        3. In the navigation pane, choose Cache Manager.
        4. Click the name of a DCS instance.
        5. Choose Analysis and Diagnosis > Slow Queries.
        6. Select a start date and an end date to view slow queries within the specified period.
           
          For details about the commands, visit the Redis official website.
          
+
          Viewing Slow Queries on the Console
          1. Log in to the DCS console.
          2. Click  in the upper left corner and select a region and a project.
          3. In the navigation pane, choose Cache Manager.
          4. Click the name of a DCS instance.
          5. Choose Analysis and Diagnosis > Slow Queries.
          6. Select a start date and an end date to view slow queries within the specified period.
             
            • For details about the commands, visit the Redis official website.
            • Slow queries of up to seven days can be queried.
            
 
            
 
            Figure 1 Slow query log of an instance
            
 
          
diff --git a/docs/dcs/umn/dcs-ug-210330002.html b/docs/dcs/umn/dcs-ug-210330002.html
index 6b00ff8ba..c48af4b1b 100644
--- a/docs/dcs/umn/dcs-ug-210330002.html
+++ b/docs/dcs/umn/dcs-ug-210330002.html
@@ -85,13 +85,16 @@
 
      Table 4 JedisClientConfiguration parameters
      Parameter
      
 
      Default Value
      
+
      Default Value
      
 
      Description
      
+
      Description
      
       		
 
      
 
      connectTimeout
      
+
      connectTimeout
      
 
      2000
      
+
      2000
      
 
      Connection timeout interval, in milliseconds.
      
+
      Connection timeout interval, in milliseconds.
      
       		
 
      readTimeout
      
+
      readTimeout
      
 
      2000
      
+
      2000
      
 
      Timeout interval for waiting for a response, in milliseconds.
      
+
      Timeout interval for waiting for a response, in milliseconds.
      
       		
 
      poolConfig
      
+
      poolConfig
      
 
      -
      
+
      -
      
 
      Pool configurations. For details, see JedisPoolConfig.
      
+
      Pool configurations. For details, see JedisPoolConfig.
      
       		
 
      
       
 
      
 
      
 
      Performance
      
-
      • The SCAN command is executed at the data plane every 5 ms, that is, 200 times per second. If Keys to Iterate is set to 10, 100, or 1000, 2000, 20,000, or 200,000 keys are scanned per second.
      • The larger the number of keys scanned per second, the higher the CPU usage.
      
+
      • The SCAN command is executed at the data plane every 5 ms, that is, 200 times per second. If Keys to Iterate is set to 10, 50, 100, or 1000, 2000, 10,000, 20,000, or 200,000 keys are scanned per second.
      • The larger the number of keys scanned per second, the higher the CPU usage.
      
 
      Reference test
      
-
      A master/standby instance is scanned. There are 10 million keys that will not expire and 5 million keys that will expire. The expiration time is 1 to 10 seconds.
      • Natural deletion: 10,000 records are deleted per second. It takes 8 minutes to delete 5 million expired keys. The CPU usage is about 5%.
      • Keys to Iterate set to 10: The scanning takes 125 minutes (15 million/2000/60 seconds) and the CPU usage is about 8%.
      • Keys to Iterate set to 50: The scanning takes 25 minutes (15 million/10,000/60 seconds) and the CPU usage is about 10%.
      • Keys to Iterate set to 100: The scanning takes 12.5 minutes (15 million/20,000/60 seconds) and the CPU usage is about 20%.
      • Keys to Iterate set to 1000: The scanning takes 1.25 minutes (15 million/200,000/60 seconds) and the CPU usage is about 25%.
      
+
      A master/standby instance is scanned. There are 10 million keys that will not expire and 5 million keys that will expire. The expiration time is 1 to 10 seconds. A full scan is executed.
      
+
       
      The following test results are for reference only. They may vary depending on the site environment and network fluctuation.
      
+
      
+
      • Natural deletion: 10,000 expired keys are deleted per second. It takes 8 minutes to delete 5 million expired keys. The CPU usage is about 5%.
      • Keys to Iterate set to 10: The scanning takes 125 minutes (15 million/2000/60 seconds) and the CPU usage is about 8%.
      • Keys to Iterate set to 50: The scanning takes 25 minutes (15 million/10,000/60 seconds) and the CPU usage is about 10%.
      • Keys to Iterate set to 100: The scanning takes 12.5 minutes (15 million/20,000/60 seconds) and the CPU usage is about 20%.
      • Keys to Iterate set to 1000: The scanning takes 1.25 minutes (15 million/200,000/60 seconds) and the CPU usage is about 25%.
      
 
      
 
      Configuration suggestions
      
 
      
-
      • You can configure the number of keys to be scanned and the scanning interval based on the total number of keys and the increase in the number of keys in the instance.
      • In the reference test with 15 million keys and Keys to Iterate set to 10, the scanning takes about 125 minutes. In this case, set the interval to more than 4 hours.
      • If you want to accelerate the scanning, set Keys to Iterate to 100. It takes about 12.5 minutes to complete the scanning. Therefore, set the interval to more than 30 minutes.
      • The larger the number of keys to iterate, the faster the scanning, and the higher the CPU usage. There is a trade-off between time and CPU usage.
      • If the number of expired keys does not increase rapidly, you can scan expired keys once a day.
         
        Start scanning during off-peak hours. Set the interval to one day and the timeout to two days.
        
+
        • You can configure the number of keys to be scanned and the scanning interval based on the total number of keys and the increase in the number of keys in the instance.
        • In the reference test with 15 million keys and Keys to Iterate set to 10, the scanning takes about 125 minutes. In this case, set the scan interval to more than 4 hours.
        • If you want to accelerate the scanning, set Keys to Iterate to 100. It takes about 12.5 minutes to complete the scanning. Therefore, set the scan interval to more than 30 minutes.
        • The larger the number of keys to iterate, the faster the scanning, and the higher the CPU usage. There is a trade-off between time and CPU usage.
        • If the number of expired keys does not increase rapidly, you can scan expired keys once a day.
           
          Start scanning during off-peak hours. Set the interval to one day and the timeout to two days.
          
 
          
 
        
 
        
diff --git a/docs/dcs/umn/dcs-ug-211105001.html b/docs/dcs/umn/dcs-ug-211105001.html
index 94b85e35c..ddc834d01 100644
--- a/docs/dcs/umn/dcs-ug-211105001.html
+++ b/docs/dcs/umn/dcs-ug-211105001.html
@@ -2,7 +2,7 @@
 
 
        go-redis
        
 
        Access a DCS Redis instance through go-redis on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis official website.
        
-
        Prerequisites
        • A DCS Redis instance has been created and is in the Running state.
        • View the IP address /domain name and port number of the DCS Redis instance to be accessed.
          For details, see Viewing Details of a DCS Instance.
          
+
          Prerequisites
          
 
          
 
          Procedure
          1. Log in to the ECS.
            A Windows ECS is used as an example.
            
@@ -46,7 +46,7 @@ func main() {
 	}
 	fmt.Println(val1)
 }
-
            host:port are the IP address/domain name and port number of the DCS Redis instance. For details about how to obtain the IP address/domain name and port, see Prerequisites. Change them as required. ******** indicates the password used to log in to the DCS Redis instance. This password is defined during DCS Redis instance creation.
            
+
            host:port are the IP address/domain name and port number of the DCS Redis instance. For details about how to obtain the IP address/domain name and port, see Prerequisites. Change them as required. ******** indicates the password used to log in to the DCS Redis instance. This password is defined during DCS Redis instance creation.
            
 
          2. Run the go build -o test main.go command to package the code into an executable file, for example, test.
             
            To run the package in the Linux OS, set the following parameters before packaging:
            
 
            set GOARCH=amd64
            
 
            set GOOS=linux
            
diff --git a/docs/dcs/umn/dcs-ug-211105002.html b/docs/dcs/umn/dcs-ug-211105002.html
index 360a3871e..c19551560 100644
--- a/docs/dcs/umn/dcs-ug-211105002.html
+++ b/docs/dcs/umn/dcs-ug-211105002.html
@@ -524,7 +524,7 @@ public class RedisPoolConfiguration {
 
 
      localhost
      
 
      IP address/domain name for connecting to a DCS Redis instance.
      
+
      IP address/domain name for connecting to a DCS Redis instance
      
       		
 
      
 
      port
      
@@ -769,28 +769,28 @@ public class RedisPoolConfiguration {
       		
 
      -1
      
 
      Maximum amount of time a connection allocation should block before throwing an exception when the pool is exhausted. The default value -1 indicates to wait indefinitely.
      
+
      Maximum amount of time a connection allocation should block before throwing an exception when the pool is exhausted. The default value –1 indicates to wait indefinitely.
      
       		
 
      
 
      testOnCreate
      
       		
 
      false
      
 
      Set to true to enable connectivity test on creating connections. Default: false.
      
+
      Set to true to enable connectivity test on creating connections. Default: false.
      
       		
 
      
 
      testOnBorrow
      
       		
 
      false
      
 
      Set to true to enable connectivity test on borrowing connections. Default: false. Set to false for heavy-traffic services to reduce overhead.
      
+
      Set to true to enable connectivity test on borrowing connections. Default: false. Set to false for heavy-traffic services to reduce overhead.
      
       		
 
      
 
      testOnReturn
      
       		
 
      false
      
 
      Set to true to enable connectivity test on returning connections. Default: false. Set to false for heavy-traffic services to reduce overhead.
      
+
      Set to true to enable connectivity test on returning connections. Default: false. Set to false for heavy-traffic services to reduce overhead.
      
       		
 
      
 
      testWhileIdle
      
@@ -811,7 +811,7 @@ public class RedisPoolConfiguration {
       		
 
      60000
      
 
      An eviction policy, set -1 (suggested) to disable it. Use softminEvictableIdleTimeMillis instead.
      
+
      An eviction policy, set to –1 (suggested) to disable it. Use softminEvictableIdleTimeMillis instead.
      
       		
 
      
 
      timeBetweenEvictionRunsMillis
      
diff --git a/docs/dcs/umn/dcs-ug-211105004.html b/docs/dcs/umn/dcs-ug-211105004.html
index 650c6f12a..279672f78 100644
--- a/docs/dcs/umn/dcs-ug-211105004.html
+++ b/docs/dcs/umn/dcs-ug-211105004.html
@@ -4,7 +4,7 @@
 
      Access a DCS Redis instance through Redisson on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis official website.
      
 
      For Spring Boot projects, Spring Data Redis is already integrated with Jedis and Lettuce, but does not support Redisson. Redisson provides the redisson-spring-boot-starter component (https://mvnrepository.com/artifact/org.redisson/redisson) that can be used with Spring Boot.
      
 
      Spring Boot 1.x is integrated with Jedis, and Spring Boot 2.x is integrated with Lettuce.
      
-
       
      • If a password was set during DCS Redis instance creation, configure the password for connecting to Redis using Redisson. Do not hard code the plaintext password.
      • To connect to a single-node, master/standby, or Proxy Cluster instance, use the useSingleServer method of the SingleServerConfig object of Redisson. To connect to a Redis Cluster instance, use the useClusterServers method of the ClusterServersConfig object.
      
+
       
      • If a password was set during DCS Redis instance creation, configure the password for connecting to Redis using Redisson. Do not hard code the plaintext password.
      • To connect to a single-node or Proxy Cluster instance, use the useSingleServer method of the SingleServerConfig object of Redisson. To connect to a master/standby instance, use the useMasterSlaveServers method of the MasterSlaveServersConfig object of Redisson. To connect to a Redis Cluster instance, use the useClusterServers method of the ClusterServersConfig object.
      
 
      
 
      Prerequisites
      • A DCS Redis instance has been created and is in the Running state.
      • View the IP address/domain name and port number of the DCS Redis instance to be accessed.
        For details, see Viewing Details of a DCS Instance.
        
 
      • An ECS has been created. For details about how to create an ECS, see Elastic Cloud Server User Guide.
      • If the ECS runs the Linux OS, ensure that the Java compilation environment has been installed on the ECS.
      
@@ -29,18 +29,19 @@
 </dependency>
 
      
 
      Bean Configuration
      Spring Boot does not provide Redisson adaptation, and the application.properties configuration file does not have the corresponding configuration item. Therefore, you can only use Bean configuration.
      
-
      • Single-node
        import org.redisson.codec.JsonJacksonCodec;
+
        • Single-node and Proxy Cluster
          import org.redisson.Redisson;
+import org.redisson.api.RedissonClient;
+import org.redisson.codec.JsonJacksonCodec;
 import org.redisson.config.Config;
 import org.redisson.config.SingleServerConfig;
-import org.redisson.spring.data.connection.RedissonConnectionFactory;
 import org.springframework.beans.factory.annotation.Value;
 import org.springframework.context.annotation.Bean;
 import org.springframework.context.annotation.Configuration;
 
 @Configuration
-public class RedisConfiguration {
+public class SingleConfig {
 
-    @Value("${redis.address}")
+    @Value("${redis.address:}")
     private String redisAddress;
 
     @Value("${redis.password:}")
@@ -74,12 +75,7 @@ public class RedisConfiguration {
     private Integer redisRetryInterval = 200;
 
     @Bean
-    public RedissonConnectionFactory redissonConnectionFactory(Config redissonSingleServerConfig) {
-        return new RedissonConnectionFactory(redissonSingleServerConfig);
-    }
-
-    @Bean
-    public Config redissonSingleServerConfig() {
+    public RedissonClient redissonClient(){
         Config redissonConfig = new Config();
 
         SingleServerConfig serverConfig = redissonConfig.useSingleServer();
@@ -97,25 +93,31 @@ public class RedisConfiguration {
         serverConfig.setRetryInterval(redisRetryInterval);
 
         redissonConfig.setCodec(new JsonJacksonCodec());
-        return redissonConfig;
+        return Redisson.create(redissonConfig);
     }
 }
          
 
        
-
        • Master/Standby
          import org.redisson.codec.JsonJacksonCodec;
+
          • Master/Standby
            import org.redisson.Redisson;
+import org.redisson.api.RedissonClient;
+import org.redisson.codec.JsonJacksonCodec;
 import org.redisson.config.Config;
 import org.redisson.config.MasterSlaveServersConfig;
 import org.redisson.config.ReadMode;
 import org.redisson.config.SubscriptionMode;
-import org.redisson.spring.data.connection.RedissonConnectionFactory;
 import org.springframework.beans.factory.annotation.Value;
 import org.springframework.context.annotation.Bean;
 import org.springframework.context.annotation.Configuration;
 
+import java.util.HashSet;
+
 @Configuration
-public class RedisConfiguration {
+public class MasterStandbyConfig {
     @Value("${redis.master.address}")
     private String redisMasterAddress;
 
+    @Value("${redis.slave.address}")
+    private String redisSlaveAddress;
+
     @Value("${redis.database:0}")
     private Integer redisDatabase = 0;
 
@@ -147,16 +149,14 @@ public class RedisConfiguration {
     private Integer redisRetryInterval = 200;
 
     @Bean
-    public RedissonConnectionFactory redissonConnectionFactory(Config redissonMasterSlaveServersConfig) {
-        return new RedissonConnectionFactory(redissonMasterSlaveServersConfig);
-    }
-
-    @Bean
-    public Config redissonMasterSlaveServersConfig() {
+    public RedissonClient redissonClient() {
         Config redissonConfig = new Config();
 
         MasterSlaveServersConfig serverConfig = redissonConfig.useMasterSlaveServers();
         serverConfig.setMasterAddress(redisMasterAddress);
+        HashSet<String> slaveSet = new HashSet<>();
+        slaveSet.add(redisSlaveAddress);
+        serverConfig.setSlaveAddresses(slaveSet);
 
         serverConfig.setDatabase(redisDatabase);
         serverConfig.setPassword(redisPassword);
@@ -175,94 +175,24 @@ public class RedisConfiguration {
         serverConfig.setRetryInterval(redisRetryInterval);
 
         redissonConfig.setCodec(new JsonJacksonCodec());
-        return redissonConfig;
+        return Redisson.create(redissonConfig);
     }
 }
            
-
          • Proxy Cluster
            import org.redisson.codec.JsonJacksonCodec;
-import org.redisson.config.Config;
-import org.redisson.config.SingleServerConfig;
-import org.redisson.spring.data.connection.RedissonConnectionFactory;
-import org.springframework.beans.factory.annotation.Value;
-import org.springframework.context.annotation.Bean;
-import org.springframework.context.annotation.Configuration;
-
-@Configuration
-public class RedisConfiguration {
-
-    @Value("${redis.address}")
-    private String redisAddress;
-
-    @Value("${redis.password:}")
-    private String redisPassword;
-
-    @Value("${redis.database:0}")
-    private Integer redisDatabase = 0;
-
-    @Value("${redis.connect.timeout:3000}")
-    private Integer redisConnectTimeout = 3000;
-
-    @Value("${redis.connection.idle.timeout:10000}")
-    private Integer redisConnectionIdleTimeout = 10000;
-
-    @Value("${redis.connection.ping.interval:1000}")
-    private Integer redisConnectionPingInterval = 1000;
-
-    @Value("${redis.timeout:2000}")
-    private Integer timeout = 2000;
-
-    @Value("${redis.connection.pool.min.size:50}")
-    private Integer redisConnectionPoolMinSize;
-
-    @Value("${redis.connection.pool.max.size:200}")
-    private Integer redisConnectionPoolMaxSize;
-
-    @Value("${redis.retry.attempts:3}")
-    private Integer redisRetryAttempts = 3;
-
-    @Value("${redis.retry.interval:200}")
-    private Integer redisRetryInterval = 200;
-
-    @Bean
-    public RedissonConnectionFactory redissonConnectionFactory(Config redissonProxyServerConfig) {
-        return new RedissonConnectionFactory(redissonProxyServerConfig);
-    }
-
-    @Bean
-    public Config redissonProxyServerConfig() {
-        Config redissonConfig = new Config();
-
-        SingleServerConfig serverConfig = redissonConfig.useSingleServer();
-        serverConfig.setAddress(redisAddress);
-        serverConfig.setConnectionMinimumIdleSize(redisConnectionPoolMinSize);
-        serverConfig.setConnectionPoolSize(redisConnectionPoolMaxSize);
-
-        serverConfig.setDatabase(redisDatabase);
-        serverConfig.setPassword(redisPassword);
-        serverConfig.setConnectTimeout(redisConnectTimeout);
-        serverConfig.setIdleConnectionTimeout(redisConnectionIdleTimeout);
-        serverConfig.setPingConnectionInterval(redisConnectionPingInterval);
-        serverConfig.setTimeout(timeout);
-        serverConfig.setRetryAttempts(redisRetryAttempts);
-        serverConfig.setRetryInterval(redisRetryInterval);
-
-        redissonConfig.setCodec(new JsonJacksonCodec());
-        return redissonConfig;
-    }
-}
            
-
          • Redis Cluster
            import java.util.List;
-
+
          • Redis Cluster
            import org.redisson.Redisson;
+import org.redisson.api.RedissonClient;
 import org.redisson.codec.JsonJacksonCodec;
 import org.redisson.config.ClusterServersConfig;
 import org.redisson.config.Config;
 import org.redisson.config.ReadMode;
 import org.redisson.config.SubscriptionMode;
-import org.redisson.spring.data.connection.RedissonConnectionFactory;
 import org.springframework.beans.factory.annotation.Value;
 import org.springframework.context.annotation.Bean;
 import org.springframework.context.annotation.Configuration;
 
+import java.util.List;
+
 @Configuration
-public class RedisConfiguration {
+public class ClusterConfig {
 
     @Value("${redis.cluster.address}")
     private List<String> redisClusterAddress;
@@ -296,14 +226,9 @@ public class RedisConfiguration {
 
     @Value("${redis.master.connection.pool.max.size:200}")
     private Integer redisMasterConnectionPoolMaxSize = 200;
-    
-    @Bean
-    public RedissonConnectionFactory redissonConnectionFactory(Config redissonClusterServersConfig) {
-        return new RedissonConnectionFactory(redissonClusterServersConfig);
-    }
 
     @Bean
-    public Config redissonClusterServersConfig() {
+    public RedissonClient redissonClient() {
         Config redissonConfig = new Config();
 
         ClusterServersConfig serverConfig = redissonConfig.useClusterServers();
@@ -326,7 +251,7 @@ public class RedisConfiguration {
         serverConfig.setRetryInterval(redisRetryInterval);
 
         redissonConfig.setCodec(new JsonJacksonCodec());
-        return redissonConfig;
+        return Redisson.create(redissonConfig);
     }
 }
            
 
          
@@ -400,7 +325,7 @@ public class RedisConfiguration {
 
      
 
      
 
-
      Table 2 SingleServerConfig parameters (single-node)
      Parameter
      
+
      
@@ -412,7 +337,7 @@ public class RedisConfiguration {
 
-
      Table 2 SingleServerConfig parameters (single-node, or Proxy Cluster)
      Parameter
      
       		
 
      Default Value
      
       		
 
      -
      
 
      Node connection information, in ip:port format.
      
+
      Node connection information, in redis://ip:port format.
      
       		
 
      
 
      database
      
@@ -510,7 +435,7 @@ public class RedisConfiguration {
 
      
 
      
 
-
      Table 3 MasterSlaveServersConfig parameters (master/standby and Proxy Cluster)
      Parameter
      
+
      
@@ -522,14 +447,14 @@ public class RedisConfiguration {
 
-
-
-
      Table 3 MasterSlaveServersConfig parameters (master/standby)
      Parameter
      
       		
 
      Default Value
      
       		
 
      -
      
 
      Master node connection information, in ip:port format.
      
+
      Master node connection information, in redis://ip:port format.
      
       		
 
      
 
      slaveAddresses
      
       		
 
      -
      
 
      List of replica connection information: Set<ip:port>
      
+
      Standby node connection information, in Set<redis://ip:port> format.
      
       		
 
      
 
      readMode
      
@@ -667,7 +592,7 @@ public class RedisConfiguration {
       		
 
      -
      
 
      Connection addresses of cluster nodes. Each address uses the ip:port format. Use commas (,) to separate connection addresses of different nodes.
      
+
      Connection addresses of cluster nodes. Each address uses the redis://ip:port format. Use commas (,) to separate connection addresses of different nodes.
      
       		
 
      
 
      password
      
diff --git a/docs/dcs/umn/dcs-ug-211202002.html b/docs/dcs/umn/dcs-ug-211202002.html
index f3e396238..8b5dcee3a 100644
--- a/docs/dcs/umn/dcs-ug-211202002.html
+++ b/docs/dcs/umn/dcs-ug-211202002.html
@@ -7,20 +7,20 @@
 
      Procedure
      1. View the IP address/domain name and port number of the DCS Redis instance to be accessed.
        For details, see Viewing Details of a DCS Instance.
        
 
      2. Log in to the ECS.
      3. Install the PHP development package and CLI tool. Run the following yum command:
        yum install php-devel php-common php-cli
        
 
      4. After the installation is complete, check the version number to ensure that the installation is successful.
        php --version
        
-
      5. Download the Predis package to the /usr/share/php directory.
        1. Run the following command to download the Predis source file:
          wget https://github.com/predis/predis/archive/refs/tags/v1.1.10.tar.gz
          
+
        2. Download the Predis package to the /usr/share/php directory.
          1. Run the following command to download the Predis source file:
            wget https://github.com/predis/predis/archive/refs/tags/v2.2.2.tar.gz
            
 
             
            This version is used as an example. To download Predis clients of other versions, visit the Redis or PHP official website.
            
 
            
-
          2. Run the following commands to decompress the source Predis package:
            tar -zxvf predis-1.1.10.tar.gz
            
-
          3. Rename the decompressed Predis directory predis and move it to /usr/share/php/.
            mv predis-1.1.10 predis
            
+
          4. Run the following commands to decompress the source Predis package:
            tar -zxvf predis-2.2.2.tar.gz
            
+
          5. Rename the decompressed Predis directory predis and move it to /usr/share/php/.
            mv predis-2.2.2 predis
            
 
          
 
        3. Edit a file used to connect to Redis.
          • Example of using redis.php to connect to a single-node, master/standby, or Proxy Cluster DCS Redis instance:
            <?php
     require 'predis/autoload.php';
     Predis\Autoloader::register();
     $client = new Predis\Client([
       'scheme' => 'tcp' ,
-      'host'     => '{redis_instance_address}' ,
-      'port'     => {port} ,
-      'password' => '{password}' 
+      'host'     => '{redis_instance_address}' ,
+      'port'     =>{port} ,
+      'password' => '{password}' 
     ]);
     $client->set('foo', 'bar');
     $value = $client->get('foo');
@@ -29,7 +29,7 @@
 
          • Example code for using redis-cluster.php to connect to Redis Cluster:
            <?php
    require 'predis/autoload.php';
         $servers = array(
-         'tcp://{redis_instance_address}:{port}' 
+         'tcp://{redis_instance_address}:{port}' 
         );
        $options = array('cluster' => 'redis');
        $client = new Predis\Client($servers, $options);
@@ -38,7 +38,7 @@
        echo $value;
 ?>
            
 
          
-
          {redis_instance_address} indicates the actual IP address/domain name of the DCS instance and {port} is the actual port number of DCS instance. For details about how to obtain the IP address/domain name and port, see 1. Change them as required. {password} indicates the password used to log in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation. If password-free access is required, delete the line that contains "password".
          
+
          {redis_instance_address} indicates the actual IP address/domain name of the DCS instance and {port} is the actual port number of DCS instance. For details about how to obtain the IP address/domain name and port, see 1. Change them as required. {password} indicates the password used to log in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation. If password-free access is required, delete the line that contains "password".
          
 
        4. Run the php redis.php command to access the DCS instance.
        
 
      
 
diff --git a/docs/dcs/umn/en-us_image_0000001673542781.png b/docs/dcs/umn/en-us_image_0000001805332909.png
similarity index 100%
rename from docs/dcs/umn/en-us_image_0000001673542781.png
rename to docs/dcs/umn/en-us_image_0000001805332909.png
diff --git a/docs/dcs/umn/en-us_image_0266235403.png b/docs/dcs/umn/en-us_image_0266235403.png
deleted file mode 100644
index 24952ad78..000000000
Binary files a/docs/dcs/umn/en-us_image_0266235403.png and /dev/null differ
diff --git a/docs/dcs/umn/en-us_image_0266315618.png b/docs/dcs/umn/en-us_image_0266315618.png
index a223f3735..c24a2e2b0 100644
Binary files a/docs/dcs/umn/en-us_image_0266315618.png and b/docs/dcs/umn/en-us_image_0266315618.png differ