diff --git a/docs/dcs/umn/.placeholder b/docs/dcs/umn/.placeholder deleted file mode 100644 index e69de29bb..000000000 diff --git a/docs/dcs/umn/ALL_META.TXT.json b/docs/dcs/umn/ALL_META.TXT.json index 7716c0595..6bec8f498 100644 --- a/docs/dcs/umn/ALL_META.TXT.json +++ b/docs/dcs/umn/ALL_META.TXT.json @@ -43,7 +43,7 @@ "uri":"CacheSingleNode.html", "product_code":"dcs", "code":"5", - "des":"Three Redis versions are available for single-node DCS Redis instances: Redis 3.0, Redis 4.0, and Redis 5.0.Low system overhead and high QPSSingle-node instances do not s", + "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", "doc_type":"usermanual", "kw":"Single-Node Redis,DCS Instance Types,User Guide", "title":"Single-Node Redis", @@ -53,7 +53,7 @@ "uri":"CacheMasterSlave.html", "product_code":"dcs", "code":"6", - "des":"This section describes master/standby DCS Redis instances. Three Redis versions are available for master/standby DCS Redis instances: Redis 3.0, Redis 4.0, and Redis 5.0.", + "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", "doc_type":"usermanual", "kw":"Master/Standby Redis,DCS Instance Types,User Guide", "title":"Master/Standby Redis", @@ -63,7 +63,7 @@ "uri":"CacheCluster.html", "product_code":"dcs", "code":"7", - "des":"DCS provides two types of cluster Redis instances: Proxy Cluster and Redis Cluster. Proxy Cluster uses Linux Virtual Server (LVS) and proxies. Redis Cluster is the native", + "des":"DCS for Redis provides Proxy Cluster instances, which use Linux Virtual Server (LVS) and proxies to achieve high availability.Proxy Cluster DCS Redis instances are compat", "doc_type":"usermanual", "kw":"Proxy Cluster Redis,DCS Instance Types,User Guide", "title":"Proxy Cluster Redis", @@ -73,16 +73,26 @@ "uri":"CacheProxy.html", "product_code":"dcs", "code":"8", - "des":"This section describes Redis Cluster DCS Redis 4.0 and 5.0 instances.The Redis Cluster instance type provided by DCS is compatible with the native Redis Cluster, which us", + "des":"Redis Cluster DCS instances use the native distributed implementation of Redis.Redis Cluster DCS instances are compatible with Redis 4.0 and 5.0.The Redis Cluster instanc", "doc_type":"usermanual", "kw":"Redis Cluster,DCS Instance Types,User Guide", "title":"Redis Cluster", "githuburl":"" }, + { + "uri":"dcs-pd-191224001.html", + "product_code":"", + "code":"9", + "des":"Table 1 describes the differences between different Redis instance types in terms of features and commands.", + "doc_type":"", + "kw":"Comparing DCS Redis Instance Types,DCS Instance Types,User Guide", + "title":"Comparing DCS Redis Instance Types", + "githuburl":"" + }, { "uri":"en-us_topic_0054235835.html", "product_code":"dcs", - "code":"9", + "code":"10", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"DCS Instance Specifications", @@ -92,7 +102,7 @@ { "uri":"dcs-pd-0916001.html", "product_code":"dcs", - "code":"10", + "code":"11", "des":"This section describes DCS Redis 3.0 instance specifications, including the total memory, available memory, maximum number of connections allowed, maximum/assured bandwid", "doc_type":"usermanual", "kw":"DCS Redis 3.0 instance specifications,Redis 3.0 Instance Specifications,DCS Instance Specifications,", @@ -102,17 +112,27 @@ { "uri":"dcs-pd-0916002.html", "product_code":"dcs", - "code":"11", + "code":"12", "des":"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", "doc_type":"usermanual", "kw":"DCS Redis 4.0 and 5.0 instance specifications,Redis 4.0 and 5.0 Instance Specifications,DCS Instance", "title":"Redis 4.0 and 5.0 Instance Specifications", "githuburl":"" }, + { + "uri":"dcs-pd-0916004.html", + "product_code":"", + "code":"13", + "des":"This section describes DCS Redis 6.0 instance specifications, including the total memory, available memory, maximum number of connections allowed, maximum/assured bandwid", + "doc_type":"", + "kw":"DCS Redis 6.0 instance specifications,Redis 6.0 Instance Specifications,DCS Instance Specifications,", + "title":"Redis 6.0 Instance Specifications", + "githuburl":"" + }, { "uri":"dcs-pd-200312003.html", "product_code":"dcs", - "code":"12", + "code":"14", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Command Compatibility", @@ -122,7 +142,7 @@ { "uri":"dcs-pd-200713005.html", "product_code":"dcs", - "code":"13", + "code":"15", "des":"DCS for Redis 3.0 is developed based on Redis 3.0.7 and is compatible with open-source protocols and commands.This section describes DCS for Redis 3.0's compatibility wit", "doc_type":"usermanual", "kw":"Redis 3.0 Commands,Command Compatibility,User Guide", @@ -132,7 +152,7 @@ { "uri":"dcs-pd-200916001.html", "product_code":"dcs", - "code":"14", + "code":"16", "des":"DCS for Redis 4.0 is developed based on Redis 4.0.14 and is compatible with open-source protocols and commands.This section describes DCS for Redis 4.0's compatibility wi", "doc_type":"usermanual", "kw":"Redis 4.0 Commands,Command Compatibility,User Guide", @@ -142,17 +162,27 @@ { "uri":"dcs-pd-200813002.html", "product_code":"dcs", - "code":"15", + "code":"17", "des":"DCS for Redis 5.0 is developed based on Redis 5.0.9 and is compatible with open-source protocols and commands.This section describes DCS for Redis 5.0's compatibility wit", "doc_type":"usermanual", "kw":"Redis 5.0 Commands,Command Compatibility,User Guide", "title":"Redis 5.0 Commands", "githuburl":"" }, + { + "uri":"dcs-pd-210209002.html", + "product_code":"", + "code":"18", + "des":"DCS for Redis 6.0 is compatible with Redis 6.2.7 and with open-source protocols and commands.This section describes DCS for Redis 6.0's command compatibility, including s", + "doc_type":"", + "kw":"Redis 6.0 Commands,Command Compatibility,User Guide", + "title":"Redis 6.0 Commands", + "githuburl":"" + }, { "uri":"dcs-pd-190826001.html", "product_code":"dcs", - "code":"16", + "code":"19", "des":"Web CLI is a command line tool provided on the DCS console. This section describes Web CLI's compatibility with Redis commands, including supported and disabled commands.", "doc_type":"usermanual", "kw":"Web CLI Commands,Command Compatibility,User Guide", @@ -162,17 +192,17 @@ { "uri":"dcs-pd-200813003.html", "product_code":"dcs", - "code":"17", + "code":"20", "des":"Some Redis commands are supported by cluster DCS instances for multi-key operations in the same slot. For details, see Table 1.While running commands that take a long tim", "doc_type":"usermanual", - "kw":"Command Restrictions for Cluster Instances,Command Compatibility,User Guide", - "title":"Command Restrictions for Cluster Instances", + "kw":"Command Restrictions,Command Compatibility,User Guide", + "title":"Command Restrictions", "githuburl":"" }, { "uri":"dcs-pd-200813004.html", "product_code":"dcs", - "code":"18", + "code":"21", "des":"This section describes restrictions on some Redis commands.In case of a large amount of cached data, running the KEYS command may block the execution of other commands fo", "doc_type":"usermanual", "kw":"Other Command Usage Restrictions,Command Compatibility,User Guide", @@ -182,18 +212,18 @@ { "uri":"GlobalDRPolicy.html", "product_code":"dcs", - "code":"19", + "code":"22", "des":"Whether you use DCS as the frontend cache or backend data store, DCS is always ready to ensure data reliability and service availability. The following figure shows the e", "doc_type":"usermanual", - "kw":"HA and DR Policies,Service Overview,User Guide", - "title":"HA and DR Policies", + "kw":"Disaster Recovery and Multi-Active Solution,Service Overview,User Guide", + "title":"Disaster Recovery and Multi-Active Solution", "githuburl":"" }, { "uri":"RedisDifference.html", "product_code":"dcs", - "code":"20", - "des":"When creating a DCS Redis instance, you can select the cache engine version and the instance type.VersionDCS supports Redis 3.0, 4.0, and 5.0. The following table describ", + "code":"23", + "des":"When creating a DCS Redis instance, you can select the cache engine version and the instance type.VersionDCS supports Redis 3.0/4.0/5.0/6.0. The following table describes", "doc_type":"usermanual", "kw":"Comparing Redis Versions,Service Overview,User Guide", "title":"Comparing Redis Versions", @@ -202,7 +232,7 @@ { "uri":"dcs-pd-0326003.html", "product_code":"dcs", - "code":"21", + "code":"24", "des":"DCS supports single-node, master/standby, and cluster instances, ensuring high read/write performance and fast data access. It also supports various instance management o", "doc_type":"usermanual", "kw":"Comparing DCS and Open-Source Cache Services,Service Overview,User Guide", @@ -212,8 +242,8 @@ { "uri":"dcs-pd-200312004.html", "product_code":"dcs", - "code":"22", - "des":"An instance is the minimum resource unit provided by DCS.DCS supports the Redis cache engine, and single-node, master/standby, and cluster instance types. For each instan", + "code":"25", + "des":"An instance is the minimum resource unit provided by DCS.For details, see DCS Instance Specifications and DCS Instance Types.Projects are used to group and isolate OpenSt", "doc_type":"usermanual", "kw":"Basic Concepts,Service Overview,User Guide", "title":"Basic Concepts", @@ -222,17 +252,17 @@ { "uri":"dcs-pd-210626001.html", "product_code":"dcs", - "code":"23", + "code":"26", "des":"If you need to assign different permissions to employees in your enterprise to access your DCS resources, Identity and Access Management (IAM) is a good choice for fine-g", "doc_type":"usermanual", - "kw":"Permissions Management,Service Overview,User Guide", - "title":"Permissions Management", + "kw":"Permissions,Service Overview,User Guide", + "title":"Permissions", "githuburl":"" }, { "uri":"dcs-pd-0326006.html", "product_code":"dcs", - "code":"24", + "code":"27", "des":"DCS is used together with other services, including VPC, ECS, IAM, Cloud Eye, CTS, and Object Storage Service (OBS).A VPC is an isolated virtual network environment on th", "doc_type":"usermanual", "kw":"Related Services,Service Overview,User Guide", @@ -242,7 +272,7 @@ { "uri":"en-us_topic_0054235836.html", "product_code":"dcs", - "code":"25", + "code":"28", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Accessing DCS", @@ -252,7 +282,7 @@ { "uri":"en-us_topic_0054235837.html", "product_code":"dcs", - "code":"26", + "code":"29", "des":"There are two ways to access DCS:Using the management consoleThe DCS provides a web-based management console. To launch the DCS console, create an account on the manageme", "doc_type":"usermanual", "kw":"How to Access DCS,Accessing DCS,User Guide", @@ -262,7 +292,7 @@ { "uri":"en-us_topic_0054247786.html", "product_code":"dcs", - "code":"27", + "code":"30", "des":"The public cloud system provides two types of user permissions by default: user management and resource management.User management refers to the management of users, user", "doc_type":"usermanual", "kw":"User Permissions,Accessing DCS,User Guide", @@ -272,7 +302,7 @@ { "uri":"dcs-ug-210626003.html", "product_code":"dcs", - "code":"28", + "code":"31", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Permissions Management", @@ -282,7 +312,7 @@ { "uri":"dcs-ug-210626004.html", "product_code":"dcs", - "code":"29", + "code":"32", "des":"This chapter describes how to use IAM to implement fine-grained permissions control for your DCS resources. With IAM, you can:Create IAM users for employees based on your", "doc_type":"usermanual", "kw":"Creating a User and Granting DCS Permissions,Permissions Management,User Guide", @@ -292,8 +322,8 @@ { "uri":"dcs-ug-210626005.html", "product_code":"dcs", - "code":"30", - "des":"Custom policies can be created to supplement the system-defined policies of DCS. For the actions that can be added for custom policies, see Permissions Policies and Suppo", + "code":"33", + "des":"Custom policies can be created to supplement the system-defined policies of DCS. For the actions that can be added to custom policies, see section \"Permissions Policies a", "doc_type":"usermanual", "kw":"DCS Custom Policies,Permissions Management,User Guide", "title":"DCS Custom Policies", @@ -302,7 +332,7 @@ { "uri":"dcs-ug-0326007.html", "product_code":"dcs", - "code":"31", + "code":"34", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Getting Started", @@ -312,7 +342,7 @@ { "uri":"dcs-ug-0312003.html", "product_code":"dcs", - "code":"32", + "code":"35", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Creating an Instance", @@ -322,7 +352,7 @@ { "uri":"PurchasePreparation.html", "product_code":"dcs", - "code":"33", + "code":"36", "des":"Before creating a DCS instance, identify your requirements and complete the following preparations:Decide on the required cache engine version.Different Redis versions ha", "doc_type":"usermanual", "kw":"Identifying Requirements,Creating an Instance,User Guide", @@ -332,17 +362,17 @@ { "uri":"dcs-ug-0312004.html", "product_code":"dcs", - "code":"34", + "code":"37", "des":"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 ", "doc_type":"usermanual", - "kw":"Preparing the Environment,Creating an Instance,User Guide", - "title":"Preparing the Environment", + "kw":"Preparing Required Resources,Creating an Instance,User Guide", + "title":"Preparing Required Resources", "githuburl":"" }, { "uri":"dcs-ug-0326008.html", "product_code":"dcs", - "code":"35", + "code":"38", "des":"You can create one or more DCS Redis instances with the required computing capabilities and storage space based on service requirements.The system automatically schedules", "doc_type":"usermanual", "kw":"Creating a DCS Redis Instance,Creating an Instance,User Guide", @@ -352,7 +382,7 @@ { "uri":"dcs-ug-0916002.html", "product_code":"dcs", - "code":"36", + "code":"39", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Accessing an Instance", @@ -362,7 +392,7 @@ { "uri":"dcs-ug-0326009.html", "product_code":"dcs", - "code":"37", + "code":"40", "des":"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 ", "doc_type":"usermanual", "kw":"Accessing a DCS Redis Instance Through redis-cli,Accessing an Instance,User Guide", @@ -372,7 +402,7 @@ { "uri":"dcs-ug-0512002.html", "product_code":"", - "code":"38", + "code":"41", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"", "kw":"Access in Different Languages", @@ -382,7 +412,7 @@ { "uri":"dcs-ug-211105003.html", "product_code":"dcs", - "code":"39", + "code":"42", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Java", @@ -392,27 +422,27 @@ { "uri":"dcs-ug-0713005.html", "product_code":"dcs", - "code":"40", - "des":"Access a DCS Redis instance through Jedis on an ECS in the same VPC. For more information on how to use other Redis clients, visit https://redis.io/clients.If a password ", + "code":"43", + "des":"Access a DCS Redis instance through Jedis on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis official website.A DCS Red", "doc_type":"usermanual", "kw":"Access a DCS Redis instance through Jedis,Jedis,Java,User Guide", "title":"Jedis", "githuburl":"" }, { - "uri":"dcs-ug-211011001.html", + "uri":"dcs-ug-211105002.html", "product_code":"dcs", - "code":"41", - "des":"Access a Redis Cluster instance through Lettuce on an ECS in the same VPC. For more information on how to use other Redis clients, visit https://redis.io/clients.If a pas", + "code":"44", + "des":"Access a DCS Redis instance through Lettuce on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis official website.A DCS R", "doc_type":"usermanual", - "kw":"Access a Redis Cluster instance through Lettuce,Lettuce,Java,User Guide", + "kw":"Access a DCS Redis instance through Lettuce,Lettuce,Java,User Guide", "title":"Lettuce", "githuburl":"" }, { "uri":"dcs-ug-211105004.html", "product_code":"dcs", - "code":"42", + "code":"45", "des":"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.If a p", "doc_type":"usermanual", "kw":"Access a DCS Redis instance through Redisson,Redisson,Java,User Guide", @@ -422,7 +452,7 @@ { "uri":"dcs-ug-211203001.html", "product_code":"dcs", - "code":"43", + "code":"46", "des":"A DCS Redis instance has been created and is in the Running state.An ECS has been created. For details about how to create an ECS, see Elastic Cloud Server User Guide.If ", "doc_type":"usermanual", "kw":"Lettuce Integration with Spring Boot,Access in Different Languages,User Guide", @@ -432,7 +462,7 @@ { "uri":"dcs-ug-0312011.html", "product_code":"dcs", - "code":"44", + "code":"47", "des":"Access a DCS Redis instance through redis-py on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis official website.Use re", "doc_type":"usermanual", "kw":"redis-py,Clients in Python,Access in Different Languages,User Guide", @@ -442,7 +472,7 @@ { "uri":"dcs-ug-211105001.html", "product_code":"dcs", - "code":"45", + "code":"48", "des":"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.A DCS ", "doc_type":"usermanual", "kw":"Access a DCS Redis instance through go-redis,go-redis,Access in Different Languages,User Guide", @@ -452,7 +482,7 @@ { "uri":"dcs-ug-0312010.html", "product_code":"dcs", - "code":"46", + "code":"49", "des":"Access a DCS Redis instance through hiredis on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis official website.The ope", "doc_type":"usermanual", "kw":"Access a DCS Redis instance through hiredis,hiredis in C++,Access in Different Languages,User Guide", @@ -462,7 +492,7 @@ { "uri":"dcs-ug-0312013.html", "product_code":"dcs", - "code":"47", + "code":"50", "des":"Access a DCS Redis instance through C# Client StackExchange.Redis on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis of", "doc_type":"usermanual", "kw":"C# Client StackExchange.Redis,C#,Access in Different Languages,User Guide", @@ -472,7 +502,7 @@ { "uri":"dcs-ug-211202001.html", "product_code":"dcs", - "code":"48", + "code":"51", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"PHP", @@ -482,7 +512,7 @@ { "uri":"dcs-ug-0312009.html", "product_code":"dcs", - "code":"49", + "code":"52", "des":"Access a DCS Redis instance through phpredis on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis official website.The op", "doc_type":"usermanual", "kw":"Access a DCS Redis instance through phpredis,phpredis,PHP,User Guide", @@ -492,7 +522,7 @@ { "uri":"dcs-ug-211202002.html", "product_code":"dcs", - "code":"50", + "code":"53", "des":"Access a DCS Redis instance through Predis on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis official website.A DCS Re", "doc_type":"usermanual", "kw":"Access a DCS Redis instance through Predis,Predis,PHP,User Guide", @@ -502,7 +532,7 @@ { "uri":"dcs-ug-0312012.html", "product_code":"dcs", - "code":"51", + "code":"54", "des":"Access a DCS Redis instance through Node.js on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis official website.The ope", "doc_type":"usermanual", "kw":"Node.js,Node.js,Access in Different Languages,User Guide", @@ -512,37 +542,27 @@ { "uri":"dcs-ug-0312008.html", "product_code":"dcs", - "code":"52", - "des":"Access a DCS Redis instance through Web CLI. This function is supported only by DCS Redis 4.0 and 5.0 instances, and not by DCS Redis 3.0 instances.Do not enter sensitive", + "code":"55", + "des":"Access a DCS Redis instance through Web CLI. This function is supported only by DCS Redis 4.0 and later instances, and not by DCS Redis 3.0 instances.Do not enter sensiti", "doc_type":"usermanual", - "kw":"Access a DCS Redis,Web CLI,Accessing a DCS Redis 4.0 or 5.0 Instance on the Console,Accessing an Ins", - "title":"Accessing a DCS Redis 4.0 or 5.0 Instance on the Console", + "kw":"Access a DCS Redis,Web CLI,Accessing a DCS Redis 4.0/5.0/6.0 Instance on the Console,Accessing an In", + "title":"Accessing a DCS Redis 4.0/5.0/6.0 Instance on the Console", "githuburl":"" }, { "uri":"dcs-ug-0312016.html", "product_code":"dcs", - "code":"53", + "code":"56", "des":"On the DCS console, you can view DCS instance details.Search by keyword.Enter a keyword to search.Enter a keyword to search.Select attributes and enter their keywords to ", "doc_type":"usermanual", "kw":"view DCS,Viewing Details of a DCS Instance,Getting Started,User Guide", "title":"Viewing Details of a DCS Instance", "githuburl":"" }, - { - "uri":"dcs-ug-0326010.html", - "product_code":"dcs", - "code":"54", - "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "doc_type":"usermanual", - "kw":"Operation Guide", - "title":"Operation Guide", - "githuburl":"" - }, { "uri":"dcs-ug-0312015.html", "product_code":"dcs", - "code":"55", + "code":"57", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Operating DCS Instances", @@ -552,7 +572,7 @@ { "uri":"dcs-ug-0326011.html", "product_code":"dcs", - "code":"56", + "code":"58", "des":"On the DCS console, you can scale a DCS Redis instance to a larger or smaller capacity.Modify instance specifications during off-peak hours.If your DCS instances are too ", "doc_type":"usermanual", "kw":"Modifying DCS Instance Specifications,Operating DCS Instances,User Guide", @@ -562,7 +582,7 @@ { "uri":"dcs-ug-0911001.html", "product_code":"dcs", - "code":"57", + "code":"59", "des":"On the DCS console, you can start one or multiple DCS instances at a time.This function is not supported by recent instances. You can only start old instances that have b", "doc_type":"usermanual", "kw":"Starting DCS Instances,Operating DCS Instances,User Guide", @@ -572,7 +592,7 @@ { "uri":"dcs-ug-0326013.html", "product_code":"dcs", - "code":"58", + "code":"60", "des":"On the DCS console, you can restart one or multiple DCS instances at a time.After a single-node DCS instance is restarted, data will be deleted from the instance.While a ", "doc_type":"usermanual", "kw":"restart one or multiple DCS instances,Restarting DCS Instances,Operating DCS Instances,User Guide", @@ -582,7 +602,7 @@ { "uri":"dcs-ug-0326014.html", "product_code":"dcs", - "code":"59", + "code":"61", "des":"On the DCS console, you can delete one or multiple DCS instances at a time. You can also delete all instance creation tasks that have failed to run.After a DCS instance i", "doc_type":"usermanual", "kw":"delete one or multiple DCS instances,Deleting DCS Instances,Operating DCS Instances,User Guide", @@ -592,7 +612,7 @@ { "uri":"dcs-ug-0312017.html", "product_code":"dcs", - "code":"60", + "code":"62", "des":"On the DCS console, you can manually switch the master and standby nodes of a DCS instance. This operation is used for special purposes, for example, releasing all servic", "doc_type":"usermanual", "kw":"Performing a Master/Standby Switchover for a DCS Instance,Operating DCS Instances,User Guide", @@ -602,8 +622,8 @@ { "uri":"dcs-ug-0312018.html", "product_code":"dcs", - "code":"61", - "des":"On the DCS console, you can clear data only for DCS Redis 4.0 and 5.0 instances.Clearing instance data cannot be undone and cleared data cannot be recovered. Exercise cau", + "code":"63", + "des":"You can clear data of DCS Redis 4.0 and later instances on the console.Clearing instance data cannot be undone and cleared data cannot be recovered. Exercise caution when", "doc_type":"usermanual", "kw":"clear data,Clearing DCS Instance Data,Operating DCS Instances,User Guide", "title":"Clearing DCS Instance Data", @@ -612,8 +632,8 @@ { "uri":"dcs-ug-0312019.html", "product_code":"dcs", - "code":"62", - "des":"On the DCS console, you can export DCS instance information in full to an Excel file.Click the export result displayed in the lower left corner of the page.", + "code":"64", + "des":"On the DCS console, you can export DCS instance information in full to an Excel file.", "doc_type":"usermanual", "kw":"Exporting DCS Instance List,Operating DCS Instances,User Guide", "title":"Exporting DCS Instance List", @@ -622,8 +642,8 @@ { "uri":"dcs-ug-1009002.html", "product_code":"dcs", - "code":"63", - "des":"After creating a DCS Redis 4.0 or 5.0 instance, you can rename the following critical commands: COMMAND, KEYS, FLUSHDB, FLUSHALL, and HGETALL.You can rename multiple comm", + "code":"65", + "des":"After creating a DCS Redis 4.0 or later instance, you can rename the following critical commands: Currently, you can only rename the COMMAND, KEYS, FLUSHDB, and FLUSHALL ", "doc_type":"usermanual", "kw":"Command Renaming,Operating DCS Instances,User Guide", "title":"Command Renaming", @@ -632,7 +652,7 @@ { "uri":"dcs-ug-0312022.html", "product_code":"dcs", - "code":"64", + "code":"66", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Managing DCS Instances", @@ -642,7 +662,7 @@ { "uri":"dcs-ug-0312023.html", "product_code":"dcs", - "code":"65", + "code":"67", "des":"In most cases, different DCS instance management operations cannot proceed concurrently. If you initiate a new management operation while the current operation is in prog", "doc_type":"usermanual", "kw":"Configuration Notice,Managing DCS Instances,User Guide", @@ -652,7 +672,7 @@ { "uri":"dcs-ug-0312024.html", "product_code":"dcs", - "code":"66", + "code":"68", "des":"You can modify the configuration parameters of your DCS instance to optimize DCS performance based on your requirements.For example, if you do not need data persistence, ", "doc_type":"usermanual", "kw":"Modifying Configuration Parameters,Managing DCS Instances,User Guide", @@ -662,7 +682,7 @@ { "uri":"dcs-ug-0312025.html", "product_code":"dcs", - "code":"67", + "code":"69", "des":"On the DCS console, after creating a DCS instance, you can modify the maintenance time window of the DCS instance on the instance's Basic Information page.At least one DC", "doc_type":"usermanual", "kw":"modify the maintenance time window,Modifying Maintenance Time Window,Managing DCS Instances,User Gui", @@ -672,7 +692,7 @@ { "uri":"dcs-ug-0312026.html", "product_code":"dcs", - "code":"68", + "code":"70", "des":"On the DCS console, after creating a DCS instance, you can modify the security group of the DCS instance on the instance's Basic Information page.You can modify the secur", "doc_type":"usermanual", "kw":"modify the security group,Modifying the Security Group,Managing DCS Instances,User Guide", @@ -682,7 +702,7 @@ { "uri":"dcs-ug-0312028.html", "product_code":"dcs", - "code":"69", + "code":"71", "des":"After you initiate certain instance operations such as modifying instance specifications and changing or resetting a password, a background task will start for the operat", "doc_type":"usermanual", "kw":"Viewing Background Tasks,Managing DCS Instances,User Guide", @@ -692,7 +712,7 @@ { "uri":"dcs-ug-0312029.html", "product_code":"dcs", - "code":"70", + "code":"72", "des":"You can view the data storage statistics of all nodes of a DCS Redis 3.0 Proxy Cluster instance. If data storage is unevenly distributed across nodes, you can scale up th", "doc_type":"usermanual", "kw":"Viewing Data Storage Statistics of a DCS Redis 3.0 Proxy Cluster Instance,Managing DCS Instances,Use", @@ -702,8 +722,8 @@ { "uri":"dcs-ug-210107001.html", "product_code":"", - "code":"71", - "des":"This section describes how to query the shards and replicas of a DCS Redis 4.0 or 5.0 instance and how to manually promote a replica to master.Currently, this function is", + "code":"73", + "des":"This section describes how to query the shards and replicas of a DCS Redis 4.0/5.0/6.0 instance and how to manually promote a replica to master.Currently, this function i", "doc_type":"", "kw":"Managing Shards and Replicas,Managing DCS Instances,User Guide", "title":"Managing Shards and Replicas", @@ -712,18 +732,18 @@ { "uri":"dcs-ug-190808001.html", "product_code":"dcs", - "code":"72", + "code":"74", "des":"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", "doc_type":"usermanual", - "kw":"Cache Analysis,Managing DCS Instances,User Guide", - "title":"Cache Analysis", + "kw":"Analyzing Big Keys and Hot Keys,Managing DCS Instances,User Guide", + "title":"Analyzing Big Keys and Hot Keys", "githuburl":"" }, { "uri":"dcs-ug-190812001.html", "product_code":"dcs", - "code":"73", - "des":"DCS helps you control access to your DCS instances in the following ways, depending on the deployment mode:To control access to Redis 3.0 instances, you can use security ", + "code":"75", + "des":"DCS helps you control access to your DCS instances in the following ways, depending on the deployment mode:To control access to DCS Redis 3.0 instances, you can use secur", "doc_type":"usermanual", "kw":"Managing IP Address Whitelist,Managing DCS Instances,User Guide", "title":"Managing IP Address Whitelist", @@ -732,27 +752,37 @@ { "uri":"dcs-ug-190926001.html", "product_code":"dcs", - "code":"74", + "code":"76", "des":"Redis logs queries that exceed a specified execution time. You can view the slow query log on the DCS console to identify performance issues.For details about the command", "doc_type":"usermanual", - "kw":"Viewing Redis Slow Logs,Managing DCS Instances,User Guide", - "title":"Viewing Redis Slow Logs", + "kw":"Viewing Redis Slow Queries,Managing DCS Instances,User Guide", + "title":"Viewing Redis Slow Queries", "githuburl":"" }, { "uri":"dcs-ug-1009001.html", "product_code":"dcs", - "code":"75", + "code":"77", "des":"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 l", "doc_type":"usermanual", "kw":"Viewing Redis Run Logs,Managing DCS Instances,User Guide", "title":"Viewing Redis Run Logs", "githuburl":"" }, + { + "uri":"dcs-ug-023129.html", + "product_code":"", + "code":"78", + "des":"DCS Redis 6.0instances support SSL encryption to ensure data transmission security. This function is not available for other instance versions. RESP (REdis Serialization ", + "doc_type":"", + "kw":"Configuring SSL,Managing DCS Instances,User Guide", + "title":"Configuring SSL", + "githuburl":"" + }, { "uri":"dcs-ug-0312030.html", "product_code":"dcs", - "code":"76", + "code":"79", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Backing Up and Restoring DCS Instances", @@ -762,7 +792,7 @@ { "uri":"en-us_topic_0079835992.html", "product_code":"dcs", - "code":"77", + "code":"80", "des":"On the DCS console, you can back up and restore DCS instances.There is a small chance that inconsistent data could exist in a DCS instance owing to service system excepti", "doc_type":"usermanual", "kw":"back up,restore,Overview,Backing Up and Restoring DCS Instances,User Guide", @@ -772,17 +802,17 @@ { "uri":"dcs-ug-0312031.html", "product_code":"dcs", - "code":"78", - "des":"On the DCS console, you can configure an automatic backup policy. The system then backs up data in your instances according to the backup policy.If automatic backup is no", + "code":"81", + "des":"On the DCS console, you can configure an automatic backup policy. The system then backs up data in your instances according to the backup policy.By default, automatic bac", "doc_type":"usermanual", - "kw":"configure an automatic backup policy,Configuring a Backup Policy,Backing Up and Restoring DCS Instan", - "title":"Configuring a Backup Policy", + "kw":"configure an automatic backup policy,Configuring an Automatic Backup Policy,Backing Up and Restoring", + "title":"Configuring an Automatic Backup Policy", "githuburl":"" }, { "uri":"dcs-ug-0312032.html", "product_code":"dcs", - "code":"79", + "code":"82", "des":"You need to manually back up data in DCS instances in a timely manner. This section describes how to manually back up data in master/standby instances using the DCS conso", "doc_type":"usermanual", "kw":"manually back up data,Manually Backing Up a DCS Instance,Backing Up and Restoring DCS Instances,User", @@ -792,7 +822,7 @@ { "uri":"dcs-ug-0312033.html", "product_code":"dcs", - "code":"80", + "code":"83", "des":"On the DCS console, you can restore backup data to a chosen DCS instance.At least one master/standby or cluster DCS instance is in the Running state.A backup task has bee", "doc_type":"usermanual", "kw":"restore backup data,Restoring a DCS Instance,Backing Up and Restoring DCS Instances,User Guide", @@ -802,8 +832,8 @@ { "uri":"dcs-ug-0312034.html", "product_code":"dcs", - "code":"81", - "des":"Due to the limitations of automatic and manual backups (automatically backed up data can be retained for a maximum of 7 days, and manually backed up data takes space in O", + "code":"84", + "des":"Automatically backed up data can be retained for a maximum of 7 days. Manually backed up data is not free of charge and takes space in OBS. Due to these limitations, you ", "doc_type":"usermanual", "kw":"Downloading a Backup File,Backing Up and Restoring DCS Instances,User Guide", "title":"Downloading a Backup File", @@ -812,7 +842,7 @@ { "uri":"dcs-ug-0312035.html", "product_code":"dcs", - "code":"82", + "code":"85", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Migrating Data with DCS", @@ -822,8 +852,8 @@ { "uri":"dcs-ug-0312036.html", "product_code":"dcs", - "code":"83", - "des":"DCS for Redis provides the following migration modes:Backup file import: The data source can be an OBS bucket or a Redis instance.Importing data from an OBS bucket: Downl", + "code":"86", + "des":"DCS for Redis supports online migration (in full or incrementally) and backup migration (by importing backup files).Backup migration is suitable when the source and targe", "doc_type":"usermanual", "kw":"Introduction to Migration with DCS,Migrating Data with DCS,User Guide", "title":"Introduction to Migration with DCS", @@ -832,7 +862,7 @@ { "uri":"dcs-ug-210922001.html", "product_code":"dcs", - "code":"84", + "code":"87", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Importing Backup Files", @@ -842,7 +872,7 @@ { "uri":"dcs-ug-0312037.html", "product_code":"dcs", - "code":"85", + "code":"88", "des":"Use the DCS console to migrate Redis data from Redis of other vendors or self-hosted Redis to DCS for Redis.Simply download the source Redis data and then upload the data", "doc_type":"usermanual", "kw":"Importing Backup Files from an OBS Bucket,Importing Backup Files,User Guide", @@ -852,7 +882,7 @@ { "uri":"dcs-ug-210226001.html", "product_code":"dcs", - "code":"86", + "code":"89", "des":"Use the DCS console to migrate Redis data from self-hosted Redis to DCS for Redis.Simply back up your Redis data, create a migration task on the DCS console, and then imp", "doc_type":"usermanual", "kw":"Importing Backup Files from Redis,Importing Backup Files,User Guide", @@ -862,7 +892,7 @@ { "uri":"dcs-ug-0312038.html", "product_code":"dcs", - "code":"87", + "code":"90", "des":"If the source and target instances are interconnected and the SYNC and PSYNC commands are supported in the source instance, data can be migrated online in full or increme", "doc_type":"usermanual", "kw":"Migrating Data Online,Migrating Data with DCS,User Guide", @@ -872,7 +902,7 @@ { "uri":"dcs-ug-0312039.html", "product_code":"dcs", - "code":"88", + "code":"91", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Managing Passwords", @@ -882,7 +912,7 @@ { "uri":"cache-instance-password.html", "product_code":"dcs", - "code":"89", + "code":"92", "des":"Passwords can be configured to control access to your DCS instances, ensuring the security of your data.After 5 consecutive incorrect password attempts, the account for a", "doc_type":"usermanual", "kw":"DCS Instance Passwords,Managing Passwords,User Guide", @@ -892,17 +922,67 @@ { "uri":"dcs-ug-0312040.html", "product_code":"dcs", - "code":"90", + "code":"93", "des":"On the DCS console, you can change the password required for accessing your DCS instance.You cannot change the password of a DCS instance in password-free mode.The DCS in", "doc_type":"usermanual", "kw":"Changing Instance Passwords,Managing Passwords,User Guide", "title":"Changing Instance Passwords", "githuburl":"" }, + { + "uri":"dcs-ug-210622001.html", + "product_code":"dcs", + "code":"94", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Parameter Templates", + "title":"Parameter Templates", + "githuburl":"" + }, + { + "uri":"dcs-ug-210622002.html", + "product_code":"dcs", + "code":"95", + "des":"This section describes how to view parameter templates on the DCS console.Currently, you can enter a keyword in the search box to search for a parameter template by templ", + "doc_type":"usermanual", + "kw":"Viewing Parameter Templates,Parameter Templates,User Guide", + "title":"Viewing Parameter Templates", + "githuburl":"" + }, + { + "uri":"dcs-ug-210622003.html", + "product_code":"dcs", + "code":"96", + "des":"You can create custom parameter templates for different cache engine versions and instance types based on service requirements.If you select Default Templates, click Cust", + "doc_type":"usermanual", + "kw":"Creating a Custom Parameter Template,Parameter Templates,User Guide", + "title":"Creating a Custom Parameter Template", + "githuburl":"" + }, + { + "uri":"dcs-ug-210622004.html", + "product_code":"dcs", + "code":"97", + "des":"You can modify the name, description, and parameters of a custom parameter template based on service requirements.Click Edit in the Operation column.Change the name or mo", + "doc_type":"usermanual", + "kw":"Modifying a Custom Parameter Template,Parameter Templates,User Guide", + "title":"Modifying a Custom Parameter Template", + "githuburl":"" + }, + { + "uri":"dcs-ug-210622005.html", + "product_code":"dcs", + "code":"98", + "des":"This section describes how to delete a custom parameter template.", + "doc_type":"usermanual", + "kw":"Deleting a Custom Parameter Template,Parameter Templates,User Guide", + "title":"Deleting a Custom Parameter Template", + "githuburl":"" + }, { "uri":"dcs-ug-0326016.html", "product_code":"dcs", - "code":"91", + "code":"99", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Monitoring", @@ -912,7 +992,7 @@ { "uri":"dcs-ug-0326019.html", "product_code":"dcs", - "code":"92", + "code":"100", "des":"This section describes DCS metrics reported to Cloud Eye as well as their namespaces and dimensions. You can use the Cloud Eye console or call APIs to query the DCS metri", "doc_type":"usermanual", "kw":"DCS Metrics,Monitoring,User Guide", @@ -922,7 +1002,7 @@ { "uri":"dcs-ug-0312045.html", "product_code":"dcs", - "code":"93", + "code":"101", "des":"You can view DCS instance metrics on the Performance Monitoring page.You can also click View Metric in the Operation column on the Cache Manager page. You will be redirec", "doc_type":"usermanual", "kw":"Viewing DCS Monitoring Metrics,Monitoring,User Guide", @@ -932,7 +1012,7 @@ { "uri":"dcs-ug-190905001.html", "product_code":"dcs", - "code":"94", + "code":"102", "des":"This section describes the alarm rules of some metrics and how to configure the rules. In actual scenarios, configure alarm rules for metrics by referring to the followin", "doc_type":"usermanual", "kw":"Configuring Alarm Rules for Critical Metrics,Monitoring,User Guide", @@ -942,7 +1022,7 @@ { "uri":"dcs-ug-0326017.html", "product_code":"dcs", - "code":"95", + "code":"103", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Auditing", @@ -952,7 +1032,7 @@ { "uri":"dcs-ug-0326018.html", "product_code":"dcs", - "code":"96", + "code":"104", "des":"With CTS, you can query, audit, and review operations performed on cloud resources. Traces include the operation requests sent using the management console or open APIs a", "doc_type":"usermanual", "kw":"DCS operations that can be recorded by CTS,Operations That Can Be Recorded by CTS,Auditing,User Guid", @@ -962,7 +1042,7 @@ { "uri":"dcs-ug-0312047.html", "product_code":"dcs", - "code":"97", + "code":"105", "des":"After CTS is enabled, the tracker starts recording operations on cloud resources. Operation records for the last seven days can be viewed on the CTS console. This section", "doc_type":"usermanual", "kw":"Viewing Traces on the CTS Console,Auditing,User Guide", @@ -972,7 +1052,7 @@ { "uri":"dcs-faq-0326019.html", "product_code":"dcs", - "code":"98", + "code":"106", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"FAQs", @@ -982,7 +1062,7 @@ { "uri":"dcs-faq-0326020.html", "product_code":"dcs", - "code":"99", + "code":"107", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Client and Network Connection", @@ -992,8 +1072,8 @@ { "uri":"en-us_topic_0090662012.html", "product_code":"dcs", - "code":"100", - "des":"DCS Redis 3.0/4.0/5.0 instances are deployed in different modes. Therefore, the access control method varies.To control access to DCS Redis 3.0 instances, you can use sec", + "code":"108", + "des":"DCS helps you control access to your DCS instances in the following ways, depending on the deployment mode:To control access to DCS Redis 3.0 instances, you can use secur", "doc_type":"usermanual", "kw":"Security Group Configurations,Client and Network Connection,User Guide", "title":"Security Group Configurations", @@ -1002,27 +1082,37 @@ { "uri":"dcs-faq-0730001.html", "product_code":"dcs", - "code":"101", + "code":"109", "des":"No. DCS instances cannot be access at their EIPs over public networks. To ensure security, the ECS that serves as a client and the DCS instance that the client will acces", "doc_type":"usermanual", - "kw":"Does DCS Support Public Access?,Client and Network Connection,User Guide", - "title":"Does DCS Support Public Access?", + "kw":"Does DCS Support Access over Public Networks?,Client and Network Connection,User Guide", + "title":"Does DCS Support Access over Public Networks?", "githuburl":"" }, { "uri":"en-us_topic_0100698850.html", "product_code":"dcs", - "code":"102", + "code":"110", "des":"Cross-VPC means the client and the instance are not in the same VPC.Generally, VPCs are isolated from each other and ECSs cannot access DCS instances that belong to a dif", "doc_type":"usermanual", "kw":"VPC peering connections,across VPCs,Does DCS Support Cross-VPC Access?,Client and Network Connection", "title":"Does DCS Support Cross-VPC Access?", "githuburl":"" }, + { + "uri":"dcs-faq-0427005.html", + "product_code":"dcs", + "code":"111", + "des":"This is because you have enabled password-free access for the instance. To prevent the error message from appearing, do not enter any password.", + "doc_type":"faq", + "kw":"Why Is \"(error) NOAUTH Authentication required\" Displayed When I Access a DCS Redis Instance?,Client", + "title":"Why Is \"(error) NOAUTH Authentication required\" Displayed When I Access a DCS Redis Instance?", + "githuburl":"" + }, { "uri":"dcs-faq-0730004.html", "product_code":"dcs", - "code":"103", + "code":"112", "des":"Analysis: If persistent connections (\"pconnect\" in Redis terminology) or connection pooling is used and connections are closed after being used for connecting to DCS inst", "doc_type":"usermanual", "kw":"What Should I Do If Access to DCS Fails After Server Disconnects?,Client and Network Connection,User", @@ -1032,7 +1122,7 @@ { "uri":"dcs-faq-0730005.html", "product_code":"dcs", - "code":"104", + "code":"113", "des":"Occasional timeout errors are normal because of network connectivity and client timeout configurations.You are advised to include reconnection operations into your servic", "doc_type":"usermanual", "kw":"Why Do Requests Sometimes Time Out in Clients?,Client and Network Connection,User Guide", @@ -1042,7 +1132,7 @@ { "uri":"dcs-faq-0730006.html", "product_code":"dcs", - "code":"105", + "code":"114", "des":"The error message that will possibly be displayed when you use the Jedis connection pool is as follows:If this error message is displayed, check whether your instance is ", "doc_type":"usermanual", "kw":"use the Jedis connection pool,Jedis client,TIME_WAIT,What Should I Do If an Error Is Returned When I", @@ -1052,7 +1142,7 @@ { "uri":"dcs-faq-0730007.html", "product_code":"dcs", - "code":"106", + "code":"115", "des":"The possible causes are as follows:The command is spelled incorrectly.As shown in the following figure, the error message is returned because the correct command for dele", "doc_type":"usermanual", "kw":"Why Is \"ERR unknown command\" Displayed When I Access a DCS Redis Instance Through a Redis Client?,Cl", @@ -1062,7 +1152,7 @@ { "uri":"dcs-faq-0730008.html", "product_code":"dcs", - "code":"107", + "code":"116", "des":"You can access a DCS Redis instance through the Redis Desktop Manager within a VPC.Enter the address, port number (6379), and authentication password of the DCS instance ", "doc_type":"usermanual", "kw":"How Do I Access a DCS Redis Instance Through Redis Desktop Manager?,Client and Network Connection,Us", @@ -1072,7 +1162,7 @@ { "uri":"dcs-faq-0730009.html", "product_code":"dcs", - "code":"108", + "code":"117", "des":"By using DCS Redis instances, Spring Session can implement session sharing. When interconnecting with Spring Cloud, the following error information is displayed:For secur", "doc_type":"usermanual", "kw":"Spring Session can implement session sharing,What If \"ERR Unsupported CONFIG subcommand\" is Displaye", @@ -1080,29 +1170,49 @@ "githuburl":"" }, { - "uri":"dcs-faq-0730010.html", + "uri":"dcs-faq-0427015.html", "product_code":"dcs", - "code":"109", - "des":"Preliminary checks:Check the connection address.Obtain the connection address from the instance basic information page on the DCS console.Obtain the connection address fr", - "doc_type":"usermanual", - "kw":"How Do I Troubleshoot Redis Connection Failures?,Client and Network Connection,User Guide", - "title":"How Do I Troubleshoot Redis Connection Failures?", + "code":"118", + "des":"A DCS Redis instance can be access with or without a password. You can directly access a DCS Redis instance through a Redis client without setting a password. However, fo", + "doc_type":"faq", + "kw":"Is a Password Required for Accessing an Instance? How Do I Set a Password?,Client and Network Connec", + "title":"Is a Password Required for Accessing an Instance? How Do I Set a Password?", "githuburl":"" }, { "uri":"dcs-faq-0730011.html", "product_code":"dcs", - "code":"110", + "code":"119", "des":"Pay attention to the following issues when using Redis for pub/sub:Your client must process messages in a timely manner.Your client subscribes to a channel. If it does no", "doc_type":"usermanual", "kw":"Redis for pub/sub,What Should Be Noted When Using Redis for Pub/Sub?,Client and Network Connection,U", "title":"What Should Be Noted When Using Redis for Pub/Sub?", "githuburl":"" }, + { + "uri":"dcs-faq-0730010.html", + "product_code":"dcs", + "code":"120", + "des":"Preliminary checks:Check the connection address.Obtain the connection address from the instance basic information page on the DCS console.Obtain the connection address fr", + "doc_type":"usermanual", + "kw":"How Do I Troubleshoot Redis Connection Failures?,Client and Network Connection,User Guide", + "title":"How Do I Troubleshoot Redis Connection Failures?", + "githuburl":"" + }, + { + "uri":"dcs-faq-210721003.html", + "product_code":"", + "code":"121", + "des":"Error message \"Cannot assign requested address\" is returned when you access Redis using connect.Applications that encounter this error typically use php-fpm and phpredis.", + "doc_type":"", + "kw":"What Can I Do If Error \"Cannot assign requested address\" Is Returned When I Access Redis Using conne", + "title":"What Can I Do If Error \"Cannot assign requested address\" Is Returned When I Access Redis Using connect?", + "githuburl":"" + }, { "uri":"dcs-faq-0326021.html", "product_code":"dcs", - "code":"111", + "code":"122", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Redis Usage", @@ -1112,7 +1222,7 @@ { "uri":"dcs-faq-0730012.html", "product_code":"dcs", - "code":"112", + "code":"123", "des":"Possible cause 1:The service QPS is so high that the CPU usage spikes to 100%.The service QPS is so high that the CPU usage spikes to 100%.Possible cause 2:You have run c", "doc_type":"usermanual", "kw":"Why Is CPU Usage of a DCS Redis Instance 100%?,Redis Usage,User Guide", @@ -1122,7 +1232,7 @@ { "uri":"dcs-faq-0730013.html", "product_code":"dcs", - "code":"113", + "code":"124", "des":"No. Once an instance is created, its VPC and subnet cannot be changed. If you want to use a different set of VPC and subnet, create a same instance and specify a desired ", "doc_type":"usermanual", "kw":"Can I Change the VPC and Subnet for a DCS Redis Instance?,Redis Usage,User Guide", @@ -1132,17 +1242,17 @@ { "uri":"dcs-faq-0730014.html", "product_code":"dcs", - "code":"114", - "des":"Currently, DCS Redis 4.0 and Redis 5.0 instances use VPC endpoints and do not support security groups. You can configure whitelists instead. For details, see Managing IP ", + "code":"125", + "des":"Currently, DCS Redis 4.0/5.0/6.0 instances use VPC endpoints and do not support security groups. You can configure whitelists instead. For details, see Managing IP Addres", "doc_type":"usermanual", - "kw":"Why Aren't Security Groups Configured for DCS Redis 4.0 and 5.0 Instances?,Redis Usage,User Guide", - "title":"Why Aren't Security Groups Configured for DCS Redis 4.0 and 5.0 Instances?", + "kw":"Why Aren't Security Groups Configured for DCS Redis 4.0/5.0/6.0 Instances?,Redis Usage,User Guide", + "title":"Why Aren't Security Groups Configured for DCS Redis 4.0/5.0/6.0 Instances?", "githuburl":"" }, { "uri":"dcs-faq-0730015.html", "product_code":"dcs", - "code":"115", + "code":"126", "des":"The maximum allowed size of a key is 512 MB.To reduce memory usage and facilitate key query, ensure that each key does not exceed 1 KB.To reduce memory usage and facilita", "doc_type":"usermanual", "kw":"Do DCS Redis Instances Limit the Size of a Key or Value?,Redis Usage,User Guide", @@ -1152,7 +1262,7 @@ { "uri":"dcs-faq-0730017.html", "product_code":"dcs", - "code":"116", + "code":"127", "des":"Cluster DCS Redis 3.0 instances (Proxy Cluster type) are used in the same way that you use single-node or master/standby instances. You do not need to know the backend no", "doc_type":"usermanual", "kw":"Can I Obtain the Addresses of the Nodes in a Cluster DCS Redis Instance?,Redis Usage,User Guide", @@ -1162,17 +1272,17 @@ { "uri":"dcs-faq-0730018.html", "product_code":"dcs", - "code":"117", - "des":"DCS Redis 3.0 instances are deployed on VMs and some memory is reserved for system overheads.", + "code":"128", + "des":"DCS Redis 3.0 instances are deployed on VMs and some memory is reserved for system overheads. This problem will not occur on other instance versions.", "doc_type":"usermanual", - "kw":"Why Is Available Memory of a DCS Redis 3.0 Instance Smaller Than Instance Cache Size?,Redis Usage,Us", - "title":"Why Is Available Memory of a DCS Redis 3.0 Instance Smaller Than Instance Cache Size?", + "kw":"Why Is Available Memory Smaller Than Instance Cache Size?,Redis Usage,User Guide", + "title":"Why Is Available Memory Smaller Than Instance Cache Size?", "githuburl":"" }, { "uri":"dcs-faq-0730019.html", "product_code":"dcs", - "code":"118", + "code":"129", "des":"Both single-node and master/standby DCS Redis instances support multiple databases. By default, single-node and master/standby DCS instances can read and write data in 25", "doc_type":"usermanual", "kw":"DCS Redis instances support multiple databases,Does DCS for Redis Support Multiple Databases?,Redis ", @@ -1182,7 +1292,7 @@ { "uri":"dcs-faq-0730020.html", "product_code":"dcs", - "code":"119", + "code":"130", "des":"Yes. DCS for Redis 4.0 and 5.0 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", @@ -1192,8 +1302,8 @@ { "uri":"dcs-faq-0730021.html", "product_code":"dcs", - "code":"120", - "des":"Yes. Redis Sentinel is supported by DCS for Redis 4.0 and 5.0 and is enabled by default. Sentinel constantly checks if master and replica nodes are running properly. If t", + "code":"131", + "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", "doc_type":"usermanual", "kw":"Does DCS for Redis Support Sentinel?,Redis Usage,User Guide", "title":"Does DCS for Redis Support Sentinel?", @@ -1202,7 +1312,7 @@ { "uri":"dcs-faq-0730022.html", "product_code":"dcs", - "code":"121", + "code":"132", "des":"Data is evicted from cache based on a user-defined space limit in order to make space for new data.You can change the eviction policy by configuring the maxmemory-policy ", "doc_type":"usermanual", "kw":"What Is the Default Data Eviction Policy?,Redis Usage,User Guide", @@ -1212,27 +1322,17 @@ { "uri":"dcs-faq-0730023.html", "product_code":"dcs", - "code":"122", + "code":"133", "des":"Start the Redis exporter using the CLI. Based on the output, check for errors and troubleshoot accordingly.", "doc_type":"usermanual", "kw":"What Should I Do If an Error Occurs in Redis Exporter?,Redis Usage,User Guide", "title":"What Should I Do If an Error Occurs in Redis Exporter?", "githuburl":"" }, - { - "uri":"dcs-faq-0730024.html", - "product_code":"dcs", - "code":"123", - "des":"This is normal due to Redis functions (such as master/replica replication and lazyfree). When the memory becomes full, scale up the instance or remove unnecessary data.", - "doc_type":"usermanual", - "kw":"Why Is Memory Usage More Than 100%?,Redis Usage,User Guide", - "title":"Why Is Memory Usage More Than 100%?", - "githuburl":"" - }, { "uri":"dcs-faq-0730025.html", "product_code":"dcs", - "code":"124", + "code":"134", "des":"Redisson implements lock acquisition and unlocking in the following process:Redisson lock acquisition and unlocking are implemented by running Lua scripts.During lock acq", "doc_type":"usermanual", "kw":"Why Is Redisson Distributed Lock Not Supported by DCS Proxy Cluster Redis 3.0 Instances?,Redis Usage", @@ -1242,8 +1342,8 @@ { "uri":"dcs-faq-0730026.html", "product_code":"dcs", - "code":"125", - "des":"You cannot customize or change the port for accessing a DCS Redis 3.0 instance. You can customize and change the port for accessing a DCS Redis 4.0 or 5.0 instance.Redis ", + "code":"135", + "des":"You cannot customize or change the port for accessing a DCS Redis 3.0 instance. You can customize (during instance creation) but cannot change the port for accessing a DC", "doc_type":"usermanual", "kw":"Can I Customize or Change the Port for Accessing a DCS Instance?,Redis Usage,User Guide", "title":"Can I Customize or Change the Port for Accessing a DCS Instance?", @@ -1252,8 +1352,8 @@ { "uri":"dcs-faq-0730027.html", "product_code":"dcs", - "code":"126", - "des":"After a DCS instance is created, its intra-VPC connection addresses cannot be modified.For details about accessing DCS instances through clients, see Accessing a DCS Redi", + "code":"136", + "des":"After a DCS instance is created, its intra-VPC connection addresses cannot be modified.To use a different IP address, you must create a new instance and manually specify ", "doc_type":"usermanual", "kw":"Can I Modify the Connection Addresses for Accessing a DCS Instance?,Redis Usage,User Guide", "title":"Can I Modify the Connection Addresses for Accessing a DCS Instance?", @@ -1262,7 +1362,7 @@ { "uri":"dcs-faq-0730029.html", "product_code":"dcs", - "code":"127", + "code":"137", "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", "doc_type":"usermanual", "kw":"Does DCS Support Cross-AZ Deployment?,Redis Usage,User Guide", @@ -1272,7 +1372,7 @@ { "uri":"dcs-faq-0730030.html", "product_code":"dcs", - "code":"128", + "code":"138", "des":"Possible cause: When a cluster instance is started, status and data are synchronized between the nodes of the instance. If a large amount of data is continuously written ", "doc_type":"usermanual", "kw":"Why Does It Take a Long Time to Start a Cluster DCS Instance?,Redis Usage,User Guide", @@ -1282,27 +1382,17 @@ { "uri":"dcs-faq-0730032.html", "product_code":"dcs", - "code":"129", + "code":"139", "des":"No. If you wish to query Redis configurations and usage information, use redis-cli. If you wish to monitor DCS Redis instance metrics, go to the Cloud Eye console. For de", "doc_type":"usermanual", "kw":"Does DCS for Redis Provide Backend Management Software?,Redis Usage,User Guide", "title":"Does DCS for Redis Provide Backend Management Software?", "githuburl":"" }, - { - "uri":"dcs-faq-0730033.html", - "product_code":"dcs", - "code":"130", - "des":"Possible cause: The output buffer may have occupied an excessive amount of memory.Solution: After connecting to the instance using redis-cli, run the redis-cli --bigkeys ", - "doc_type":"usermanual", - "kw":"Why Is Memory of a DCS Redis Instance Used Up by Just a Few Keys?,Redis Usage,User Guide", - "title":"Why Is Memory of a DCS Redis Instance Used Up by Just a Few Keys?", - "githuburl":"" - }, { "uri":"dcs-faq-0730034.html", "product_code":"dcs", - "code":"131", + "code":"140", "des":"If a DCS instance is automatically deleted or manually deleted through the Redis client, its data cannot be retrieved. If you have backed up the instance, you can restore", "doc_type":"usermanual", "kw":"Can I Recover Data from Deleted DCS Instances?,Redis Usage,User Guide", @@ -1312,7 +1402,7 @@ { "uri":"dcs-faq-210223001.html", "product_code":"dcs", - "code":"132", + "code":"141", "des":"Symptom: \"Error in execution; nested exception is io.lettuce.core.RedisCommandExecutionException: OOM command not allowed when used memory > 'maxmemory'\" is returned duri", "doc_type":"usermanual", "kw":"Why Is \"Error in execution\" Returned When I Access Redis?,Redis Usage,User Guide", @@ -1322,7 +1412,7 @@ { "uri":"dcs-faq-210409001.html", "product_code":"", - "code":"133", + "code":"142", "des":"Normally, Redis keys do not disappear. If a key is missing, it may have expired, been evicted, or been deleted.Perform the following checks one by one:Check whether the k", "doc_type":"", "kw":"Why Does a Key Disappear in Redis?,Redis Usage,User Guide", @@ -1332,7 +1422,7 @@ { "uri":"dcs-faq-0220330.html", "product_code":"", - "code":"134", + "code":"143", "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":"", "kw":"Will Cached Data Be Retained After an Instance Is Restarted?,Redis Usage,User Guide", @@ -1342,7 +1432,7 @@ { "uri":"dcs-faq-190921003.html", "product_code":"dcs", - "code":"135", + "code":"144", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Redis Commands", @@ -1352,7 +1442,7 @@ { "uri":"dcs-faq-0730036.html", "product_code":"dcs", - "code":"136", + "code":"145", "des":"Exercise caution when clearing data.Redis 3.0Data of a DCS Redis 3.0 instance cannot be cleared on the console, and can only be cleared by the FLUSHDB or FLUSHALL command", "doc_type":"usermanual", "kw":"How Do I Clear Redis Data?,Redis Commands,User Guide", @@ -1362,7 +1452,7 @@ { "uri":"dcs-faq-0730039.html", "product_code":"dcs", - "code":"137", + "code":"146", "des":"Yes. For more information about Redis command compatibility, see Command Compatibility.", "doc_type":"usermanual", "kw":"Does DCS for Redis Support the INCR and EXPIRE Commands?,Redis Commands,User Guide", @@ -1372,8 +1462,8 @@ { "uri":"dcs-faq-0730040.html", "product_code":"dcs", - "code":"138", - "des":"Possible causes include the following:The command is incorrect.The command is disabled in DCS.For security purposes, some Redis commands are disabled in DCS. For details ", + "code":"147", + "des":"Possible causes include the following:The command is incorrect.As shown in the following figure, the error message is returned because the correct command for deleting a ", "doc_type":"usermanual", "kw":"Why Do I Fail to Execute Some Redis Commands?,Redis Commands,User Guide", "title":"Why Do I Fail to Execute Some Redis Commands?", @@ -1382,7 +1472,7 @@ { "uri":"dcs-faq-0730041.html", "product_code":"dcs", - "code":"139", + "code":"148", "des":"Run the command in redis-cli to check whether the command takes effect.The following describes two scenarios:Scenario 1: Set and query the value of a key to check whether", "doc_type":"usermanual", "kw":"Why Does a Redis Command Fail to Take Effect?,Redis Commands,User Guide", @@ -1390,19 +1480,39 @@ "githuburl":"" }, { - "uri":"dcs-faq-0730042.html", + "uri":"dcs-faq-0427057.html", "product_code":"dcs", - "code":"140", - "des":"The time limit for executing a Redis command is 1 minute. This limit cannot be configured. After the execution of a command times out, your client will be automatically d", - "doc_type":"usermanual", - "kw":"time limit for executing a Redis command,Is There a Time Limit on Executing Redis Commands? What Wil", + "code":"149", + "des":"Redis command timeouts can be controlled on the client end or server end.Timeouts on the client end are controlled in the client code. You can determine the timeouts that", + "doc_type":"faq", + "kw":"Is There a Time Limit on Executing Redis Commands? What Will Happen If a Command Times Out?,Redis Co", "title":"Is There a Time Limit on Executing Redis Commands? What Will Happen If a Command Times Out?", "githuburl":"" }, + { + "uri":"dcs-faq-0427058.html", + "product_code":"dcs", + "code":"150", + "des":"No. Like in open-source Redis, keys in DCS for Redis are case-sensitive and cannot be configured to be case-insensitive.", + "doc_type":"faq", + "kw":"Can I Configure Redis Keys to Be Case-Insensitive?,Redis Commands,User Guide", + "title":"Can I Configure Redis Keys to Be Case-Insensitive?", + "githuburl":"" + }, + { + "uri":"dcs-faq-0624001.html", + "product_code":"", + "code":"151", + "des":"No. Redis does not record commands and does not support viewing the most frequently used commands.", + "doc_type":"", + "kw":"Can I View the Most Frequently Used Redis Commands?,Redis Commands,User Guide", + "title":"Can I View the Most Frequently Used Redis Commands?", + "githuburl":"" + }, { "uri":"dcs-faq-0326022.html", "product_code":"dcs", - "code":"141", + "code":"152", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Instance Scaling and Upgrade", @@ -1412,17 +1522,17 @@ { "uri":"dcs-faq-0730043.html", "product_code":"dcs", - "code":"142", - "des":"No. Different Redis versions use different underlying architectures. The Redis version used by a DCS instance cannot be changed once the instance is created. However, you", + "code":"153", + "des":"No. Different Redis versions use different underlying architectures. The Redis version used by a DCS instance cannot be changed once the instance is created. For example,", "doc_type":"usermanual", - "kw":"Can DCS Redis Instances Be Upgraded, for Example, from Redis 3.0 to Redis 4.0 or 5.0?,Instance Scali", - "title":"Can DCS Redis Instances Be Upgraded, for Example, from Redis 3.0 to Redis 4.0 or 5.0?", + "kw":"Can DCS Redis Instances Be Upgraded, for Example, from Redis 4.0 to 5.0?,Instance Scaling and Upgrad", + "title":"Can DCS Redis Instances Be Upgraded, for Example, from Redis 4.0 to 5.0?", "githuburl":"" }, { "uri":"dcs-faq-0730044.html", "product_code":"dcs", - "code":"143", + "code":"154", "des":"O&M personnel will contact you before performing maintenance during the maintenance time window, informing you of the operations and their impacts. You do not need to wor", "doc_type":"usermanual", "kw":"Are Services Interrupted If Maintenance is Performed During the Maintenance Time Window?,Instance Sc", @@ -1432,18 +1542,18 @@ { "uri":"dcs-faq-0730045.html", "product_code":"dcs", - "code":"144", + "code":"155", "des":"No. Specification modifications can take place while the instance is running and do not affect any other resources.", "doc_type":"usermanual", - "kw":"Are Instance Resources Affected During Specification Modification?,Instance Scaling and Upgrade,User", - "title":"Are Instance Resources Affected During Specification Modification?", + "kw":"Are Instances Stopped or Restarted During Specification Modification?,Instance Scaling and Upgrade,U", + "title":"Are Instances Stopped or Restarted During Specification Modification?", "githuburl":"" }, { "uri":"dcs-faq-0730047.html", "product_code":"dcs", - "code":"145", - "des":"You are advised to change the instance specifications during off-peak hours because specification modification has the following impacts:Impact of instance type changes:F", + "code":"156", + "des":"You are advised to change the instance specifications during off-peak hours because specification modification has the following impacts:Impact of scaling:Single-node and", "doc_type":"usermanual", "kw":"Are Services Interrupted During Specification Modification?,Instance Scaling and Upgrade,User Guide", "title":"Are Services Interrupted During Specification Modification?", @@ -1452,7 +1562,7 @@ { "uri":"dcs-faq-0730048.html", "product_code":"dcs", - "code":"146", + "code":"157", "des":"Specifications of a DCS instance cannot be modified if another task of the instance is still running. For example, you cannot delete or scale up an instance while it is b", "doc_type":"usermanual", "kw":"Why Can't I Modify Specifications for a DCS Redis Instance?,Instance Scaling and Upgrade,User Guide", @@ -1462,7 +1572,7 @@ { "uri":"dcs-faq-0326023.html", "product_code":"dcs", - "code":"147", + "code":"158", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Monitoring and Alarm", @@ -1472,7 +1582,7 @@ { "uri":"dcs-faq-0427070.html", "product_code":"dcs", - "code":"148", + "code":"159", "des":"The number of connections received by a DCS instance is a metric that is monitored by Cloud Eye. For details on how to view metrics, see Viewing DCS Monitoring Metrics.On", "doc_type":"faq", "kw":"How Do I View Current Concurrent Connections and Maximum Connections of a DCS Redis Instance?,Monito", @@ -1482,7 +1592,7 @@ { "uri":"dcs-faq-0730049.html", "product_code":"dcs", - "code":"149", + "code":"160", "des":"No. To ensure high-performance reads and writes, Redis does not audit commands. Commands are not printed.", "doc_type":"usermanual", "kw":"Does Redis Support Command Audits?,Monitoring and Alarm,User Guide", @@ -1492,7 +1602,7 @@ { "uri":"dcs-faq-0730050.html", "product_code":"dcs", - "code":"150", + "code":"161", "des":"If you have any doubt on the monitoring data of a DCS Redis instance, you can access the instance through redis-cli and run the INFO ALL command to view the metrics. For ", "doc_type":"usermanual", "kw":"What Should I Do If the Monitoring Data of a DCS Redis Instance Is Abnormal?,Monitoring and Alarm,Us", @@ -1502,7 +1612,7 @@ { "uri":"dcs-faq-0730052.html", "product_code":"dcs", - "code":"151", + "code":"162", "des":"For single-node and master/standby DCS instances, the used instance memory is measured by the Redis-server process. For cluster DCS instances, the used cluster memory is ", "doc_type":"usermanual", "kw":"used instance memory is normally slightly higher than the available instance memory,Why Is Used Memo", @@ -1512,7 +1622,7 @@ { "uri":"dcs-faq-0513001.html", "product_code":"", - "code":"152", + "code":"163", "des":"The basic information about the bandwidth usage metric is as follows.Bandwidth usage = (Input flow + Output flow)/(2 x Maximum bandwidth) x 100%According to the formula, ", "doc_type":"", "kw":"Why Does Bandwidth Usage Exceed 100%?,Monitoring and Alarm,User Guide", @@ -1522,8 +1632,8 @@ { "uri":"dcs-faq-0603001.html", "product_code":"", - "code":"153", - "des":"If the Rejected Connections metric is displayed, check if the number of connected clients exceeds the maximum allowed number of connections of the instances. To check the", + "code":"164", + "des":"If the Rejected Connections metric is displayed, check if the number of connected clients exceeds the maximum allowed number of connections of the instances.To check the ", "doc_type":"", "kw":"Why Is the Rejected Connections Metric Displayed?,Monitoring and Alarm,User Guide", "title":"Why Is the Rejected Connections Metric Displayed?", @@ -1532,7 +1642,7 @@ { "uri":"dcs-faq-0220721.html", "product_code":"", - "code":"154", + "code":"165", "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", "doc_type":"", "kw":"Why Is Flow Control Triggered? How Do I Handle It?,Monitoring and Alarm,User Guide", @@ -1542,7 +1652,7 @@ { "uri":"dcs-faq-0326024.html", "product_code":"dcs", - "code":"155", + "code":"166", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Data Backup, Export, and Migration", @@ -1552,7 +1662,7 @@ { "uri":"dcs-faq-0730053.html", "product_code":"dcs", - "code":"156", + "code":"167", "des":"For master/standby or cluster instances:Perform the following operations to export the data:On the Backups & Restorations page, view the backup records.If there are no ba", "doc_type":"usermanual", "kw":"How Do I Export DCS Redis Instance Data?,Data Backup, Export, and Migration,User Guide", @@ -1562,7 +1672,7 @@ { "uri":"dcs-faq-0730054.html", "product_code":"dcs", - "code":"157", + "code":"168", "des":"Redis 3.0No. On the console, backup data of a DCS Redis 3.0 instance can be exported only to AOF files. To export data to RDB files, run the following command in redis-cl", "doc_type":"usermanual", "kw":"Can I Export Backup Data of DCS Redis Instances to RDB Files Using the Console?,Data Backup, Export,", @@ -1570,19 +1680,49 @@ "githuburl":"" }, { - "uri":"dcs-faq-0730057.html", + "uri":"dcs-faq-0427081.html", "product_code":"dcs", - "code":"158", - "des":"DCS Redis instances:Single-node: Not supportedMaster/Standby and cluster: SupportedSingle-node: Not supportedMaster/Standby and cluster: Supported", - "doc_type":"usermanual", - "kw":"Does DCS Support Data Persistence?,Data Backup, Export, and Migration,User Guide", - "title":"Does DCS Support Data Persistence?", + "code":"169", + "des":"DCS Redis instances:Single-node: Data persistence is not supported.Master/standby and cluster (except single-replica clusters): Data persistence is supported.Single-node:", + "doc_type":"faq", + "kw":"Does DCS Support Data Persistence? What Is the Impact of Persistence?,Data Backup, Export, and Migra", + "title":"Does DCS Support Data Persistence? What Is the Impact of Persistence?", + "githuburl":"" + }, + { + "uri":"dcs-faq-210706001.html", + "product_code":"", + "code":"170", + "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", + "doc_type":"", + "kw":"When Will AOF Rewrites Be Triggered?,Data Backup, Export, and Migration,User Guide", + "title":"When Will AOF Rewrites Be Triggered?", + "githuburl":"" + }, + { + "uri":"dcs-faq-220317.html", + "product_code":"", + "code":"171", + "des":"No. A migration task allows data to be migrated to only one target instance. To migrate data to multiple target instances, create multiple migration tasks.", + "doc_type":"", + "kw":"Can I Migrate Data to Multiple Target Instances in One Migration Task?,Data Backup, Export, and Migr", + "title":"Can I Migrate Data to Multiple Target Instances in One Migration Task?", + "githuburl":"" + }, + { + "uri":"dcs-faq-11185.html", + "product_code":"", + "code":"172", + "des":"If the data exists on both the source and target instances, the target data is overwritten by the source data. If the data exists only on the target instance, the data wi", + "doc_type":"", + "kw":"Will the Same Keys Be Overwritten During Data Migration or Backup Import?,Data Backup, Export, and M", + "title":"Will the Same Keys Be Overwritten During Data Migration or Backup Import?", "githuburl":"" }, { "uri":"dcs-migration-090626001.html", "product_code":"", - "code":"159", + "code":"173", "des":"Rump is an open-source tool designed for migrating Redis data online. It supports migration between DBs of the same instance and between DBs of different instances.Rump u", "doc_type":"", "kw":"Online Migration with Rump,Data Backup, Export, and Migration,User Guide", @@ -1592,67 +1732,67 @@ { "uri":"dcs-faq-0805001.html", "product_code":"", - "code":"160", + "code":"174", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"", - "kw":"Analysis of Big Keys and Hot Keys", - "title":"Analysis of Big Keys and Hot Keys", + "kw":"Big/Hot Key Analysis", + "title":"Big/Hot Key Analysis", "githuburl":"" }, { "uri":"dcs-faq-0521003.html", "product_code":"", - "code":"161", + "code":"175", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"", - "kw":"What Are Big Keys and Hot Keys?,Analysis of Big Keys and Hot Keys,User Guide", + "kw":"What Are Big Keys and Hot Keys?,Big/Hot Key Analysis,User Guide", "title":"What Are Big Keys and Hot Keys?", "githuburl":"" }, { "uri":"dcs-faq-0521004.html", "product_code":"", - "code":"162", + "code":"176", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"", - "kw":"What Is the Impact of Big Keys or Hot Keys?,Analysis of Big Keys and Hot Keys,User Guide", + "kw":"What Is the Impact of Big Keys or Hot Keys?,Big/Hot Key Analysis,User Guide", "title":"What Is the Impact of Big Keys or Hot Keys?", "githuburl":"" }, { "uri":"dcs-faq-0521005.html", "product_code":"", - "code":"163", + "code":"177", "des":"Keep the size of Strings within 10 KB and the quantity of Hashes, Lists, Sets, or Zsets within 5000.When naming keys, use the service name abbreviation as the prefix and ", "doc_type":"", - "kw":"How Do I Avoid Big Keys and Hot Keys?,Analysis of Big Keys and Hot Keys,User Guide", + "kw":"How Do I Avoid Big Keys and Hot Keys?,Big/Hot Key Analysis,User Guide", "title":"How Do I Avoid Big Keys and Hot Keys?", "githuburl":"" }, { "uri":"dcs-faq-0521006.html", "product_code":"", - "code":"164", + "code":"178", "des":"DCS for Redis 3.0 does not support hot key analysis on the console. Alternatively, you can use the following methods to analyze hot keys:Method 1: Analyze the service str", "doc_type":"", - "kw":"How Do I Analyze the Hot Keys of a DCS Redis 3.0 Instance?,Analysis of Big Keys and Hot Keys,User Gu", + "kw":"How Do I Analyze the Hot Keys of a DCS Redis 3.0 Instance?,Big/Hot Key Analysis,User Guide", "title":"How Do I Analyze the Hot Keys of a DCS Redis 3.0 Instance?", "githuburl":"" }, { "uri":"dcs-faq-0606002.html", "product_code":"", - "code":"165", + "code":"179", "des":"Hot key analysis is not supported by DCS Redis 3.0 instances. You can configure alarms to detect hot keys.Configure alarm rules for the Memory Usage metric of the instanc", "doc_type":"", - "kw":"How Do I Detect Big Keys and Hot Keys in Advance?,Analysis of Big Keys and Hot Keys,User Guide", + "kw":"How Do I Detect Big Keys and Hot Keys in Advance?,Big/Hot Key Analysis,User Guide", "title":"How Do I Detect Big Keys and Hot Keys in Advance?", "githuburl":"" }, { "uri":"dcs-faq-191204001.html", "product_code":"dcs", - "code":"166", + "code":"180", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Master/Standby Switchover", @@ -1662,7 +1802,7 @@ { "uri":"dcs-faq-0730058.html", "product_code":"dcs", - "code":"167", + "code":"181", "des":"A master/standby switchover may occur in the following scenarios:A master/standby switchover operation is initiated on the DCS Console.If the master node of a master/stan", "doc_type":"usermanual", "kw":"When Does a Master/Standby Switchover Occur?,Master/Standby Switchover,User Guide", @@ -1672,7 +1812,7 @@ { "uri":"dcs-faq-0730059.html", "product_code":"dcs", - "code":"168", + "code":"182", "des":"If a fault occurs in a master/standby or cluster DCS instance, a failover is triggered automatically. Services may be interrupted for less than half a minute during excep", "doc_type":"usermanual", "kw":"How Does Master/Standby Switchover Affect Services?,Master/Standby Switchover,User Guide", @@ -1682,7 +1822,7 @@ { "uri":"dcs-faq-0730060.html", "product_code":"dcs", - "code":"169", + "code":"183", "des":"No. If the master fails, the standby node will be promoted to master and takes the original IP address.", "doc_type":"usermanual", "kw":"Does the Client Need to Switch the Connection Address After a Master/Standby Switchover?,Master/Stan", @@ -1692,7 +1832,7 @@ { "uri":"dcs-faq-0730061.html", "product_code":"dcs", - "code":"170", + "code":"184", "des":"Redis master/standby instances are also called master/slave instances. Generally, updates to the master cache node are automatically and asynchronously replicated to the ", "doc_type":"usermanual", "kw":"asynchronously replicated,How Does Redis Master/Standby Replication Work?,Master/Standby Switchover,", @@ -1702,7 +1842,7 @@ { "uri":"en-us_topic_0072429345.html", "product_code":"dcs", - "code":"171", + "code":"185", "des":"For details about the terms involved in this document, see Glossary.", "doc_type":"usermanual", "kw":"Glossary,User Guide", @@ -1712,7 +1852,7 @@ { "uri":"dcs-ug-0326026.html", "product_code":"dcs", - "code":"172", + "code":"186", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Change History,User Guide", diff --git a/docs/dcs/umn/CLASS.TXT.json b/docs/dcs/umn/CLASS.TXT.json index 06f865a8b..2a2aafa42 100644 --- a/docs/dcs/umn/CLASS.TXT.json +++ b/docs/dcs/umn/CLASS.TXT.json @@ -36,7 +36,7 @@ "code":"4" }, { - "desc":"Three Redis versions are available for single-node DCS Redis instances: Redis 3.0, Redis 4.0, and Redis 5.0.Low system overhead and high QPSSingle-node instances do not s", + "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", "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. Three Redis versions are available for master/standby DCS Redis instances: Redis 3.0, Redis 4.0, and Redis 5.0.", + "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", "product_code":"dcs", "title":"Master/Standby Redis", "uri":"CacheMasterSlave.html", @@ -54,7 +54,7 @@ "code":"6" }, { - "desc":"DCS provides two types of cluster Redis instances: Proxy Cluster and Redis Cluster. Proxy Cluster uses Linux Virtual Server (LVS) and proxies. Redis Cluster is the native", + "desc":"DCS for Redis provides Proxy Cluster instances, which use Linux Virtual Server (LVS) and proxies to achieve high availability.Proxy Cluster DCS Redis instances are compat", "product_code":"dcs", "title":"Proxy Cluster Redis", "uri":"CacheCluster.html", @@ -63,7 +63,7 @@ "code":"7" }, { - "desc":"This section describes Redis Cluster DCS Redis 4.0 and 5.0 instances.The Redis Cluster instance type provided by DCS is compatible with the native Redis Cluster, which us", + "desc":"Redis Cluster DCS instances use the native distributed implementation of Redis.Redis Cluster DCS instances are compatible with Redis 4.0 and 5.0.The Redis Cluster instanc", "product_code":"dcs", "title":"Redis Cluster", "uri":"CacheProxy.html", @@ -71,6 +71,15 @@ "p_code":"4", "code":"8" }, + { + "desc":"Table 1 describes the differences between different Redis instance types in terms of features and commands.", + "product_code":"dcs", + "title":"Comparing DCS Redis Instance Types", + "uri":"dcs-pd-191224001.html", + "doc_type":"usermanual", + "p_code":"4", + "code":"9" + }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dcs", @@ -78,7 +87,7 @@ "uri":"en-us_topic_0054235835.html", "doc_type":"usermanual", "p_code":"1", - "code":"9" + "code":"10" }, { "desc":"This section describes DCS Redis 3.0 instance specifications, including the total memory, available memory, maximum number of connections allowed, maximum/assured bandwid", @@ -86,8 +95,8 @@ "title":"Redis 3.0 Instance Specifications", "uri":"dcs-pd-0916001.html", "doc_type":"usermanual", - "p_code":"9", - "code":"10" + "p_code":"10", + "code":"11" }, { "desc":"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", @@ -95,8 +104,17 @@ "title":"Redis 4.0 and 5.0 Instance Specifications", "uri":"dcs-pd-0916002.html", "doc_type":"usermanual", - "p_code":"9", - "code":"11" + "p_code":"10", + "code":"12" + }, + { + "desc":"This section describes DCS Redis 6.0 instance specifications, including the total memory, available memory, maximum number of connections allowed, maximum/assured bandwid", + "product_code":"dcs", + "title":"Redis 6.0 Instance Specifications", + "uri":"dcs-pd-0916004.html", + "doc_type":"usermanual", + "p_code":"10", + "code":"13" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -105,7 +123,7 @@ "uri":"dcs-pd-200312003.html", "doc_type":"usermanual", "p_code":"1", - "code":"12" + "code":"14" }, { "desc":"DCS for Redis 3.0 is developed based on Redis 3.0.7 and is compatible with open-source protocols and commands.This section describes DCS for Redis 3.0's compatibility wit", @@ -113,8 +131,8 @@ "title":"Redis 3.0 Commands", "uri":"dcs-pd-200713005.html", "doc_type":"usermanual", - "p_code":"12", - "code":"13" + "p_code":"14", + "code":"15" }, { "desc":"DCS for Redis 4.0 is developed based on Redis 4.0.14 and is compatible with open-source protocols and commands.This section describes DCS for Redis 4.0's compatibility wi", @@ -122,8 +140,8 @@ "title":"Redis 4.0 Commands", "uri":"dcs-pd-200916001.html", "doc_type":"usermanual", - "p_code":"12", - "code":"14" + "p_code":"14", + "code":"16" }, { "desc":"DCS for Redis 5.0 is developed based on Redis 5.0.9 and is compatible with open-source protocols and commands.This section describes DCS for Redis 5.0's compatibility wit", @@ -131,8 +149,17 @@ "title":"Redis 5.0 Commands", "uri":"dcs-pd-200813002.html", "doc_type":"usermanual", - "p_code":"12", - "code":"15" + "p_code":"14", + "code":"17" + }, + { + "desc":"DCS for Redis 6.0 is compatible with Redis 6.2.7 and with open-source protocols and commands.This section describes DCS for Redis 6.0's command compatibility, including s", + "product_code":"dcs", + "title":"Redis 6.0 Commands", + "uri":"dcs-pd-210209002.html", + "doc_type":"usermanual", + "p_code":"14", + "code":"18" }, { "desc":"Web CLI is a command line tool provided on the DCS console. This section describes Web CLI's compatibility with Redis commands, including supported and disabled commands.", @@ -140,17 +167,17 @@ "title":"Web CLI Commands", "uri":"dcs-pd-190826001.html", "doc_type":"usermanual", - "p_code":"12", - "code":"16" + "p_code":"14", + "code":"19" }, { "desc":"Some Redis commands are supported by cluster DCS instances for multi-key operations in the same slot. For details, see Table 1.While running commands that take a long tim", "product_code":"dcs", - "title":"Command Restrictions for Cluster Instances", + "title":"Command Restrictions", "uri":"dcs-pd-200813003.html", "doc_type":"usermanual", - "p_code":"12", - "code":"17" + "p_code":"14", + "code":"20" }, { "desc":"This section describes restrictions on some Redis commands.In case of a large amount of cached data, running the KEYS command may block the execution of other commands fo", @@ -158,26 +185,26 @@ "title":"Other Command Usage Restrictions", "uri":"dcs-pd-200813004.html", "doc_type":"usermanual", - "p_code":"12", - "code":"18" + "p_code":"14", + "code":"21" }, { "desc":"Whether you use DCS as the frontend cache or backend data store, DCS is always ready to ensure data reliability and service availability. The following figure shows the e", "product_code":"dcs", - "title":"HA and DR Policies", + "title":"Disaster Recovery and Multi-Active Solution", "uri":"GlobalDRPolicy.html", "doc_type":"usermanual", "p_code":"1", - "code":"19" + "code":"22" }, { - "desc":"When creating a DCS Redis instance, you can select the cache engine version and the instance type.VersionDCS supports Redis 3.0, 4.0, and 5.0. The following table describ", + "desc":"When creating a DCS Redis instance, you can select the cache engine version and the instance type.VersionDCS supports Redis 3.0/4.0/5.0/6.0. The following table describes", "product_code":"dcs", "title":"Comparing Redis Versions", "uri":"RedisDifference.html", "doc_type":"usermanual", "p_code":"1", - "code":"20" + "code":"23" }, { "desc":"DCS supports single-node, master/standby, and cluster instances, ensuring high read/write performance and fast data access. It also supports various instance management o", @@ -186,25 +213,25 @@ "uri":"dcs-pd-0326003.html", "doc_type":"usermanual", "p_code":"1", - "code":"21" + "code":"24" }, { - "desc":"An instance is the minimum resource unit provided by DCS.DCS supports the Redis cache engine, and single-node, master/standby, and cluster instance types. For each instan", + "desc":"An instance is the minimum resource unit provided by DCS.For details, see DCS Instance Specifications and DCS Instance Types.Projects are used to group and isolate OpenSt", "product_code":"dcs", "title":"Basic Concepts", "uri":"dcs-pd-200312004.html", "doc_type":"usermanual", "p_code":"1", - "code":"22" + "code":"25" }, { "desc":"If you need to assign different permissions to employees in your enterprise to access your DCS resources, Identity and Access Management (IAM) is a good choice for fine-g", "product_code":"dcs", - "title":"Permissions Management", + "title":"Permissions", "uri":"dcs-pd-210626001.html", "doc_type":"usermanual", "p_code":"1", - "code":"23" + "code":"26" }, { "desc":"DCS is used together with other services, including VPC, ECS, IAM, Cloud Eye, CTS, and Object Storage Service (OBS).A VPC is an isolated virtual network environment on th", @@ -213,7 +240,7 @@ "uri":"dcs-pd-0326006.html", "doc_type":"usermanual", "p_code":"1", - "code":"24" + "code":"27" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -222,7 +249,7 @@ "uri":"en-us_topic_0054235836.html", "doc_type":"usermanual", "p_code":"1", - "code":"25" + "code":"28" }, { "desc":"There are two ways to access DCS:Using the management consoleThe DCS provides a web-based management console. To launch the DCS console, create an account on the manageme", @@ -230,8 +257,8 @@ "title":"How to Access DCS", "uri":"en-us_topic_0054235837.html", "doc_type":"usermanual", - "p_code":"25", - "code":"26" + "p_code":"28", + "code":"29" }, { "desc":"The public cloud system provides two types of user permissions by default: user management and resource management.User management refers to the management of users, user", @@ -239,8 +266,8 @@ "title":"User Permissions", "uri":"en-us_topic_0054247786.html", "doc_type":"usermanual", - "p_code":"25", - "code":"27" + "p_code":"28", + "code":"30" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -249,7 +276,7 @@ "uri":"dcs-ug-210626003.html", "doc_type":"usermanual", "p_code":"", - "code":"28" + "code":"31" }, { "desc":"This chapter describes how to use IAM to implement fine-grained permissions control for your DCS resources. With IAM, you can:Create IAM users for employees based on your", @@ -257,17 +284,17 @@ "title":"Creating a User and Granting DCS Permissions", "uri":"dcs-ug-210626004.html", "doc_type":"usermanual", - "p_code":"28", - "code":"29" + "p_code":"31", + "code":"32" }, { - "desc":"Custom policies can be created to supplement the system-defined policies of DCS. For the actions that can be added for custom policies, see Permissions Policies and Suppo", + "desc":"Custom policies can be created to supplement the system-defined policies of DCS. For the actions that can be added to custom policies, see section \"Permissions Policies a", "product_code":"dcs", "title":"DCS Custom Policies", "uri":"dcs-ug-210626005.html", "doc_type":"usermanual", - "p_code":"28", - "code":"30" + "p_code":"31", + "code":"33" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -276,7 +303,7 @@ "uri":"dcs-ug-0326007.html", "doc_type":"usermanual", "p_code":"", - "code":"31" + "code":"34" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -284,8 +311,8 @@ "title":"Creating an Instance", "uri":"dcs-ug-0312003.html", "doc_type":"usermanual", - "p_code":"31", - "code":"32" + "p_code":"34", + "code":"35" }, { "desc":"Before creating a DCS instance, identify your requirements and complete the following preparations:Decide on the required cache engine version.Different Redis versions ha", @@ -293,17 +320,17 @@ "title":"Identifying Requirements", "uri":"PurchasePreparation.html", "doc_type":"usermanual", - "p_code":"32", - "code":"33" + "p_code":"35", + "code":"36" }, { "desc":"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 ", "product_code":"dcs", - "title":"Preparing the Environment", + "title":"Preparing Required Resources", "uri":"dcs-ug-0312004.html", "doc_type":"usermanual", - "p_code":"32", - "code":"34" + "p_code":"35", + "code":"37" }, { "desc":"You can create one or more DCS Redis instances with the required computing capabilities and storage space based on service requirements.The system automatically schedules", @@ -311,8 +338,8 @@ "title":"Creating a DCS Redis Instance", "uri":"dcs-ug-0326008.html", "doc_type":"usermanual", - "p_code":"32", - "code":"35" + "p_code":"35", + "code":"38" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -320,8 +347,8 @@ "title":"Accessing an Instance", "uri":"dcs-ug-0916002.html", "doc_type":"usermanual", - "p_code":"31", - "code":"36" + "p_code":"34", + "code":"39" }, { "desc":"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 ", @@ -329,8 +356,8 @@ "title":"Accessing a DCS Redis Instance Through redis-cli", "uri":"dcs-ug-0326009.html", "doc_type":"usermanual", - "p_code":"36", - "code":"37" + "p_code":"39", + "code":"40" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -338,8 +365,8 @@ "title":"Access in Different Languages", "uri":"dcs-ug-0512002.html", "doc_type":"usermanual", - "p_code":"36", - "code":"38" + "p_code":"39", + "code":"41" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -347,26 +374,26 @@ "title":"Java", "uri":"dcs-ug-211105003.html", "doc_type":"usermanual", - "p_code":"38", - "code":"39" + "p_code":"41", + "code":"42" }, { - "desc":"Access a DCS Redis instance through Jedis on an ECS in the same VPC. For more information on how to use other Redis clients, visit https://redis.io/clients.If a password ", + "desc":"Access a DCS Redis instance through Jedis on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis official website.A DCS Red", "product_code":"dcs", "title":"Jedis", "uri":"dcs-ug-0713005.html", "doc_type":"usermanual", - "p_code":"39", - "code":"40" + "p_code":"42", + "code":"43" }, { - "desc":"Access a Redis Cluster instance through Lettuce on an ECS in the same VPC. For more information on how to use other Redis clients, visit https://redis.io/clients.If a pas", + "desc":"Access a DCS Redis instance through Lettuce on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis official website.A DCS R", "product_code":"dcs", "title":"Lettuce", - "uri":"dcs-ug-211011001.html", + "uri":"dcs-ug-211105002.html", "doc_type":"usermanual", - "p_code":"39", - "code":"41" + "p_code":"42", + "code":"44" }, { "desc":"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.If a p", @@ -374,8 +401,8 @@ "title":"Redisson", "uri":"dcs-ug-211105004.html", "doc_type":"usermanual", - "p_code":"39", - "code":"42" + "p_code":"42", + "code":"45" }, { "desc":"A DCS Redis instance has been created and is in the Running state.An ECS has been created. For details about how to create an ECS, see Elastic Cloud Server User Guide.If ", @@ -383,8 +410,8 @@ "title":"Lettuce Integration with Spring Boot", "uri":"dcs-ug-211203001.html", "doc_type":"usermanual", - "p_code":"38", - "code":"43" + "p_code":"41", + "code":"46" }, { "desc":"Access a DCS Redis instance through redis-py on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis official website.Use re", @@ -392,8 +419,8 @@ "title":"Clients in Python", "uri":"dcs-ug-0312011.html", "doc_type":"usermanual", - "p_code":"38", - "code":"44" + "p_code":"41", + "code":"47" }, { "desc":"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.A DCS ", @@ -401,8 +428,8 @@ "title":"go-redis", "uri":"dcs-ug-211105001.html", "doc_type":"usermanual", - "p_code":"38", - "code":"45" + "p_code":"41", + "code":"48" }, { "desc":"Access a DCS Redis instance through hiredis on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis official website.The ope", @@ -410,8 +437,8 @@ "title":"hiredis in C++", "uri":"dcs-ug-0312010.html", "doc_type":"usermanual", - "p_code":"38", - "code":"46" + "p_code":"41", + "code":"49" }, { "desc":"Access a DCS Redis instance through C# Client StackExchange.Redis on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis of", @@ -419,8 +446,8 @@ "title":"C#", "uri":"dcs-ug-0312013.html", "doc_type":"usermanual", - "p_code":"38", - "code":"47" + "p_code":"41", + "code":"50" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -428,8 +455,8 @@ "title":"PHP", "uri":"dcs-ug-211202001.html", "doc_type":"usermanual", - "p_code":"38", - "code":"48" + "p_code":"41", + "code":"51" }, { "desc":"Access a DCS Redis instance through phpredis on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis official website.The op", @@ -437,8 +464,8 @@ "title":"phpredis", "uri":"dcs-ug-0312009.html", "doc_type":"usermanual", - "p_code":"48", - "code":"49" + "p_code":"51", + "code":"52" }, { "desc":"Access a DCS Redis instance through Predis on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis official website.A DCS Re", @@ -446,8 +473,8 @@ "title":"Predis", "uri":"dcs-ug-211202002.html", "doc_type":"usermanual", - "p_code":"48", - "code":"50" + "p_code":"51", + "code":"53" }, { "desc":"Access a DCS Redis instance through Node.js on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis official website.The ope", @@ -455,17 +482,17 @@ "title":"Node.js", "uri":"dcs-ug-0312012.html", "doc_type":"usermanual", - "p_code":"38", - "code":"51" + "p_code":"41", + "code":"54" }, { - "desc":"Access a DCS Redis instance through Web CLI. This function is supported only by DCS Redis 4.0 and 5.0 instances, and not by DCS Redis 3.0 instances.Do not enter sensitive", + "desc":"Access a DCS Redis instance through Web CLI. This function is supported only by DCS Redis 4.0 and later instances, and not by DCS Redis 3.0 instances.Do not enter sensiti", "product_code":"dcs", - "title":"Accessing a DCS Redis 4.0 or 5.0 Instance on the Console", + "title":"Accessing a DCS Redis 4.0/5.0/6.0 Instance on the Console", "uri":"dcs-ug-0312008.html", "doc_type":"usermanual", - "p_code":"36", - "code":"52" + "p_code":"39", + "code":"55" }, { "desc":"On the DCS console, you can view DCS instance details.Search by keyword.Enter a keyword to search.Enter a keyword to search.Select attributes and enter their keywords to ", @@ -473,17 +500,8 @@ "title":"Viewing Details of a DCS Instance", "uri":"dcs-ug-0312016.html", "doc_type":"usermanual", - "p_code":"31", - "code":"53" - }, - { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", - "product_code":"dcs", - "title":"Operation Guide", - "uri":"dcs-ug-0326010.html", - "doc_type":"usermanual", - "p_code":"", - "code":"54" + "p_code":"34", + "code":"56" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -491,8 +509,8 @@ "title":"Operating DCS Instances", "uri":"dcs-ug-0312015.html", "doc_type":"usermanual", - "p_code":"54", - "code":"55" + "p_code":"", + "code":"57" }, { "desc":"On the DCS console, you can scale a DCS Redis instance to a larger or smaller capacity.Modify instance specifications during off-peak hours.If your DCS instances are too ", @@ -500,8 +518,8 @@ "title":"Modifying DCS Instance Specifications", "uri":"dcs-ug-0326011.html", "doc_type":"usermanual", - "p_code":"55", - "code":"56" + "p_code":"57", + "code":"58" }, { "desc":"On the DCS console, you can start one or multiple DCS instances at a time.This function is not supported by recent instances. You can only start old instances that have b", @@ -509,8 +527,8 @@ "title":"Starting DCS Instances", "uri":"dcs-ug-0911001.html", "doc_type":"usermanual", - "p_code":"55", - "code":"57" + "p_code":"57", + "code":"59" }, { "desc":"On the DCS console, you can restart one or multiple DCS instances at a time.After a single-node DCS instance is restarted, data will be deleted from the instance.While a ", @@ -518,8 +536,8 @@ "title":"Restarting DCS Instances", "uri":"dcs-ug-0326013.html", "doc_type":"usermanual", - "p_code":"55", - "code":"58" + "p_code":"57", + "code":"60" }, { "desc":"On the DCS console, you can delete one or multiple DCS instances at a time. You can also delete all instance creation tasks that have failed to run.After a DCS instance i", @@ -527,8 +545,8 @@ "title":"Deleting DCS Instances", "uri":"dcs-ug-0326014.html", "doc_type":"usermanual", - "p_code":"55", - "code":"59" + "p_code":"57", + "code":"61" }, { "desc":"On the DCS console, you can manually switch the master and standby nodes of a DCS instance. This operation is used for special purposes, for example, releasing all servic", @@ -536,35 +554,35 @@ "title":"Performing a Master/Standby Switchover for a DCS Instance", "uri":"dcs-ug-0312017.html", "doc_type":"usermanual", - "p_code":"55", - "code":"60" + "p_code":"57", + "code":"62" }, { - "desc":"On the DCS console, you can clear data only for DCS Redis 4.0 and 5.0 instances.Clearing instance data cannot be undone and cleared data cannot be recovered. Exercise cau", + "desc":"You can clear data of DCS Redis 4.0 and later instances on the console.Clearing instance data cannot be undone and cleared data cannot be recovered. Exercise caution when", "product_code":"dcs", "title":"Clearing DCS Instance Data", "uri":"dcs-ug-0312018.html", "doc_type":"usermanual", - "p_code":"55", - "code":"61" + "p_code":"57", + "code":"63" }, { - "desc":"On the DCS console, you can export DCS instance information in full to an Excel file.Click the export result displayed in the lower left corner of the page.", + "desc":"On the DCS console, you can export DCS instance information in full to an Excel file.", "product_code":"dcs", "title":"Exporting DCS Instance List", "uri":"dcs-ug-0312019.html", "doc_type":"usermanual", - "p_code":"55", - "code":"62" + "p_code":"57", + "code":"64" }, { - "desc":"After creating a DCS Redis 4.0 or 5.0 instance, you can rename the following critical commands: COMMAND, KEYS, FLUSHDB, FLUSHALL, and HGETALL.You can rename multiple comm", + "desc":"After creating a DCS Redis 4.0 or later instance, you can rename the following critical commands: Currently, you can only rename the COMMAND, KEYS, FLUSHDB, and FLUSHALL ", "product_code":"dcs", "title":"Command Renaming", "uri":"dcs-ug-1009002.html", "doc_type":"usermanual", - "p_code":"55", - "code":"63" + "p_code":"57", + "code":"65" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -572,8 +590,8 @@ "title":"Managing DCS Instances", "uri":"dcs-ug-0312022.html", "doc_type":"usermanual", - "p_code":"54", - "code":"64" + "p_code":"", + "code":"66" }, { "desc":"In most cases, different DCS instance management operations cannot proceed concurrently. If you initiate a new management operation while the current operation is in prog", @@ -581,8 +599,8 @@ "title":"Configuration Notice", "uri":"dcs-ug-0312023.html", "doc_type":"usermanual", - "p_code":"64", - "code":"65" + "p_code":"66", + "code":"67" }, { "desc":"You can modify the configuration parameters of your DCS instance to optimize DCS performance based on your requirements.For example, if you do not need data persistence, ", @@ -590,8 +608,8 @@ "title":"Modifying Configuration Parameters", "uri":"dcs-ug-0312024.html", "doc_type":"usermanual", - "p_code":"64", - "code":"66" + "p_code":"66", + "code":"68" }, { "desc":"On the DCS console, after creating a DCS instance, you can modify the maintenance time window of the DCS instance on the instance's Basic Information page.At least one DC", @@ -599,8 +617,8 @@ "title":"Modifying Maintenance Time Window", "uri":"dcs-ug-0312025.html", "doc_type":"usermanual", - "p_code":"64", - "code":"67" + "p_code":"66", + "code":"69" }, { "desc":"On the DCS console, after creating a DCS instance, you can modify the security group of the DCS instance on the instance's Basic Information page.You can modify the secur", @@ -608,8 +626,8 @@ "title":"Modifying the Security Group", "uri":"dcs-ug-0312026.html", "doc_type":"usermanual", - "p_code":"64", - "code":"68" + "p_code":"66", + "code":"70" }, { "desc":"After you initiate certain instance operations such as modifying instance specifications and changing or resetting a password, a background task will start for the operat", @@ -617,8 +635,8 @@ "title":"Viewing Background Tasks", "uri":"dcs-ug-0312028.html", "doc_type":"usermanual", - "p_code":"64", - "code":"69" + "p_code":"66", + "code":"71" }, { "desc":"You can view the data storage statistics of all nodes of a DCS Redis 3.0 Proxy Cluster instance. If data storage is unevenly distributed across nodes, you can scale up th", @@ -626,44 +644,44 @@ "title":"Viewing Data Storage Statistics of a DCS Redis 3.0 Proxy Cluster Instance", "uri":"dcs-ug-0312029.html", "doc_type":"usermanual", - "p_code":"64", - "code":"70" + "p_code":"66", + "code":"72" }, { - "desc":"This section describes how to query the shards and replicas of a DCS Redis 4.0 or 5.0 instance and how to manually promote a replica to master.Currently, this function is", + "desc":"This section describes how to query the shards and replicas of a DCS Redis 4.0/5.0/6.0 instance and how to manually promote a replica to master.Currently, this function i", "product_code":"dcs", "title":"Managing Shards and Replicas", "uri":"dcs-ug-210107001.html", "doc_type":"usermanual", - "p_code":"64", - "code":"71" + "p_code":"66", + "code":"73" }, { "desc":"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", "product_code":"dcs", - "title":"Cache Analysis", + "title":"Analyzing Big Keys and Hot Keys", "uri":"dcs-ug-190808001.html", "doc_type":"usermanual", - "p_code":"64", - "code":"72" + "p_code":"66", + "code":"74" }, { - "desc":"DCS helps you control access to your DCS instances in the following ways, depending on the deployment mode:To control access to Redis 3.0 instances, you can use security ", + "desc":"DCS helps you control access to your DCS instances in the following ways, depending on the deployment mode:To control access to DCS Redis 3.0 instances, you can use secur", "product_code":"dcs", "title":"Managing IP Address Whitelist", "uri":"dcs-ug-190812001.html", "doc_type":"usermanual", - "p_code":"64", - "code":"73" + "p_code":"66", + "code":"75" }, { "desc":"Redis logs queries that exceed a specified execution time. You can view the slow query log on the DCS console to identify performance issues.For details about the command", "product_code":"dcs", - "title":"Viewing Redis Slow Logs", + "title":"Viewing Redis Slow Queries", "uri":"dcs-ug-190926001.html", "doc_type":"usermanual", - "p_code":"64", - "code":"74" + "p_code":"66", + "code":"76" }, { "desc":"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 l", @@ -671,8 +689,17 @@ "title":"Viewing Redis Run Logs", "uri":"dcs-ug-1009001.html", "doc_type":"usermanual", - "p_code":"64", - "code":"75" + "p_code":"66", + "code":"77" + }, + { + "desc":"DCS Redis 6.0instances support SSL encryption to ensure data transmission security. This function is not available for other instance versions. RESP (REdis Serialization ", + "product_code":"dcs", + "title":"Configuring SSL", + "uri":"dcs-ug-023129.html", + "doc_type":"usermanual", + "p_code":"66", + "code":"78" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -680,8 +707,8 @@ "title":"Backing Up and Restoring DCS Instances", "uri":"dcs-ug-0312030.html", "doc_type":"usermanual", - "p_code":"54", - "code":"76" + "p_code":"", + "code":"79" }, { "desc":"On the DCS console, you can back up and restore DCS instances.There is a small chance that inconsistent data could exist in a DCS instance owing to service system excepti", @@ -689,17 +716,17 @@ "title":"Overview", "uri":"en-us_topic_0079835992.html", "doc_type":"usermanual", - "p_code":"76", - "code":"77" + "p_code":"79", + "code":"80" }, { - "desc":"On the DCS console, you can configure an automatic backup policy. The system then backs up data in your instances according to the backup policy.If automatic backup is no", + "desc":"On the DCS console, you can configure an automatic backup policy. The system then backs up data in your instances according to the backup policy.By default, automatic bac", "product_code":"dcs", - "title":"Configuring a Backup Policy", + "title":"Configuring an Automatic Backup Policy", "uri":"dcs-ug-0312031.html", "doc_type":"usermanual", - "p_code":"76", - "code":"78" + "p_code":"79", + "code":"81" }, { "desc":"You need to manually back up data in DCS instances in a timely manner. This section describes how to manually back up data in master/standby instances using the DCS conso", @@ -707,8 +734,8 @@ "title":"Manually Backing Up a DCS Instance", "uri":"dcs-ug-0312032.html", "doc_type":"usermanual", - "p_code":"76", - "code":"79" + "p_code":"79", + "code":"82" }, { "desc":"On the DCS console, you can restore backup data to a chosen DCS instance.At least one master/standby or cluster DCS instance is in the Running state.A backup task has bee", @@ -716,17 +743,17 @@ "title":"Restoring a DCS Instance", "uri":"dcs-ug-0312033.html", "doc_type":"usermanual", - "p_code":"76", - "code":"80" + "p_code":"79", + "code":"83" }, { - "desc":"Due to the limitations of automatic and manual backups (automatically backed up data can be retained for a maximum of 7 days, and manually backed up data takes space in O", + "desc":"Automatically backed up data can be retained for a maximum of 7 days. Manually backed up data is not free of charge and takes space in OBS. Due to these limitations, you ", "product_code":"dcs", "title":"Downloading a Backup File", "uri":"dcs-ug-0312034.html", "doc_type":"usermanual", - "p_code":"76", - "code":"81" + "p_code":"79", + "code":"84" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -734,17 +761,17 @@ "title":"Migrating Data with DCS", "uri":"dcs-ug-0312035.html", "doc_type":"usermanual", - "p_code":"54", - "code":"82" + "p_code":"", + "code":"85" }, { - "desc":"DCS for Redis provides the following migration modes:Backup file import: The data source can be an OBS bucket or a Redis instance.Importing data from an OBS bucket: Downl", + "desc":"DCS for Redis supports online migration (in full or incrementally) and backup migration (by importing backup files).Backup migration is suitable when the source and targe", "product_code":"dcs", "title":"Introduction to Migration with DCS", "uri":"dcs-ug-0312036.html", "doc_type":"usermanual", - "p_code":"82", - "code":"83" + "p_code":"85", + "code":"86" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -752,8 +779,8 @@ "title":"Importing Backup Files", "uri":"dcs-ug-210922001.html", "doc_type":"usermanual", - "p_code":"82", - "code":"84" + "p_code":"85", + "code":"87" }, { "desc":"Use the DCS console to migrate Redis data from Redis of other vendors or self-hosted Redis to DCS for Redis.Simply download the source Redis data and then upload the data", @@ -761,8 +788,8 @@ "title":"Importing Backup Files from an OBS Bucket", "uri":"dcs-ug-0312037.html", "doc_type":"usermanual", - "p_code":"84", - "code":"85" + "p_code":"87", + "code":"88" }, { "desc":"Use the DCS console to migrate Redis data from self-hosted Redis to DCS for Redis.Simply back up your Redis data, create a migration task on the DCS console, and then imp", @@ -770,8 +797,8 @@ "title":"Importing Backup Files from Redis", "uri":"dcs-ug-210226001.html", "doc_type":"usermanual", - "p_code":"84", - "code":"86" + "p_code":"87", + "code":"89" }, { "desc":"If the source and target instances are interconnected and the SYNC and PSYNC commands are supported in the source instance, data can be migrated online in full or increme", @@ -779,8 +806,8 @@ "title":"Migrating Data Online", "uri":"dcs-ug-0312038.html", "doc_type":"usermanual", - "p_code":"82", - "code":"87" + "p_code":"85", + "code":"90" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -788,8 +815,8 @@ "title":"Managing Passwords", "uri":"dcs-ug-0312039.html", "doc_type":"usermanual", - "p_code":"54", - "code":"88" + "p_code":"", + "code":"91" }, { "desc":"Passwords can be configured to control access to your DCS instances, ensuring the security of your data.After 5 consecutive incorrect password attempts, the account for a", @@ -797,8 +824,8 @@ "title":"DCS Instance Passwords", "uri":"cache-instance-password.html", "doc_type":"usermanual", - "p_code":"88", - "code":"89" + "p_code":"91", + "code":"92" }, { "desc":"On the DCS console, you can change the password required for accessing your DCS instance.You cannot change the password of a DCS instance in password-free mode.The DCS in", @@ -806,8 +833,53 @@ "title":"Changing Instance Passwords", "uri":"dcs-ug-0312040.html", "doc_type":"usermanual", - "p_code":"88", - "code":"90" + "p_code":"91", + "code":"93" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"dcs", + "title":"Parameter Templates", + "uri":"dcs-ug-210622001.html", + "doc_type":"usermanual", + "p_code":"", + "code":"94" + }, + { + "desc":"This section describes how to view parameter templates on the DCS console.Currently, you can enter a keyword in the search box to search for a parameter template by templ", + "product_code":"dcs", + "title":"Viewing Parameter Templates", + "uri":"dcs-ug-210622002.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"95" + }, + { + "desc":"You can create custom parameter templates for different cache engine versions and instance types based on service requirements.If you select Default Templates, click Cust", + "product_code":"dcs", + "title":"Creating a Custom Parameter Template", + "uri":"dcs-ug-210622003.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"96" + }, + { + "desc":"You can modify the name, description, and parameters of a custom parameter template based on service requirements.Click Edit in the Operation column.Change the name or mo", + "product_code":"dcs", + "title":"Modifying a Custom Parameter Template", + "uri":"dcs-ug-210622004.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"97" + }, + { + "desc":"This section describes how to delete a custom parameter template.", + "product_code":"dcs", + "title":"Deleting a Custom Parameter Template", + "uri":"dcs-ug-210622005.html", + "doc_type":"usermanual", + "p_code":"94", + "code":"98" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -816,7 +888,7 @@ "uri":"dcs-ug-0326016.html", "doc_type":"usermanual", "p_code":"", - "code":"91" + "code":"99" }, { "desc":"This section describes DCS metrics reported to Cloud Eye as well as their namespaces and dimensions. You can use the Cloud Eye console or call APIs to query the DCS metri", @@ -824,8 +896,8 @@ "title":"DCS Metrics", "uri":"dcs-ug-0326019.html", "doc_type":"usermanual", - "p_code":"91", - "code":"92" + "p_code":"99", + "code":"100" }, { "desc":"You can view DCS instance metrics on the Performance Monitoring page.You can also click View Metric in the Operation column on the Cache Manager page. You will be redirec", @@ -833,8 +905,8 @@ "title":"Viewing DCS Monitoring Metrics", "uri":"dcs-ug-0312045.html", "doc_type":"usermanual", - "p_code":"91", - "code":"93" + "p_code":"99", + "code":"101" }, { "desc":"This section describes the alarm rules of some metrics and how to configure the rules. In actual scenarios, configure alarm rules for metrics by referring to the followin", @@ -842,8 +914,8 @@ "title":"Configuring Alarm Rules for Critical Metrics", "uri":"dcs-ug-190905001.html", "doc_type":"usermanual", - "p_code":"91", - "code":"94" + "p_code":"99", + "code":"102" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -852,7 +924,7 @@ "uri":"dcs-ug-0326017.html", "doc_type":"usermanual", "p_code":"", - "code":"95" + "code":"103" }, { "desc":"With CTS, you can query, audit, and review operations performed on cloud resources. Traces include the operation requests sent using the management console or open APIs a", @@ -860,8 +932,8 @@ "title":"Operations That Can Be Recorded by CTS", "uri":"dcs-ug-0326018.html", "doc_type":"usermanual", - "p_code":"95", - "code":"96" + "p_code":"103", + "code":"104" }, { "desc":"After CTS is enabled, the tracker starts recording operations on cloud resources. Operation records for the last seven days can be viewed on the CTS console. This section", @@ -869,8 +941,8 @@ "title":"Viewing Traces on the CTS Console", "uri":"dcs-ug-0312047.html", "doc_type":"usermanual", - "p_code":"95", - "code":"97" + "p_code":"103", + "code":"105" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -879,7 +951,7 @@ "uri":"dcs-faq-0326019.html", "doc_type":"usermanual", "p_code":"", - "code":"98" + "code":"106" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -887,26 +959,26 @@ "title":"Client and Network Connection", "uri":"dcs-faq-0326020.html", "doc_type":"usermanual", - "p_code":"98", - "code":"99" + "p_code":"106", + "code":"107" }, { - "desc":"DCS Redis 3.0/4.0/5.0 instances are deployed in different modes. Therefore, the access control method varies.To control access to DCS Redis 3.0 instances, you can use sec", + "desc":"DCS helps you control access to your DCS instances in the following ways, depending on the deployment mode:To control access to DCS Redis 3.0 instances, you can use secur", "product_code":"dcs", "title":"Security Group Configurations", "uri":"en-us_topic_0090662012.html", "doc_type":"usermanual", - "p_code":"99", - "code":"100" + "p_code":"107", + "code":"108" }, { "desc":"No. DCS instances cannot be access at their EIPs over public networks. To ensure security, the ECS that serves as a client and the DCS instance that the client will acces", "product_code":"dcs", - "title":"Does DCS Support Public Access?", + "title":"Does DCS Support Access over Public Networks?", "uri":"dcs-faq-0730001.html", "doc_type":"usermanual", - "p_code":"99", - "code":"101" + "p_code":"107", + "code":"109" }, { "desc":"Cross-VPC means the client and the instance are not in the same VPC.Generally, VPCs are isolated from each other and ECSs cannot access DCS instances that belong to a dif", @@ -914,8 +986,17 @@ "title":"Does DCS Support Cross-VPC Access?", "uri":"en-us_topic_0100698850.html", "doc_type":"usermanual", - "p_code":"99", - "code":"102" + "p_code":"107", + "code":"110" + }, + { + "desc":"This is because you have enabled password-free access for the instance. To prevent the error message from appearing, do not enter any password.", + "product_code":"dcs", + "title":"Why Is \"(error) NOAUTH Authentication required\" Displayed When I Access a DCS Redis Instance?", + "uri":"dcs-faq-0427005.html", + "doc_type":"usermanual", + "p_code":"107", + "code":"111" }, { "desc":"Analysis: If persistent connections (\"pconnect\" in Redis terminology) or connection pooling is used and connections are closed after being used for connecting to DCS inst", @@ -923,8 +1004,8 @@ "title":"What Should I Do If Access to DCS Fails After Server Disconnects?", "uri":"dcs-faq-0730004.html", "doc_type":"usermanual", - "p_code":"99", - "code":"103" + "p_code":"107", + "code":"112" }, { "desc":"Occasional timeout errors are normal because of network connectivity and client timeout configurations.You are advised to include reconnection operations into your servic", @@ -932,8 +1013,8 @@ "title":"Why Do Requests Sometimes Time Out in Clients?", "uri":"dcs-faq-0730005.html", "doc_type":"usermanual", - "p_code":"99", - "code":"104" + "p_code":"107", + "code":"113" }, { "desc":"The error message that will possibly be displayed when you use the Jedis connection pool is as follows:If this error message is displayed, check whether your instance is ", @@ -941,8 +1022,8 @@ "title":"What Should I Do If an Error Is Returned When I Use the Jedis Connection Pool?", "uri":"dcs-faq-0730006.html", "doc_type":"usermanual", - "p_code":"99", - "code":"105" + "p_code":"107", + "code":"114" }, { "desc":"The possible causes are as follows:The command is spelled incorrectly.As shown in the following figure, the error message is returned because the correct command for dele", @@ -950,8 +1031,8 @@ "title":"Why Is \"ERR unknown command\" Displayed When I Access a DCS Redis Instance Through a Redis Client?", "uri":"dcs-faq-0730007.html", "doc_type":"usermanual", - "p_code":"99", - "code":"106" + "p_code":"107", + "code":"115" }, { "desc":"You can access a DCS Redis instance through the Redis Desktop Manager within a VPC.Enter the address, port number (6379), and authentication password of the DCS instance ", @@ -959,8 +1040,8 @@ "title":"How Do I Access a DCS Redis Instance Through Redis Desktop Manager?", "uri":"dcs-faq-0730008.html", "doc_type":"usermanual", - "p_code":"99", - "code":"107" + "p_code":"107", + "code":"116" }, { "desc":"By using DCS Redis instances, Spring Session can implement session sharing. When interconnecting with Spring Cloud, the following error information is displayed:For secur", @@ -968,17 +1049,17 @@ "title":"What If \"ERR Unsupported CONFIG subcommand\" is Displayed in SpringCloud?", "uri":"dcs-faq-0730009.html", "doc_type":"usermanual", - "p_code":"99", - "code":"108" + "p_code":"107", + "code":"117" }, { - "desc":"Preliminary checks:Check the connection address.Obtain the connection address from the instance basic information page on the DCS console.Obtain the connection address fr", + "desc":"A DCS Redis instance can be access with or without a password. You can directly access a DCS Redis instance through a Redis client without setting a password. However, fo", "product_code":"dcs", - "title":"How Do I Troubleshoot Redis Connection Failures?", - "uri":"dcs-faq-0730010.html", + "title":"Is a Password Required for Accessing an Instance? How Do I Set a Password?", + "uri":"dcs-faq-0427015.html", "doc_type":"usermanual", - "p_code":"99", - "code":"109" + "p_code":"107", + "code":"118" }, { "desc":"Pay attention to the following issues when using Redis for pub/sub:Your client must process messages in a timely manner.Your client subscribes to a channel. If it does no", @@ -986,8 +1067,26 @@ "title":"What Should Be Noted When Using Redis for Pub/Sub?", "uri":"dcs-faq-0730011.html", "doc_type":"usermanual", - "p_code":"99", - "code":"110" + "p_code":"107", + "code":"119" + }, + { + "desc":"Preliminary checks:Check the connection address.Obtain the connection address from the instance basic information page on the DCS console.Obtain the connection address fr", + "product_code":"dcs", + "title":"How Do I Troubleshoot Redis Connection Failures?", + "uri":"dcs-faq-0730010.html", + "doc_type":"usermanual", + "p_code":"107", + "code":"120" + }, + { + "desc":"Error message \"Cannot assign requested address\" is returned when you access Redis using connect.Applications that encounter this error typically use php-fpm and phpredis.", + "product_code":"dcs", + "title":"What Can I Do If Error \"Cannot assign requested address\" Is Returned When I Access Redis Using connect?", + "uri":"dcs-faq-210721003.html", + "doc_type":"usermanual", + "p_code":"107", + "code":"121" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -995,8 +1094,8 @@ "title":"Redis Usage", "uri":"dcs-faq-0326021.html", "doc_type":"usermanual", - "p_code":"98", - "code":"111" + "p_code":"106", + "code":"122" }, { "desc":"Possible cause 1:The service QPS is so high that the CPU usage spikes to 100%.The service QPS is so high that the CPU usage spikes to 100%.Possible cause 2:You have run c", @@ -1004,8 +1103,8 @@ "title":"Why Is CPU Usage of a DCS Redis Instance 100%?", "uri":"dcs-faq-0730012.html", "doc_type":"usermanual", - "p_code":"111", - "code":"112" + "p_code":"122", + "code":"123" }, { "desc":"No. Once an instance is created, its VPC and subnet cannot be changed. If you want to use a different set of VPC and subnet, create a same instance and specify a desired ", @@ -1013,17 +1112,17 @@ "title":"Can I Change the VPC and Subnet for a DCS Redis Instance?", "uri":"dcs-faq-0730013.html", "doc_type":"usermanual", - "p_code":"111", - "code":"113" + "p_code":"122", + "code":"124" }, { - "desc":"Currently, DCS Redis 4.0 and Redis 5.0 instances use VPC endpoints and do not support security groups. You can configure whitelists instead. For details, see Managing IP ", + "desc":"Currently, DCS Redis 4.0/5.0/6.0 instances use VPC endpoints and do not support security groups. You can configure whitelists instead. For details, see Managing IP Addres", "product_code":"dcs", - "title":"Why Aren't Security Groups Configured for DCS Redis 4.0 and 5.0 Instances?", + "title":"Why Aren't Security Groups Configured for DCS Redis 4.0/5.0/6.0 Instances?", "uri":"dcs-faq-0730014.html", "doc_type":"usermanual", - "p_code":"111", - "code":"114" + "p_code":"122", + "code":"125" }, { "desc":"The maximum allowed size of a key is 512 MB.To reduce memory usage and facilitate key query, ensure that each key does not exceed 1 KB.To reduce memory usage and facilita", @@ -1031,8 +1130,8 @@ "title":"Do DCS Redis Instances Limit the Size of a Key or Value?", "uri":"dcs-faq-0730015.html", "doc_type":"usermanual", - "p_code":"111", - "code":"115" + "p_code":"122", + "code":"126" }, { "desc":"Cluster DCS Redis 3.0 instances (Proxy Cluster type) are used in the same way that you use single-node or master/standby instances. You do not need to know the backend no", @@ -1040,17 +1139,17 @@ "title":"Can I Obtain the Addresses of the Nodes in a Cluster DCS Redis Instance?", "uri":"dcs-faq-0730017.html", "doc_type":"usermanual", - "p_code":"111", - "code":"116" + "p_code":"122", + "code":"127" }, { - "desc":"DCS Redis 3.0 instances are deployed on VMs and some memory is reserved for system overheads.", + "desc":"DCS Redis 3.0 instances are deployed on VMs and some memory is reserved for system overheads. This problem will not occur on other instance versions.", "product_code":"dcs", - "title":"Why Is Available Memory of a DCS Redis 3.0 Instance Smaller Than Instance Cache Size?", + "title":"Why Is Available Memory Smaller Than Instance Cache Size?", "uri":"dcs-faq-0730018.html", "doc_type":"usermanual", - "p_code":"111", - "code":"117" + "p_code":"122", + "code":"128" }, { "desc":"Both single-node and master/standby DCS Redis instances support multiple databases. By default, single-node and master/standby DCS instances can read and write data in 25", @@ -1058,8 +1157,8 @@ "title":"Does DCS for Redis Support Multiple Databases?", "uri":"dcs-faq-0730019.html", "doc_type":"usermanual", - "p_code":"111", - "code":"118" + "p_code":"122", + "code":"129" }, { "desc":"Yes. DCS for Redis 4.0 and 5.0 support Redis Clusters. DCS for Redis 3.0 supports Proxy Clusters.", @@ -1067,17 +1166,17 @@ "title":"Does DCS for Redis Support Redis Clusters?", "uri":"dcs-faq-0730020.html", "doc_type":"usermanual", - "p_code":"111", - "code":"119" + "p_code":"122", + "code":"130" }, { - "desc":"Yes. Redis Sentinel is supported by DCS for Redis 4.0 and 5.0 and is enabled by default. Sentinel constantly checks if master and replica nodes are running properly. If t", + "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", "product_code":"dcs", "title":"Does DCS for Redis Support Sentinel?", "uri":"dcs-faq-0730021.html", "doc_type":"usermanual", - "p_code":"111", - "code":"120" + "p_code":"122", + "code":"131" }, { "desc":"Data is evicted from cache based on a user-defined space limit in order to make space for new data.You can change the eviction policy by configuring the maxmemory-policy ", @@ -1085,8 +1184,8 @@ "title":"What Is the Default Data Eviction Policy?", "uri":"dcs-faq-0730022.html", "doc_type":"usermanual", - "p_code":"111", - "code":"121" + "p_code":"122", + "code":"132" }, { "desc":"Start the Redis exporter using the CLI. Based on the output, check for errors and troubleshoot accordingly.", @@ -1094,17 +1193,8 @@ "title":"What Should I Do If an Error Occurs in Redis Exporter?", "uri":"dcs-faq-0730023.html", "doc_type":"usermanual", - "p_code":"111", - "code":"122" - }, - { - "desc":"This is normal due to Redis functions (such as master/replica replication and lazyfree). When the memory becomes full, scale up the instance or remove unnecessary data.", - "product_code":"dcs", - "title":"Why Is Memory Usage More Than 100%?", - "uri":"dcs-faq-0730024.html", - "doc_type":"usermanual", - "p_code":"111", - "code":"123" + "p_code":"122", + "code":"133" }, { "desc":"Redisson implements lock acquisition and unlocking in the following process:Redisson lock acquisition and unlocking are implemented by running Lua scripts.During lock acq", @@ -1112,26 +1202,26 @@ "title":"Why Is Redisson Distributed Lock Not Supported by DCS Proxy Cluster Redis 3.0 Instances?", "uri":"dcs-faq-0730025.html", "doc_type":"usermanual", - "p_code":"111", - "code":"124" + "p_code":"122", + "code":"134" }, { - "desc":"You cannot customize or change the port for accessing a DCS Redis 3.0 instance. You can customize and change the port for accessing a DCS Redis 4.0 or 5.0 instance.Redis ", + "desc":"You cannot customize or change the port for accessing a DCS Redis 3.0 instance. You can customize (during instance creation) but cannot change the port for accessing a DC", "product_code":"dcs", "title":"Can I Customize or Change the Port for Accessing a DCS Instance?", "uri":"dcs-faq-0730026.html", "doc_type":"usermanual", - "p_code":"111", - "code":"125" + "p_code":"122", + "code":"135" }, { - "desc":"After a DCS instance is created, its intra-VPC connection addresses cannot be modified.For details about accessing DCS instances through clients, see Accessing a DCS Redi", + "desc":"After a DCS instance is created, its intra-VPC connection addresses cannot be modified.To use a different IP address, you must create a new instance and manually specify ", "product_code":"dcs", "title":"Can I Modify the Connection Addresses for Accessing a DCS Instance?", "uri":"dcs-faq-0730027.html", "doc_type":"usermanual", - "p_code":"111", - "code":"126" + "p_code":"122", + "code":"136" }, { "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", @@ -1139,8 +1229,8 @@ "title":"Does DCS Support Cross-AZ Deployment?", "uri":"dcs-faq-0730029.html", "doc_type":"usermanual", - "p_code":"111", - "code":"127" + "p_code":"122", + "code":"137" }, { "desc":"Possible cause: When a cluster instance is started, status and data are synchronized between the nodes of the instance. If a large amount of data is continuously written ", @@ -1148,8 +1238,8 @@ "title":"Why Does It Take a Long Time to Start a Cluster DCS Instance?", "uri":"dcs-faq-0730030.html", "doc_type":"usermanual", - "p_code":"111", - "code":"128" + "p_code":"122", + "code":"138" }, { "desc":"No. If you wish to query Redis configurations and usage information, use redis-cli. If you wish to monitor DCS Redis instance metrics, go to the Cloud Eye console. For de", @@ -1157,17 +1247,8 @@ "title":"Does DCS for Redis Provide Backend Management Software?", "uri":"dcs-faq-0730032.html", "doc_type":"usermanual", - "p_code":"111", - "code":"129" - }, - { - "desc":"Possible cause: The output buffer may have occupied an excessive amount of memory.Solution: After connecting to the instance using redis-cli, run the redis-cli --bigkeys ", - "product_code":"dcs", - "title":"Why Is Memory of a DCS Redis Instance Used Up by Just a Few Keys?", - "uri":"dcs-faq-0730033.html", - "doc_type":"usermanual", - "p_code":"111", - "code":"130" + "p_code":"122", + "code":"139" }, { "desc":"If a DCS instance is automatically deleted or manually deleted through the Redis client, its data cannot be retrieved. If you have backed up the instance, you can restore", @@ -1175,8 +1256,8 @@ "title":"Can I Recover Data from Deleted DCS Instances?", "uri":"dcs-faq-0730034.html", "doc_type":"usermanual", - "p_code":"111", - "code":"131" + "p_code":"122", + "code":"140" }, { "desc":"Symptom: \"Error in execution; nested exception is io.lettuce.core.RedisCommandExecutionException: OOM command not allowed when used memory > 'maxmemory'\" is returned duri", @@ -1184,8 +1265,8 @@ "title":"Why Is \"Error in execution\" Returned When I Access Redis?", "uri":"dcs-faq-210223001.html", "doc_type":"usermanual", - "p_code":"111", - "code":"132" + "p_code":"122", + "code":"141" }, { "desc":"Normally, Redis keys do not disappear. If a key is missing, it may have expired, been evicted, or been deleted.Perform the following checks one by one:Check whether the k", @@ -1193,8 +1274,8 @@ "title":"Why Does a Key Disappear in Redis?", "uri":"dcs-faq-210409001.html", "doc_type":"usermanual", - "p_code":"111", - "code":"133" + "p_code":"122", + "code":"142" }, { "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", @@ -1202,8 +1283,8 @@ "title":"Will Cached Data Be Retained After an Instance Is Restarted?", "uri":"dcs-faq-0220330.html", "doc_type":"usermanual", - "p_code":"111", - "code":"134" + "p_code":"122", + "code":"143" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1211,8 +1292,8 @@ "title":"Redis Commands", "uri":"dcs-faq-190921003.html", "doc_type":"usermanual", - "p_code":"98", - "code":"135" + "p_code":"106", + "code":"144" }, { "desc":"Exercise caution when clearing data.Redis 3.0Data of a DCS Redis 3.0 instance cannot be cleared on the console, and can only be cleared by the FLUSHDB or FLUSHALL command", @@ -1220,8 +1301,8 @@ "title":"How Do I Clear Redis Data?", "uri":"dcs-faq-0730036.html", "doc_type":"usermanual", - "p_code":"135", - "code":"136" + "p_code":"144", + "code":"145" }, { "desc":"Yes. For more information about Redis command compatibility, see Command Compatibility.", @@ -1229,17 +1310,17 @@ "title":"Does DCS for Redis Support the INCR and EXPIRE Commands?", "uri":"dcs-faq-0730039.html", "doc_type":"usermanual", - "p_code":"135", - "code":"137" + "p_code":"144", + "code":"146" }, { - "desc":"Possible causes include the following:The command is incorrect.The command is disabled in DCS.For security purposes, some Redis commands are disabled in DCS. For details ", + "desc":"Possible causes include the following:The command is incorrect.As shown in the following figure, the error message is returned because the correct command for deleting a ", "product_code":"dcs", "title":"Why Do I Fail to Execute Some Redis Commands?", "uri":"dcs-faq-0730040.html", "doc_type":"usermanual", - "p_code":"135", - "code":"138" + "p_code":"144", + "code":"147" }, { "desc":"Run the command in redis-cli to check whether the command takes effect.The following describes two scenarios:Scenario 1: Set and query the value of a key to check whether", @@ -1247,17 +1328,35 @@ "title":"Why Does a Redis Command Fail to Take Effect?", "uri":"dcs-faq-0730041.html", "doc_type":"usermanual", - "p_code":"135", - "code":"139" + "p_code":"144", + "code":"148" }, { - "desc":"The time limit for executing a Redis command is 1 minute. This limit cannot be configured. After the execution of a command times out, your client will be automatically d", + "desc":"Redis command timeouts can be controlled on the client end or server end.Timeouts on the client end are controlled in the client code. You can determine the timeouts that", "product_code":"dcs", "title":"Is There a Time Limit on Executing Redis Commands? What Will Happen If a Command Times Out?", - "uri":"dcs-faq-0730042.html", + "uri":"dcs-faq-0427057.html", "doc_type":"usermanual", - "p_code":"135", - "code":"140" + "p_code":"144", + "code":"149" + }, + { + "desc":"No. Like in open-source Redis, keys in DCS for Redis are case-sensitive and cannot be configured to be case-insensitive.", + "product_code":"dcs", + "title":"Can I Configure Redis Keys to Be Case-Insensitive?", + "uri":"dcs-faq-0427058.html", + "doc_type":"usermanual", + "p_code":"144", + "code":"150" + }, + { + "desc":"No. Redis does not record commands and does not support viewing the most frequently used commands.", + "product_code":"dcs", + "title":"Can I View the Most Frequently Used Redis Commands?", + "uri":"dcs-faq-0624001.html", + "doc_type":"usermanual", + "p_code":"144", + "code":"151" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1265,17 +1364,17 @@ "title":"Instance Scaling and Upgrade", "uri":"dcs-faq-0326022.html", "doc_type":"usermanual", - "p_code":"98", - "code":"141" + "p_code":"106", + "code":"152" }, { - "desc":"No. Different Redis versions use different underlying architectures. The Redis version used by a DCS instance cannot be changed once the instance is created. However, you", + "desc":"No. Different Redis versions use different underlying architectures. The Redis version used by a DCS instance cannot be changed once the instance is created. For example,", "product_code":"dcs", - "title":"Can DCS Redis Instances Be Upgraded, for Example, from Redis 3.0 to Redis 4.0 or 5.0?", + "title":"Can DCS Redis Instances Be Upgraded, for Example, from Redis 4.0 to 5.0?", "uri":"dcs-faq-0730043.html", "doc_type":"usermanual", - "p_code":"141", - "code":"142" + "p_code":"152", + "code":"153" }, { "desc":"O&M personnel will contact you before performing maintenance during the maintenance time window, informing you of the operations and their impacts. You do not need to wor", @@ -1283,26 +1382,26 @@ "title":"Are Services Interrupted If Maintenance is Performed During the Maintenance Time Window?", "uri":"dcs-faq-0730044.html", "doc_type":"usermanual", - "p_code":"141", - "code":"143" + "p_code":"152", + "code":"154" }, { "desc":"No. Specification modifications can take place while the instance is running and do not affect any other resources.", "product_code":"dcs", - "title":"Are Instance Resources Affected During Specification Modification?", + "title":"Are Instances Stopped or Restarted During Specification Modification?", "uri":"dcs-faq-0730045.html", "doc_type":"usermanual", - "p_code":"141", - "code":"144" + "p_code":"152", + "code":"155" }, { - "desc":"You are advised to change the instance specifications during off-peak hours because specification modification has the following impacts:Impact of instance type changes:F", + "desc":"You are advised to change the instance specifications during off-peak hours because specification modification has the following impacts:Impact of scaling:Single-node and", "product_code":"dcs", "title":"Are Services Interrupted During Specification Modification?", "uri":"dcs-faq-0730047.html", "doc_type":"usermanual", - "p_code":"141", - "code":"145" + "p_code":"152", + "code":"156" }, { "desc":"Specifications of a DCS instance cannot be modified if another task of the instance is still running. For example, you cannot delete or scale up an instance while it is b", @@ -1310,8 +1409,8 @@ "title":"Why Can't I Modify Specifications for a DCS Redis Instance?", "uri":"dcs-faq-0730048.html", "doc_type":"usermanual", - "p_code":"141", - "code":"146" + "p_code":"152", + "code":"157" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1319,8 +1418,8 @@ "title":"Monitoring and Alarm", "uri":"dcs-faq-0326023.html", "doc_type":"usermanual", - "p_code":"98", - "code":"147" + "p_code":"106", + "code":"158" }, { "desc":"The number of connections received by a DCS instance is a metric that is monitored by Cloud Eye. For details on how to view metrics, see Viewing DCS Monitoring Metrics.On", @@ -1328,8 +1427,8 @@ "title":"How Do I View Current Concurrent Connections and Maximum Connections of a DCS Redis Instance?", "uri":"dcs-faq-0427070.html", "doc_type":"usermanual", - "p_code":"147", - "code":"148" + "p_code":"158", + "code":"159" }, { "desc":"No. To ensure high-performance reads and writes, Redis does not audit commands. Commands are not printed.", @@ -1337,8 +1436,8 @@ "title":"Does Redis Support Command Audits?", "uri":"dcs-faq-0730049.html", "doc_type":"usermanual", - "p_code":"147", - "code":"149" + "p_code":"158", + "code":"160" }, { "desc":"If you have any doubt on the monitoring data of a DCS Redis instance, you can access the instance through redis-cli and run the INFO ALL command to view the metrics. For ", @@ -1346,8 +1445,8 @@ "title":"What Should I Do If the Monitoring Data of a DCS Redis Instance Is Abnormal?", "uri":"dcs-faq-0730050.html", "doc_type":"usermanual", - "p_code":"147", - "code":"150" + "p_code":"158", + "code":"161" }, { "desc":"For single-node and master/standby DCS instances, the used instance memory is measured by the Redis-server process. For cluster DCS instances, the used cluster memory is ", @@ -1355,8 +1454,8 @@ "title":"Why Is Used Memory Greater Than Available Memory?", "uri":"dcs-faq-0730052.html", "doc_type":"usermanual", - "p_code":"147", - "code":"151" + "p_code":"158", + "code":"162" }, { "desc":"The basic information about the bandwidth usage metric is as follows.Bandwidth usage = (Input flow + Output flow)/(2 x Maximum bandwidth) x 100%According to the formula, ", @@ -1364,17 +1463,17 @@ "title":"Why Does Bandwidth Usage Exceed 100%?", "uri":"dcs-faq-0513001.html", "doc_type":"usermanual", - "p_code":"147", - "code":"152" + "p_code":"158", + "code":"163" }, { - "desc":"If the Rejected Connections metric is displayed, check if the number of connected clients exceeds the maximum allowed number of connections of the instances. To check the", + "desc":"If the Rejected Connections metric is displayed, check if the number of connected clients exceeds the maximum allowed number of connections of the instances.To check the ", "product_code":"dcs", "title":"Why Is the Rejected Connections Metric Displayed?", "uri":"dcs-faq-0603001.html", "doc_type":"usermanual", - "p_code":"147", - "code":"153" + "p_code":"158", + "code":"164" }, { "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", @@ -1382,8 +1481,8 @@ "title":"Why Is Flow Control Triggered? How Do I Handle It?", "uri":"dcs-faq-0220721.html", "doc_type":"usermanual", - "p_code":"147", - "code":"154" + "p_code":"158", + "code":"165" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1391,8 +1490,8 @@ "title":"Data Backup, Export, and Migration", "uri":"dcs-faq-0326024.html", "doc_type":"usermanual", - "p_code":"98", - "code":"155" + "p_code":"106", + "code":"166" }, { "desc":"For master/standby or cluster instances:Perform the following operations to export the data:On the Backups & Restorations page, view the backup records.If there are no ba", @@ -1400,8 +1499,8 @@ "title":"How Do I Export DCS Redis Instance Data?", "uri":"dcs-faq-0730053.html", "doc_type":"usermanual", - "p_code":"155", - "code":"156" + "p_code":"166", + "code":"167" }, { "desc":"Redis 3.0No. On the console, backup data of a DCS Redis 3.0 instance can be exported only to AOF files. To export data to RDB files, run the following command in redis-cl", @@ -1409,17 +1508,44 @@ "title":"Can I Export Backup Data of DCS Redis Instances to RDB Files Using the Console?", "uri":"dcs-faq-0730054.html", "doc_type":"usermanual", - "p_code":"155", - "code":"157" + "p_code":"166", + "code":"168" }, { - "desc":"DCS Redis instances:Single-node: Not supportedMaster/Standby and cluster: SupportedSingle-node: Not supportedMaster/Standby and cluster: Supported", + "desc":"DCS Redis instances:Single-node: Data persistence is not supported.Master/standby and cluster (except single-replica clusters): Data persistence is supported.Single-node:", "product_code":"dcs", - "title":"Does DCS Support Data Persistence?", - "uri":"dcs-faq-0730057.html", + "title":"Does DCS Support Data Persistence? What Is the Impact of Persistence?", + "uri":"dcs-faq-0427081.html", "doc_type":"usermanual", - "p_code":"155", - "code":"158" + "p_code":"166", + "code":"169" + }, + { + "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", + "product_code":"dcs", + "title":"When Will AOF Rewrites Be Triggered?", + "uri":"dcs-faq-210706001.html", + "doc_type":"usermanual", + "p_code":"166", + "code":"170" + }, + { + "desc":"No. A migration task allows data to be migrated to only one target instance. To migrate data to multiple target instances, create multiple migration tasks.", + "product_code":"dcs", + "title":"Can I Migrate Data to Multiple Target Instances in One Migration Task?", + "uri":"dcs-faq-220317.html", + "doc_type":"usermanual", + "p_code":"166", + "code":"171" + }, + { + "desc":"If the data exists on both the source and target instances, the target data is overwritten by the source data. If the data exists only on the target instance, the data wi", + "product_code":"dcs", + "title":"Will the Same Keys Be Overwritten During Data Migration or Backup Import?", + "uri":"dcs-faq-11185.html", + "doc_type":"usermanual", + "p_code":"166", + "code":"172" }, { "desc":"Rump is an open-source tool designed for migrating Redis data online. It supports migration between DBs of the same instance and between DBs of different instances.Rump u", @@ -1427,17 +1553,17 @@ "title":"Online Migration with Rump", "uri":"dcs-migration-090626001.html", "doc_type":"usermanual", - "p_code":"155", - "code":"159" + "p_code":"166", + "code":"173" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"dcs", - "title":"Analysis of Big Keys and Hot Keys", + "title":"Big/Hot Key Analysis", "uri":"dcs-faq-0805001.html", "doc_type":"usermanual", - "p_code":"98", - "code":"160" + "p_code":"106", + "code":"174" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1445,8 +1571,8 @@ "title":"What Are Big Keys and Hot Keys?", "uri":"dcs-faq-0521003.html", "doc_type":"usermanual", - "p_code":"160", - "code":"161" + "p_code":"174", + "code":"175" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1454,8 +1580,8 @@ "title":"What Is the Impact of Big Keys or Hot Keys?", "uri":"dcs-faq-0521004.html", "doc_type":"usermanual", - "p_code":"160", - "code":"162" + "p_code":"174", + "code":"176" }, { "desc":"Keep the size of Strings within 10 KB and the quantity of Hashes, Lists, Sets, or Zsets within 5000.When naming keys, use the service name abbreviation as the prefix and ", @@ -1463,8 +1589,8 @@ "title":"How Do I Avoid Big Keys and Hot Keys?", "uri":"dcs-faq-0521005.html", "doc_type":"usermanual", - "p_code":"160", - "code":"163" + "p_code":"174", + "code":"177" }, { "desc":"DCS for Redis 3.0 does not support hot key analysis on the console. Alternatively, you can use the following methods to analyze hot keys:Method 1: Analyze the service str", @@ -1472,8 +1598,8 @@ "title":"How Do I Analyze the Hot Keys of a DCS Redis 3.0 Instance?", "uri":"dcs-faq-0521006.html", "doc_type":"usermanual", - "p_code":"160", - "code":"164" + "p_code":"174", + "code":"178" }, { "desc":"Hot key analysis is not supported by DCS Redis 3.0 instances. You can configure alarms to detect hot keys.Configure alarm rules for the Memory Usage metric of the instanc", @@ -1481,8 +1607,8 @@ "title":"How Do I Detect Big Keys and Hot Keys in Advance?", "uri":"dcs-faq-0606002.html", "doc_type":"usermanual", - "p_code":"160", - "code":"165" + "p_code":"174", + "code":"179" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1490,8 +1616,8 @@ "title":"Master/Standby Switchover", "uri":"dcs-faq-191204001.html", "doc_type":"usermanual", - "p_code":"98", - "code":"166" + "p_code":"106", + "code":"180" }, { "desc":"A master/standby switchover may occur in the following scenarios:A master/standby switchover operation is initiated on the DCS Console.If the master node of a master/stan", @@ -1499,8 +1625,8 @@ "title":"When Does a Master/Standby Switchover Occur?", "uri":"dcs-faq-0730058.html", "doc_type":"usermanual", - "p_code":"166", - "code":"167" + "p_code":"180", + "code":"181" }, { "desc":"If a fault occurs in a master/standby or cluster DCS instance, a failover is triggered automatically. Services may be interrupted for less than half a minute during excep", @@ -1508,8 +1634,8 @@ "title":"How Does Master/Standby Switchover Affect Services?", "uri":"dcs-faq-0730059.html", "doc_type":"usermanual", - "p_code":"166", - "code":"168" + "p_code":"180", + "code":"182" }, { "desc":"No. If the master fails, the standby node will be promoted to master and takes the original IP address.", @@ -1517,8 +1643,8 @@ "title":"Does the Client Need to Switch the Connection Address After a Master/Standby Switchover?", "uri":"dcs-faq-0730060.html", "doc_type":"usermanual", - "p_code":"166", - "code":"169" + "p_code":"180", + "code":"183" }, { "desc":"Redis master/standby instances are also called master/slave instances. Generally, updates to the master cache node are automatically and asynchronously replicated to the ", @@ -1526,8 +1652,8 @@ "title":"How Does Redis Master/Standby Replication Work?", "uri":"dcs-faq-0730061.html", "doc_type":"usermanual", - "p_code":"166", - "code":"170" + "p_code":"180", + "code":"184" }, { "desc":"For details about the terms involved in this document, see Glossary.", @@ -1536,7 +1662,7 @@ "uri":"en-us_topic_0072429345.html", "doc_type":"usermanual", "p_code":"", - "code":"171" + "code":"185" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1545,6 +1671,6 @@ "uri":"dcs-ug-0326026.html", "doc_type":"usermanual", "p_code":"", - "code":"172" + "code":"186" } ] \ No newline at end of file diff --git a/docs/dcs/umn/CacheCluster.html b/docs/dcs/umn/CacheCluster.html index e3e48c753..bb6d995d7 100644 --- a/docs/dcs/umn/CacheCluster.html +++ b/docs/dcs/umn/CacheCluster.html @@ -1,9 +1,9 @@

Proxy Cluster Redis

-

DCS provides two types of cluster Redis instances: Proxy Cluster and Redis Cluster. Proxy Cluster uses Linux Virtual Server (LVS) and proxies. Redis Cluster is the native distributed implementation of Redis. Proxy Cluster instances are compatible with Redis 3.0, while Redis Cluster instances are compatible with Redis 4.0 and 5.0.

-

This section describes Proxy Cluster DCS Redis 3.0 instances.

-
  • A Proxy Cluster instance can be connected in the same way that a single-node or master/standby instance is connected, without any special settings on the client. You can use the IP address or domain name of the instance, and do not need to know or use the proxy or shard addresses.
+

DCS for Redis provides Proxy Cluster instances, which use Linux Virtual Server (LVS) and proxies to achieve high availability.

+

Proxy Cluster DCS Redis instances are compatible with Redis 3.0.

+
  • A Proxy Cluster instance can be connected in the same way that a single-node or master/standby instance is connected, without any special settings on the client. You can use the IP address of the instance, and do not need to know or use the proxy or shard addresses.

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.

diff --git a/docs/dcs/umn/CacheMasterSlave.html b/docs/dcs/umn/CacheMasterSlave.html index d47ba5a14..06b995095 100644 --- a/docs/dcs/umn/CacheMasterSlave.html +++ b/docs/dcs/umn/CacheMasterSlave.html @@ -1,8 +1,8 @@

Master/Standby Redis

-

This section describes master/standby DCS Redis instances. Three Redis versions are available for master/standby DCS Redis instances: Redis 3.0, Redis 4.0, and Redis 5.0.

-

You cannot upgrade the Redis version for an instance. For example, a master/standby DCS Redis 3.0 instance cannot be upgraded to a master/standby DCS Redis 4.0 or 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.

+

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 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.

Master/Standby DCS instances have the following features:

@@ -11,13 +11,11 @@
  • Data synchronization

    Data in the master and standby nodes is kept consistent through incremental synchronization.

    After recovering from a network exception or node fault, master/standby instances perform a full synchronization to ensure data consistency.

    -
  • Automatic master/standby switchover

    If the master node becomes faulty, the standby node takes over within 30 seconds, without requiring any service interruptions or manual operations.

    -
  • DR policies

    Each master/standby instance can be deployed across AZs with physically isolated power supplies and networks. Applications can also be deployed across AZs to achieve high availability for both data and applications.

    +
  • Automatic master/standby switchover

    If the master node becomes faulty, the instance is disconnected and unavailable for several seconds. The standby node takes over within 30 seconds without manual operations to resume stable services.

    +
  • DR policies

    Each master/standby DCS instance can be deployed across AZs with physically isolated power supplies and networks. Applications can also be deployed across AZs to achieve high availability for both data and applications.

    • -

    Architecture

    Figure 1 shows the architecture of master/standby DCS Redis instances.

    -

    To access a DCS Redis 3.0 instance, you must use port 6379. To access a DCS Redis 4.0 or 5.0 instance, you can customize the port. If no port is specified, the default port 6379 will be used. In the following architecture, port 6379 is used. If you have customized a port, replace 6379 with the actual port.

    -
    +

    Architecture of DCS Redis 3.0 Instances

    Figure 1 shows the architecture of master/standby DCS Redis instances.

    Figure 1 Master/Standby DCS instance architecture

    Architecture description:

    • VPC

      All server nodes of the instance run in the same VPC.

      @@ -28,9 +26,15 @@

      DCS Redis instances are compatible with the Redis protocol, and can be accessed through open-source clients. For details about accessing DCS instances, see Accessing an Instance.

    • DCS instance

      Indicates a master/standby DCS instance which has a master node and a standby node. By default, data persistence is enabled and data is synchronized between the two nodes.

      DCS monitors the availability of the instance in real time. If the master node becomes faulty, the standby node becomes the master node and resumes service provisioning.

      -

      DCS Redis instances are accessed through port 6379 by default.

      +

      DCS Redis 3.0 instances are accessed through port 6379 by default. Port customization is not supported.

    +

    Architecture of Master/Standby DCS Redis 4.0/5.0/6.0 Instances

    The following figure shows the architecture of a master/standby DCS Redis 4.0/5.0/6.0 instance.

    +
    Figure 2 Architecture of a master/standby DCS Redis 4.0/5.0/6.0 instance
    +

    Architecture description:

    +
    1. Master/standby DCS Redis 4.0/5.0/6.0 instances support Sentinels. Sentinels monitor the running status of the master and standby nodes. If the master node becomes faulty, a failover will be performed.

      Sentinels are invisible to you and is used only in the service.

      +
    2. A standby node has the same specifications as a master node. A master/standby instance consists of a pair of master and standby nodes by default.
    3. To access a DCS Redis 4.0/5.0/6.0 instance, you can customize the port. If no port is specified, the default port 6379 will be used. In the architecture diagram, port 6379 is used. If you have customized a port, replace 6379 with the actual port.
    +
    diff --git a/docs/dcs/umn/CacheProxy.html b/docs/dcs/umn/CacheProxy.html index 47a9ce48e..08e183152 100644 --- a/docs/dcs/umn/CacheProxy.html +++ b/docs/dcs/umn/CacheProxy.html @@ -1,70 +1,71 @@

    Redis Cluster

    -

    This section describes Redis Cluster DCS Redis 4.0 and 5.0 instances.

    -

    Redis Cluster DCS Redis 4.0 and 5.0 Instances

    The Redis Cluster instance type provided by DCS is compatible with the native Redis Cluster, which uses smart clients and a distributed architecture to perform sharding.

    +

    Redis Cluster DCS instances use the native distributed implementation of Redis.

    +

    Redis Cluster DCS instances are compatible with Redis 4.0 and 5.0.

    +

    Redis Cluster

    The Redis Cluster instance type provided by DCS is compatible with the native Redis Cluster, which uses smart clients and a distributed architecture to perform sharding.

    Table 1 lists the shard specification for different instance specifications.

    -

    Specification per shard=Instance specification/Number of shards. For example, if a 48 GB instance has 6 shards, the specification of each shard is 48 GB/6 = 8 GB.

    +

    Size of a shard = Instance specification/Number of shards. For example, if a 48 GB instance has 6 shards, the size of each shard is 48 GB/6 = 8 GB.

    -
    Table 1 Specifications of Redis Cluster DCS instances

    Total Memory

    +
    - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/dcs/umn/CacheSingleNode.html b/docs/dcs/umn/CacheSingleNode.html index e041e9852..1a20291c4 100644 --- a/docs/dcs/umn/CacheSingleNode.html +++ b/docs/dcs/umn/CacheSingleNode.html @@ -1,7 +1,9 @@

    Single-Node Redis

    -

    Three Redis versions are available for single-node DCS Redis instances: Redis 3.0, Redis 4.0, and Redis 5.0.

    +

    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.

    +

    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.

    3. Out-of-the-box usability and no data persistence

      Single-node DCS instances can be used out of the box because they do not involve data loading. If your service requires high QPS, you can warm up the data beforehand to avoid strong concurrency impact on the backend database.

      @@ -10,12 +12,12 @@

      In summary, single-node DCS instances support highly concurrent read/write operations, but do not support data persistence. Data will be deleted after instances are restarted. They are suitable for scenarios which do not require data persistence, such as database front-end caching, to accelerate access and ease the concurrency load off the backend. If the desired data does not exist in the cache, requests will go to the database. When restarting the service or the DCS instance, you can pre-generate cache data from the disk database to relieve pressure on the backend during startup.

    Architecture

    Figure 1 shows the architecture of single-node DCS Redis instances.

    -

    To access a DCS Redis 3.0 instance, you must use port 6379. To access a DCS Redis 4.0 or 5.0 instance, you can customize the port. If no port is specified, the default port 6379 will be used. In the following architecture, port 6379 is used. If you have customized a port, replace 6379 with the actual port.

    +

    To access a DCS Redis 3.0 instance, you must use port 6379. To access a DCS Redis 4.0/5.0/6.0 instance, you can customize the port. If no port is specified, the default port 6379 will be used. In the following architecture, port 6379 is used. If you have customized a port, replace 6379 with the actual port.

    Figure 1 Single-node DCS Redis instance architecture

    Architecture description:

    • VPC

      All server nodes of the instance run in the same VPC.

      -

      For intra-VPC access, the client and the instance must be in the same VPC with specified security group rule configurations with specified security group rule configurations.

      +

      For intra-VPC access, the client and the instance must be in the same VPC with specified security group rule configurations.

      For details, see Security Group Configurations.

    • Application

      The client of the instance, which is the application running on an Elastic Cloud Server (ECS).

      diff --git a/docs/dcs/umn/GlobalDRPolicy.html b/docs/dcs/umn/GlobalDRPolicy.html index 59e5f3e54..93dee00bd 100644 --- a/docs/dcs/umn/GlobalDRPolicy.html +++ b/docs/dcs/umn/GlobalDRPolicy.html @@ -1,10 +1,10 @@ -

      HA and DR Policies

      +

      Disaster Recovery and Multi-Active Solution

      Whether you use DCS as the frontend cache or backend data store, DCS is always ready to ensure data reliability and service availability. The following figure shows the evolution of DCS DR architectures.

      Figure 1 DCS DR architecture evolution

      To meet the reliability requirements of your data and services, you can choose to deploy your DCS instance within a single AZ or across AZs.

      -

      Single-AZ HA

      Single-AZ deployment means deploying an instance within a physical equipment room. DCS provides process/service HA, data persistence, and hot standby DR policies for different types of DCS instances.

      +

      Single-AZ HA

      Single-AZ deployment means to deploy an instance within a physical equipment room. DCS provides process/service HA, data persistence, and hot standby DR policies for different types of DCS instances.

      Single-node DCS instance: When DCS detects a process fault, a new process is started to ensure service HA.

      Figure 2 HA for a single-node DCS instance deployed within an AZ

      Master/Standby DCS instance: Data is persisted to disk in the master node and incrementally synchronized and persisted to the standby node, achieving hot standby and data persistence.

      @@ -16,8 +16,11 @@
      Figure 5 Cross-AZ deployment of a master/standby DCS instance

      This mechanism applies in a similar way to a cluster DCS instance. Each shard (process) is deployed across AZs.

      -

      When creating a master/standby or cluster DCS instance, select a standby AZ that is different from the primary AZ.

      +

      When creating a master/standby or cluster DCS instance, select a standby AZ that is different from the primary AZ. See the following figure.

      +
      Figure 6 Selecting different AZs

      Backup, configuration modification, and password change functions cannot be used during the fault.

      +

      You can deploy your application across AZs to ensure both data reliability and service availability in the event of power supply or network disruptions.

      +
      diff --git a/docs/dcs/umn/RedisDifference.html b/docs/dcs/umn/RedisDifference.html index 2dd49dbf6..20574bf11 100644 --- a/docs/dcs/umn/RedisDifference.html +++ b/docs/dcs/umn/RedisDifference.html @@ -2,63 +2,97 @@

      Comparing Redis Versions

      When creating a DCS Redis instance, you can select the cache engine version and the instance type.

      -
      • Version

        DCS supports Redis 3.0, 4.0, and 5.0. The following table describes the differences between these versions.

        +
        • Version

          DCS supports Redis 3.0/4.0/5.0/6.0. The following table describes the differences between these versions.

          -
    Table 1 Specifications of Redis Cluster DCS instances

    Total Memory

    Shards

    +

    Shards

    4 GB/8 GB/16 GB/24 GB/32 GB

    +

    4 GB/8 GB/16 GB/24 GB/32 GB

    3

    +

    3

    48 GB

    +

    48 GB

    6

    +

    6

    64 GB

    +

    64 GB

    8

    +

    8

    96 GB

    +

    96 GB

    12

    +

    12

    128 GB

    +

    128 GB

    16

    +

    16

    192 GB

    +

    192 GB

    24

    +

    24

    256 GB

    +

    256 GB

    32

    +

    32

    384 GB

    +

    384 GB

    48

    +

    48

    512 GB

    +

    512 GB

    64

    +

    64

    768 GB

    +

    768 GB

    96

    +

    96

    1024 GB

    +

    1024 GB

    128

    +

    128
    Table 1 Differences between Redis versions

    Feature

    +
    - - + - - - + - - - + - - - + - - - + - - - + - - - + - - - + + + + + + + + + + + diff --git a/docs/dcs/umn/dcs-faq-0220721.html b/docs/dcs/umn/dcs-faq-0220721.html index 323688503..804913de0 100644 --- a/docs/dcs/umn/dcs-faq-0220721.html +++ b/docs/dcs/umn/dcs-faq-0220721.html @@ -9,7 +9,7 @@
    • If flow control is always triggered when the bandwidth usage is low, there may be service microbursts or big or hot keys. In this case, check for big or hot keys.
    • If the bandwidth usage remains high, the bandwidth limit may be exceeded. In this case, expand the capacity. Larger capacity supports higher bandwidth.

    For cluster instances:

    • If flow control is triggered only on one or a few shards, the shards may have big or hot keys.
    • If flow control or high bandwidth usage occurs on all or most shards at the same time, bandwidth usage of the instance has reached the limit. In this case, expand the instance capacity.
    -

    You can analyze big keys and hot keys on the DCS console. For details, see Cache Analysis.

    +
    • You can analyze big keys and hot keys on the DCS console. For details, see Analyzing Big Keys and Hot Keys.
    • Running commands (such as KEYS) that consume lots of resources may cause high CPU and bandwidth usage. As a result, flow control is triggered.
    diff --git a/docs/dcs/umn/dcs-faq-0326019.html b/docs/dcs/umn/dcs-faq-0326019.html index ece2f3432..e419356cb 100644 --- a/docs/dcs/umn/dcs-faq-0326019.html +++ b/docs/dcs/umn/dcs-faq-0326019.html @@ -20,7 +20,7 @@
  • Data Backup, Export, and Migration
    • -
  • Analysis of Big Keys and Hot Keys
    +
  • Big/Hot Key Analysis
  • Master/Standby Switchover
    • diff --git a/docs/dcs/umn/dcs-faq-0326020.html b/docs/dcs/umn/dcs-faq-0326020.html index 45f2d3bb4..56cb9a8f7 100644 --- a/docs/dcs/umn/dcs-faq-0326020.html +++ b/docs/dcs/umn/dcs-faq-0326020.html @@ -6,10 +6,12 @@
    diff --git a/docs/dcs/umn/dcs-faq-0326021.html b/docs/dcs/umn/dcs-faq-0326021.html index 9b9813a2c..aecb80b2c 100644 --- a/docs/dcs/umn/dcs-faq-0326021.html +++ b/docs/dcs/umn/dcs-faq-0326021.html @@ -8,13 +8,13 @@
  • Can I Change the VPC and Subnet for a DCS Redis Instance?
    • -
  • Why Aren't Security Groups Configured for DCS Redis 4.0 and 5.0 Instances?
    +
  • Why Aren't Security Groups Configured for DCS Redis 4.0/5.0/6.0 Instances?
  • Do DCS Redis Instances Limit the Size of a Key or Value?
  • Can I Obtain the Addresses of the Nodes in a Cluster DCS Redis Instance?
    • -
  • Why Is Available Memory of a DCS Redis 3.0 Instance Smaller Than Instance Cache Size?
    +
  • Why Is Available Memory Smaller Than Instance Cache Size?
  • Does DCS for Redis Support Multiple Databases?
    • @@ -26,8 +26,6 @@
  • What Should I Do If an Error Occurs in Redis Exporter?
    • -
  • Why Is Memory Usage More Than 100%?
    -
  • Why Is Redisson Distributed Lock Not Supported by DCS Proxy Cluster Redis 3.0 Instances?
  • Can I Customize or Change the Port for Accessing a DCS Instance?
    @@ -40,8 +38,6 @@
  • Does DCS for Redis Provide Backend Management Software?
    • -
  • Why Is Memory of a DCS Redis Instance Used Up by Just a Few Keys?
    -
  • Can I Recover Data from Deleted DCS Instances?
  • Why Is "Error in execution" Returned When I Access Redis?
    diff --git a/docs/dcs/umn/dcs-faq-0326022.html b/docs/dcs/umn/dcs-faq-0326022.html index 287c7f7dd..78501d852 100644 --- a/docs/dcs/umn/dcs-faq-0326022.html +++ b/docs/dcs/umn/dcs-faq-0326022.html @@ -4,11 +4,11 @@
      -
    • Can DCS Redis Instances Be Upgraded, for Example, from Redis 3.0 to Redis 4.0 or 5.0?
      +
    • Can DCS Redis Instances Be Upgraded, for Example, from Redis 4.0 to 5.0?
    • Are Services Interrupted If Maintenance is Performed During the Maintenance Time Window?
      • -
    • Are Instance Resources Affected During Specification Modification?
      +
    • Are Instances Stopped or Restarted During Specification Modification?
    • Are Services Interrupted During Specification Modification?
      • diff --git a/docs/dcs/umn/dcs-faq-0326024.html b/docs/dcs/umn/dcs-faq-0326024.html index 033f43acb..7d943511e 100644 --- a/docs/dcs/umn/dcs-faq-0326024.html +++ b/docs/dcs/umn/dcs-faq-0326024.html @@ -8,7 +8,13 @@
    • Can I Export Backup Data of DCS Redis Instances to RDB Files Using the Console?
      • -
    • Does DCS Support Data Persistence?
      +
    • Does DCS Support Data Persistence? What Is the Impact of Persistence?
      +
      • +
    • When Will AOF Rewrites Be Triggered?
      +
      • +
    • Can I Migrate Data to Multiple Target Instances in One Migration Task?
      +
      • +
    • Will the Same Keys Be Overwritten During Data Migration or Backup Import?
    • Online Migration with Rump
      • diff --git a/docs/dcs/umn/dcs-faq-0427005.html b/docs/dcs/umn/dcs-faq-0427005.html new file mode 100644 index 000000000..0ee2dfd7c --- /dev/null +++ b/docs/dcs/umn/dcs-faq-0427005.html @@ -0,0 +1,11 @@ + + +

      Why Is "(error) NOAUTH Authentication required" Displayed When I Access a DCS Redis Instance?

      +

      This is because you have enabled password-free access for the instance. To prevent the error message from appearing, do not enter any password.

      +
      +
      +
      +
      Parent topic: Client and Network Connection
      +
      +
      + diff --git a/docs/dcs/umn/dcs-faq-0427015.html b/docs/dcs/umn/dcs-faq-0427015.html new file mode 100644 index 000000000..2460841f9 --- /dev/null +++ b/docs/dcs/umn/dcs-faq-0427015.html @@ -0,0 +1,11 @@ + + +

      Is a Password Required for Accessing an Instance? How Do I Set a Password?

      +
      • A DCS Redis instance can be access with or without a password. You can directly access a DCS Redis instance through a Redis client without setting a password. However, for security purposes, you are advised to set a password for authentication and verification whenever possible. The password must be set when you create the instance.
      • To change the Redis instance access mode, or change or reset a password, see Managing Passwords.
      +
      +
      +
      +
      Parent topic: Client and Network Connection
      +
      +
      + diff --git a/docs/dcs/umn/dcs-faq-0427057.html b/docs/dcs/umn/dcs-faq-0427057.html new file mode 100644 index 000000000..7c39d0f3f --- /dev/null +++ b/docs/dcs/umn/dcs-faq-0427057.html @@ -0,0 +1,12 @@ + + +

      Is There a Time Limit on Executing Redis Commands? What Will Happen If a Command Times Out?

      +

      Redis command timeouts can be controlled on the client end or server end.

      +
      • Timeouts on the client end are controlled in the client code. You can determine the timeouts that suit service needs. For example, if you use Lettuce, a Java client, configure the timeout parameter.
      • On the server end, the timeout parameter is set to 0 by default, indicating that connections will never be terminated. Modify the parameter setting by referring to Modifying Configuration Parameters.
      +
      +
      +
      +
      Parent topic: Redis Commands
      +
      +
      + diff --git a/docs/dcs/umn/dcs-faq-0427058.html b/docs/dcs/umn/dcs-faq-0427058.html new file mode 100644 index 000000000..8dfc4fc6d --- /dev/null +++ b/docs/dcs/umn/dcs-faq-0427058.html @@ -0,0 +1,11 @@ + + +

      Can I Configure Redis Keys to Be Case-Insensitive?

      +

      No. Like in open-source Redis, keys in DCS for Redis are case-sensitive and cannot be configured to be case-insensitive.

      +
      +
      +
      +
      Parent topic: Redis Commands
      +
      +
      + diff --git a/docs/dcs/umn/dcs-faq-0427081.html b/docs/dcs/umn/dcs-faq-0427081.html new file mode 100644 index 000000000..16eda5dbf --- /dev/null +++ b/docs/dcs/umn/dcs-faq-0427081.html @@ -0,0 +1,22 @@ + + +

      Does DCS Support Data Persistence? What Is the Impact of Persistence?

      +

      Support for Persistence

      • DCS Redis instances:
        • Single-node: Data persistence is not supported.
        • Master/standby and cluster (except single-replica clusters): Data persistence is supported.
        +
      +
      +

      Persistence Modes

      • DCS supports only AOF persistence by default. You can enable or disable persistence as required. All instances except single-node and single-replica cluster ones are created with AOF persistence enabled.
      • DCS does not support RDB persistence by default and you cannot configure the save parameter. If RDB persistence is required for a master/standby or cluster instance of Redis 4.0 or later, you can use the backup and restoration function to back up the instance data to an RDB file and store the data in OBS.
      +
      +

      Disk Used for Persistence

      For DCS Redis 4.0 and later instances, data is persisted to SSD disks.

      +
      +

      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).

      +

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

      +
      +
      + + diff --git a/docs/dcs/umn/dcs-faq-0521003.html b/docs/dcs/umn/dcs-faq-0521003.html index ee0c493b9..934ad0f25 100644 --- a/docs/dcs/umn/dcs-faq-0521003.html +++ b/docs/dcs/umn/dcs-faq-0521003.html @@ -26,7 +26,7 @@
    diff --git a/docs/dcs/umn/dcs-faq-0521004.html b/docs/dcs/umn/dcs-faq-0521004.html index fd1c650e4..4d0c9a19a 100644 --- a/docs/dcs/umn/dcs-faq-0521004.html +++ b/docs/dcs/umn/dcs-faq-0521004.html @@ -54,7 +54,7 @@
    • diff --git a/docs/dcs/umn/dcs-faq-0521005.html b/docs/dcs/umn/dcs-faq-0521005.html index 09d061bf9..f9ef29fa2 100644 --- a/docs/dcs/umn/dcs-faq-0521005.html +++ b/docs/dcs/umn/dcs-faq-0521005.html @@ -38,7 +38,7 @@
    diff --git a/docs/dcs/umn/dcs-faq-0521006.html b/docs/dcs/umn/dcs-faq-0521006.html index 3178037aa..a6146aa16 100644 --- a/docs/dcs/umn/dcs-faq-0521006.html +++ b/docs/dcs/umn/dcs-faq-0521006.html @@ -11,7 +11,7 @@
    diff --git a/docs/dcs/umn/dcs-faq-0603001.html b/docs/dcs/umn/dcs-faq-0603001.html index 42aedde14..30e6f1a1a 100644 --- a/docs/dcs/umn/dcs-faq-0603001.html +++ b/docs/dcs/umn/dcs-faq-0603001.html @@ -1,7 +1,9 @@

    Why Is the Rejected Connections Metric Displayed?

    -

    If the Rejected Connections metric is displayed, check if the number of connected clients exceeds the maximum allowed number of connections of the instances. To check the maximum allowed number of connections, go to the Parameters tab page of the instance and check the value of the maxclients parameter.

    +

    If the Rejected Connections metric is displayed, check if the number of connected clients exceeds the maximum allowed number of connections of the instances.

    +
    • To check the maximum allowed number of connections, go to the Parameters tab page of the instance and check the value of the maxclients parameter. (Proxy Cluster instances do not have this parameter. You can view the maximum number of connections on the instance creation page.)
    • To check the current number of connections, go to the Performance Monitoring tab page of the instance and check the Connected Clients metric.
    +

    If the current number of connections reaches the upper limit, you can adjust the value of maxclients. If the value of maxclients can no longer be increased, increase the instance specifications.

    diff --git a/docs/dcs/umn/dcs-faq-0606002.html b/docs/dcs/umn/dcs-faq-0606002.html index fa28c7bd0..df9b69ba1 100644 --- a/docs/dcs/umn/dcs-faq-0606002.html +++ b/docs/dcs/umn/dcs-faq-0606002.html @@ -10,7 +10,7 @@
    - - -
    Table 1 Differences between Redis versions

    Feature

    Redis 3.0

    +

    Redis 3.0

    Redis 4.0 and Redis 5.0

    +

    Redis 4.0 & Redis 5.0

    +

    Redis 6.0

    Instance deployment mode

    +

    Open-source compatibility

    Based on VMs

    +

    Redis 3.0.7

    Containerized based on physical servers

    +

    Redis 4.0.14 and 5.0.14, respectively

    +

    6.2.7

    Time required for creating an instance

    +

    Instance deployment mode

    3–15 minutes, or 10–30 minutes for cluster instances.

    +

    Based on VMs

    8 seconds

    +

    Containerized based on physical servers

    +

    Containerized based on physical servers

    QPS

    +

    Time required for creating an instance

    100,000 QPS per node

    +

    3–15 minutes, or 10–30 minutes for cluster instances.

    100,000 QPS per node

    +

    8 seconds

    +

    8 seconds

    Instance type

    +

    QPS

    Single-node, master/standby, and Proxy Cluster

    +

    100,000 QPS per node

    Single-node, master/standby and Redis Cluster

    +

    100,000 QPS per node

    +

    150,000 QPS per node

    Instance total memory

    +

    Visualized data management

    Ranges from 2 GB, 4 GB, 8 GB, to 1024 GB.

    +

    Not supported

    Regular specifications range from 2 GB, 4 GB, 8 GB, to 1024 GB. Small specifications, such as 128 MB, 256 MB, 512 MB, and 1 GB, are also available for single-node and master/standby instances.

    +

    Web CLI for connecting to Redis and managing data

    +

    Web CLI for connecting to Redis and managing data

    Scale-up or scale-down

    +

    Instance type

    Online scale-up and scale-down

    +

    Single-node, master/standby, and Proxy Cluster

    Online scale-up and scale-down

    +

    Single-node, master/standby and Redis Cluster

    +

    Single-node and master/standby

    Backup and restoration

    +

    Instance total memory

    Supported for master/standby and cluster instances

    +

    Ranges from 2 GB, 4 GB, 8 GB, to 1024 GB.

    Supported for master/standby and cluster instances

    +

    Regular specifications range from 2 GB, 4 GB, 8 GB, to 1024 GB. Small specifications, such as 128 MB, 256 MB, 512 MB, and 1 GB, are also available for single-node and master/standby instances.

    +

    2 GB, 4 GB, 8 GB, 16 GB, 32 GB, and 64 GB. Small specifications (128 MB, 256 MB, 512 MB, and 1 GB) are also supported.

    +

    Scale-up or scale-down

    +

    Online scale-up and scale-down

    +

    Online scale-up and scale-down

    +

    Online scale-up and scale-down

    +

    Backup and restoration

    +

    Supported for master/standby and cluster instances

    +

    Supported for master/standby and cluster instances

    +

    Supported for master/standby instances

    Through Big Key Analysis and Hot Key Analysis on the DCS console

    See Cache Analysis.

    +

    See Analyzing Big Keys and Hot Keys.

    By using the bigkeys and hotkeys options on redis-cli

    @@ -29,7 +29,7 @@ diff --git a/docs/dcs/umn/dcs-faq-0624001.html b/docs/dcs/umn/dcs-faq-0624001.html new file mode 100644 index 000000000..f79b96f70 --- /dev/null +++ b/docs/dcs/umn/dcs-faq-0624001.html @@ -0,0 +1,11 @@ + + +

    Can I View the Most Frequently Used Redis Commands?

    +

    No. Redis does not record commands and does not support viewing the most frequently used commands.

    +
    +
    +
    +
    Parent topic: Redis Commands
    +
    +
    + diff --git a/docs/dcs/umn/dcs-faq-0730001.html b/docs/dcs/umn/dcs-faq-0730001.html index 4e20d9b94..fbff2937e 100644 --- a/docs/dcs/umn/dcs-faq-0730001.html +++ b/docs/dcs/umn/dcs-faq-0730001.html @@ -1,8 +1,7 @@ -

    Does DCS Support Public Access?

    +

    Does DCS Support Access over Public Networks?

    No. DCS instances cannot be access at their EIPs over public networks. To ensure security, the ECS that serves as a client and the DCS instance that the client will access must belong to the same VPC.

    -

    In the application development and debugging phase, you can also use an SSH agent to access DCS instances in the local environment.

    diff --git a/docs/dcs/umn/dcs-faq-0730005.html b/docs/dcs/umn/dcs-faq-0730005.html index b81378a8f..fbbdda3de 100644 --- a/docs/dcs/umn/dcs-faq-0730005.html +++ b/docs/dcs/umn/dcs-faq-0730005.html @@ -3,6 +3,7 @@

    Why Do Requests Sometimes Time Out in Clients?

    Occasional timeout errors are normal because of network connectivity and client timeout configurations.

    You are advised to include reconnection operations into your service code to avoid service failure if a single request fails.

    +

    If a connection request times out, check if AOF persistence has been enabled. To avoid blocking, ensure that AOF has been enabled.

    If timeout errors occur frequently, contact O&M personnel.

    diff --git a/docs/dcs/umn/dcs-faq-0730006.html b/docs/dcs/umn/dcs-faq-0730006.html index 00a0d0556..ac0975f78 100644 --- a/docs/dcs/umn/dcs-faq-0730006.html +++ b/docs/dcs/umn/dcs-faq-0730006.html @@ -4,7 +4,7 @@

    The error message that will possibly be displayed when you use the Jedis connection pool is as follows:

    redis.clients.jedis.exceptions.JedisConnectionException: Could not get a resource from the pool

    If this error message is displayed, check whether your instance is running properly. If it is running properly, perform the following checks:

    -
    1. Network

      1. Check the IP address configurations.

        Check whether the IP address configured on the Jedis client is the same as the subnet address configured for your DCS instance.

        +
        1. Network

          1. Check the IP address configurations.

            Check whether the IP address configured on the Jedis client is the same as the subnet address configured for your DCS instance.

          2. Test the network.

            Use the ping command and telnet on the client to test the network.

            • If the network cannot be pinged:

              For intra-VPC access to a DCS Redis 3.0 instance, ensure that the client and your DCS instance belong to the same VPC and security group, or the security group of your DCS instance allows access through port 6379. For details, see Security Group Configurations.

            • If the IP address can be pinged but telnet failed, restart your instance. If the problem persists after the restart, contact technical support.
            diff --git a/docs/dcs/umn/dcs-faq-0730008.html b/docs/dcs/umn/dcs-faq-0730008.html index 6cd99dc4a..3dc4bd1ad 100644 --- a/docs/dcs/umn/dcs-faq-0730008.html +++ b/docs/dcs/umn/dcs-faq-0730008.html @@ -1,7 +1,7 @@

            How Do I Access a DCS Redis Instance Through Redis Desktop Manager?

            -

            You can access a DCS Redis instance through the Redis Desktop Manager within a VPC.

            +

            You can access a DCS Redis instance through the Redis Desktop Manager within a VPC.

            1. Enter the address, port number (6379), and authentication password of the DCS instance you want to access.
            2. Click Test Connection.

              The system displays a success message if the connection is successful.

              Figure 1 Accessing a DCS Redis instance through Redis Desktop Manager over the intranet

              When accessing a cluster DCS instance, the Redis command is run properly, but an error message may display on the left because DCS clusters are based on Codis, which differs from the native Redis in terms of the INFO command output.

              diff --git a/docs/dcs/umn/dcs-faq-0730010.html b/docs/dcs/umn/dcs-faq-0730010.html index a9528501e..3c9b1b61d 100644 --- a/docs/dcs/umn/dcs-faq-0730010.html +++ b/docs/dcs/umn/dcs-faq-0730010.html @@ -8,7 +8,7 @@
            3. Check if the maximum bandwidth has been reached.

              If the bandwidth reaches the maximum bandwidth for the corresponding instance specifications, Redis connections may time out.

            4. For a DCS Redis 3.0 instance, check the inbound access rules of the security group.

              Intra-VPC access: If the Redis client and the Redis instance are bound with different security groups, allow inbound access over port 6379 for the security group of the instance.

              For details, see Security Group Configurations.

              -
            5. For a DCS Redis 4.0 or 5.0 instance, check the whitelist configuration.

              If the instance has a whitelist, ensure that the client IP address is included in the whitelist. Otherwise, the connection will fail.

              +
            6. For a DCS Redis 4.0/5.0/6.0 instance, check the whitelist configuration.

              If the instance has a whitelist, ensure that the client IP address is included in the whitelist. Otherwise, the connection will fail.

              For details, see Managing IP Address Whitelist.

              If the client IP address has changed, add the new IP address to the whitelist.

            7. Check the configuration parameter notify-keyspace-events.

              Set notify-keyspace-events to Egx.

              diff --git a/docs/dcs/umn/dcs-faq-0730014.html b/docs/dcs/umn/dcs-faq-0730014.html index 54fab4706..e6a704ab0 100644 --- a/docs/dcs/umn/dcs-faq-0730014.html +++ b/docs/dcs/umn/dcs-faq-0730014.html @@ -1,8 +1,8 @@ -

              Why Aren't Security Groups Configured for DCS Redis 4.0 and 5.0 Instances?

              -

              Currently, DCS Redis 4.0 and Redis 5.0 instances use VPC endpoints and do not support security groups. You can configure whitelists instead. For details, see Managing IP Address Whitelist.

              -

              To allow access only from specific IP addresses to a DCS Redis 4.0 or 5.0 instance, add the IP addresses to the instance whitelist.

              +

              Why Aren't Security Groups Configured for DCS Redis 4.0/5.0/6.0 Instances?

              +

              Currently, DCS Redis 4.0/5.0/6.0 instances use VPC endpoints and do not support security groups. You can configure whitelists instead. For details, see Managing IP Address Whitelist.

              +

              To allow access only from specific IP addresses to a DCS Redis instance, add the IP addresses to the instance whitelist.

              If no whitelists are added to the instance whitelist or the whitelist function is disabled, all IP addresses that can communicate with the VPC can access the instance.

              diff --git a/docs/dcs/umn/dcs-faq-0730017.html b/docs/dcs/umn/dcs-faq-0730017.html index 72aeec703..22209e375 100644 --- a/docs/dcs/umn/dcs-faq-0730017.html +++ b/docs/dcs/umn/dcs-faq-0730017.html @@ -2,7 +2,7 @@

              Can I Obtain the Addresses of the Nodes in a Cluster DCS Redis Instance?

              Cluster DCS Redis 3.0 instances (Proxy Cluster type) are used in the same way that you use single-node or master/standby instances. You do not need to know the backend node addresses.

              -

              For a cluster DCS Redis 4.0 or 5.0 instance (Redis Cluster type), run the CLUSTER NODES command to obtain node addresses:

              +

              For a cluster DCS Redis 4.0/5.0/ instance (Redis Cluster type), run the CLUSTER NODES command to obtain node addresses:

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

              In the output similar to the following, obtain the IP addresses and port numbers of all the master nodes.

              diff --git a/docs/dcs/umn/dcs-faq-0730018.html b/docs/dcs/umn/dcs-faq-0730018.html index 725cad139..8611c66b9 100644 --- a/docs/dcs/umn/dcs-faq-0730018.html +++ b/docs/dcs/umn/dcs-faq-0730018.html @@ -1,7 +1,7 @@ -

              Why Is Available Memory of a DCS Redis 3.0 Instance Smaller Than Instance Cache Size?

              -

              DCS Redis 3.0 instances are deployed on VMs and some memory is reserved for system overheads.

              +

              Why Is Available Memory Smaller Than Instance Cache Size?

              +

              DCS Redis 3.0 instances are deployed on VMs and some memory is reserved for system overheads. This problem will not occur on other instance versions.

              diff --git a/docs/dcs/umn/dcs-faq-0730021.html b/docs/dcs/umn/dcs-faq-0730021.html index 0c48299a0..43c3b87fc 100644 --- a/docs/dcs/umn/dcs-faq-0730021.html +++ b/docs/dcs/umn/dcs-faq-0730021.html @@ -1,7 +1,7 @@

              Does DCS for Redis Support Sentinel?

              -

              Yes. Redis Sentinel is supported by DCS for Redis 4.0 and 5.0 and is enabled by default. Sentinel constantly checks if master and replica nodes are running properly. If the master is not running properly, Sentinel starts a failover process and promotes a replica to master.

              +

              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.

              diff --git a/docs/dcs/umn/dcs-faq-0730023.html b/docs/dcs/umn/dcs-faq-0730023.html index 4ae553a0f..d0c9a43b9 100644 --- a/docs/dcs/umn/dcs-faq-0730023.html +++ b/docs/dcs/umn/dcs-faq-0730023.html @@ -2,7 +2,12 @@

              What Should I Do If an Error Occurs in Redis Exporter?

              Start the Redis exporter using the CLI. Based on the output, check for errors and troubleshoot accordingly.

              -

              +
              [root@ecs-swk /]./redis_exporter -redis.addr 192.168.0.23:6379
+INFO[0000] Redis Metrics Exporter V0.15.0   build date:2018-01-19-04:08:01 sha1: a0d9ec4704b4d35cd08544d395038f417716a03a
+  Go:go1.9.2
+INFO[0000] Providing metrics at :9121/metrics
+INFO[0000] Connecting to redis hosts: []string{192.168.0.23:6379}
+INFO[0000] Using alias:[]string{""}
              diff --git a/docs/dcs/umn/dcs-faq-0730024.html b/docs/dcs/umn/dcs-faq-0730024.html deleted file mode 100644 index f785a0f17..000000000 --- a/docs/dcs/umn/dcs-faq-0730024.html +++ /dev/null @@ -1,11 +0,0 @@ - - -

              Why Is Memory Usage More Than 100%?

              -

              This is normal due to Redis functions (such as master/replica replication and lazyfree). When the memory becomes full, scale up the instance or remove unnecessary data.

              -
              -
              -
              -
              Parent topic: Redis Usage
              -
              -
              - diff --git a/docs/dcs/umn/dcs-faq-0730026.html b/docs/dcs/umn/dcs-faq-0730026.html index 5fcab5d50..3a21c25ab 100644 --- a/docs/dcs/umn/dcs-faq-0730026.html +++ b/docs/dcs/umn/dcs-faq-0730026.html @@ -1,9 +1,9 @@

              Can I Customize or Change the Port for Accessing a DCS Instance?

              -

              You cannot customize or change the port for accessing a DCS Redis 3.0 instance. You can customize and change the port for accessing a DCS Redis 4.0 or 5.0 instance.

              -
              • Redis 3.0

                Use port 6379 for intra-VPC access.

                -
              • Redis 4.0 and Redis 5.0

                You can specify a port (ranging from 1 to 65535) or use the default port (6379) for accessing a DCS Redis 4.0 or 5.0 instance. If no port is specified, the default port will be used.

                +

                You cannot customize or change the port for accessing a DCS Redis 3.0 instance. You can customize (during instance creation) but cannot change the port for accessing a DCS Redis 4.0 or later instance.

                +
                • Redis 3.0

                  Intra-VPC access: port 6379.

                  +
                • Redis 4.0 and later

                  You can specify a port (ranging from 1 to 65535) or use the default port (6379) for accessing an instance. If no port is specified, the default port will be used.

                If the instance and the client use different security groups, you must configure access rules for the security groups, allowing access through the specified port. For details, see Security Group Configurations.

                diff --git a/docs/dcs/umn/dcs-faq-0730027.html b/docs/dcs/umn/dcs-faq-0730027.html index 7cf11cb6b..46006fd53 100644 --- a/docs/dcs/umn/dcs-faq-0730027.html +++ b/docs/dcs/umn/dcs-faq-0730027.html @@ -1,7 +1,8 @@

                Can I Modify the Connection Addresses for Accessing a DCS Instance?

                -

                After a DCS instance is created, its intra-VPC connection addresses cannot be modified.

                +

                After a DCS instance is created, its intra-VPC connection addresses cannot be modified.

                +

                To use a different IP address, you must create a new instance and manually specify an IP address. After the instance is created, migrate the data from the old instance to the new instance.

                For details about accessing DCS instances through clients, see Accessing a DCS Redis Instance Through redis-cli.

                diff --git a/docs/dcs/umn/dcs-faq-0730033.html b/docs/dcs/umn/dcs-faq-0730033.html deleted file mode 100644 index 0c328c420..000000000 --- a/docs/dcs/umn/dcs-faq-0730033.html +++ /dev/null @@ -1,12 +0,0 @@ - - -

                Why Is Memory of a DCS Redis Instance Used Up by Just a Few Keys?

                -

                Possible cause: The output buffer may have occupied an excessive amount of memory.

                -

                Solution: After connecting to the instance using redis-cli, run the redis-cli --bigkeys command to scan for big keys. Then, run the info command to check the output buffer size.

                -
                -
                -
                -
                Parent topic: Redis Usage
                -
                -
                - diff --git a/docs/dcs/umn/dcs-faq-0730034.html b/docs/dcs/umn/dcs-faq-0730034.html index 742344aca..20feb3f1d 100644 --- a/docs/dcs/umn/dcs-faq-0730034.html +++ b/docs/dcs/umn/dcs-faq-0730034.html @@ -2,7 +2,9 @@

                Can I Recover Data from Deleted DCS Instances?

                If a DCS instance is automatically deleted or manually deleted through the Redis client, its data cannot be retrieved. If you have backed up the instance, you can restore its data from the backup. However, the restoration will overwrite the data written in during the period from the backup and the restoration.

                -

                By default, data is not evicted from DCS instances. You can modify the instance configuration parameters to adjust the eviction policy so that the instance can evict key values.

                +

                You can restore backup data to a master/standby cluster, or instance through Backups & Restorations on the DCS console. For details, see Restoring a DCS Instance.

                +

                +

                If a DCS instance is deleted, the instance data and its backup will also be deleted. Before deleting an instance, you can download the backup files of the instance for permanent local storage and can also migrate them to a new instance if you need to restore the data. For details about how to download the backup data, see Downloading a Backup File

                diff --git a/docs/dcs/umn/dcs-faq-0730036.html b/docs/dcs/umn/dcs-faq-0730036.html index 1ef91d514..ea476be00 100644 --- a/docs/dcs/umn/dcs-faq-0730036.html +++ b/docs/dcs/umn/dcs-faq-0730036.html @@ -5,9 +5,9 @@
                • 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 5.0

                  To clear data of a DCS Redis 4.0 or 5.0 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/5.0/6.0

                  To clear data of a DCS Redis 4.0/5.0/6.0 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 5.0 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 and run the FLUSHDB command on each master node.
                  • Redis Cluster data cannot be cleared by using Web CLI.
                  +
                  • 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 and run the FLUSHDB command on each master node.
                  • Redis Cluster data cannot be cleared by using Web CLI.
                diff --git a/docs/dcs/umn/dcs-faq-0730040.html b/docs/dcs/umn/dcs-faq-0730040.html index ce0052b7a..a01a3bbac 100644 --- a/docs/dcs/umn/dcs-faq-0730040.html +++ b/docs/dcs/umn/dcs-faq-0730040.html @@ -2,7 +2,11 @@

                Why Do I Fail to Execute Some Redis Commands?

                Possible causes include the following:

                -
                • The command is incorrect.
                • The command is disabled in DCS.

                  For security purposes, some Redis commands are disabled in DCS. For details about disabled and restricted Redis commands, see Command Compatibility.

                  +
                  • The command is incorrect.

                    As shown in the following figure, the error message is returned because the correct command for deleting a key should be del.

                    +

                    +
                  • A command available in a higher Redis version is run in a lower Redis version.

                    As shown in the following figure, the error message is returned because a stream command (available in Redis 5.0) is run in Redis 3.0.

                    +

                    +
                  • The command is disabled in DCS.

                    For security purposes, some Redis commands are disabled in DCS. For details about disabled and restricted Redis commands, see Command Compatibility.

                  • The LUA script fails to be executed.

                    For example, the error message "ERR unknown command 'EVAL'" indicates that your DCS Redis instance is of a lower version that does not support the LUA script. In this case, contact technical support for the instance to be upgraded.

                  • The CLIENT SETNAME and CLIENT GETNAME commands fail to be executed.

                    This is because the DCS Redis instance is of a lower version that does not support these commands. In this case, contact technical support for the instance to be upgraded.

                  diff --git a/docs/dcs/umn/dcs-faq-0730042.html b/docs/dcs/umn/dcs-faq-0730042.html deleted file mode 100644 index 16ea282cc..000000000 --- a/docs/dcs/umn/dcs-faq-0730042.html +++ /dev/null @@ -1,11 +0,0 @@ - - -

                  Is There a Time Limit on Executing Redis Commands? What Will Happen If a Command Times Out?

                  -

                  The time limit for executing a Redis command is 1 minute. This limit cannot be configured. After the execution of a command times out, your client will be automatically disconnected.

                  -
                  -
                  -
                  -
                  Parent topic: Redis Commands
                  -
                  -
                  - diff --git a/docs/dcs/umn/dcs-faq-0730043.html b/docs/dcs/umn/dcs-faq-0730043.html index a4a55c60c..21c6d1bb1 100644 --- a/docs/dcs/umn/dcs-faq-0730043.html +++ b/docs/dcs/umn/dcs-faq-0730043.html @@ -1,7 +1,7 @@ -

                  Can DCS Redis Instances Be Upgraded, for Example, from Redis 3.0 to Redis 4.0 or 5.0?

                  -

                  No. Different Redis versions use different underlying architectures. The Redis version used by a DCS instance cannot be changed once the instance is created. However, you will be informed of any defects or problems found in Redis.

                  +

                  Can DCS Redis Instances Be Upgraded, for Example, from Redis 4.0 to 5.0?

                  +

                  No. Different Redis versions use different underlying architectures. The Redis version used by a DCS instance cannot be changed once the instance is created. For example, you cannot change a DCS Redis 4.0 instance to Redis 5.0. However, you will be informed of any defects or problems found in Redis.

                  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 original instance to the new one. For details on how to migrate data, see Migrating Data with DCS.

                  diff --git a/docs/dcs/umn/dcs-faq-0730045.html b/docs/dcs/umn/dcs-faq-0730045.html index b5da9c032..fc80c3755 100644 --- a/docs/dcs/umn/dcs-faq-0730045.html +++ b/docs/dcs/umn/dcs-faq-0730045.html @@ -1,6 +1,6 @@ -

                  Are Instance Resources Affected During Specification Modification?

                  +

                  Are Instances Stopped or Restarted During Specification Modification?

                  No. Specification modifications can take place while the instance is running and do not affect any other resources.

                  diff --git a/docs/dcs/umn/dcs-faq-0730047.html b/docs/dcs/umn/dcs-faq-0730047.html index 94a2d1ee6..cb3907b28 100644 --- a/docs/dcs/umn/dcs-faq-0730047.html +++ b/docs/dcs/umn/dcs-faq-0730047.html @@ -2,15 +2,11 @@

                  Are Services Interrupted During Specification Modification?

                  You are advised to change the instance specifications during off-peak hours because specification modification has the following impacts:

                  -
                  • Impact of instance type changes:
                    • From single-node to master/standby for a DCS Redis 3.0 instance:

                      The instance cannot be connected for several seconds and remains read-only for about 1 minute.

                      -
                    • From master/standby to Proxy Cluster for a DCS Redis 3.0 instance:

                      The instance cannot be connected and remains read-only for 5 to 30 minutes.

                      +
                      • Impact of scaling:
                        • Single-node and master/standby
                          • A DCS Redis 4.0/5.0/6.0 instance will be disconnected for several seconds and remain read-only for about 1 minute.
                          • A DCS Redis 3.0 instance will be disconnected and remain read-only for 5 to 30 minutes.
                          • For scaling up, only the memory of the instance is expanded. The CPU processing capability is not improved.
                          • Data of single-node instances may be lost because they do not support data persistence. After scaling, check whether the data is complete and import data if required.
                          • Backup records of master/standby instances cannot be used after scaling down.
                          +
                        • Cluster
                          • If the shard quantity is not decreased, the instance can always be connected, but the CPU usage will increase, compromising performance by up to 20%, and the latency will increase during data migration.
                          • During scaling up, new Redis Server nodes are added, and data is automatically balanced to the new nodes.
                          • Nodes will be deleted if the shard quantity decreases. To prevent disconnection, ensure that the deleted nodes are not directly referenced in your application.
                          • Ensure that the used memory of each node is less than 70% of the maximum memory per node of the new flavor. Otherwise, you cannot perform the scale-in.
                          • If the memory becomes full during scaling due to a large amount of data being written, scaling will fail. Modify specifications during off-peak hours.
                          • Scaling involves data migration. The latency for accessing the key being migrated increases. For a Redis Cluster instance, ensure that the client can properly process the MOVED and ASK commands. Otherwise, requests will fail.
                          • Before scaling, perform cache analysis to ensure that no big keys (≥ 512 MB) exist in the instance. Otherwise, scaling may fail.
                          • Backup records created before scaling cannot be restored.
                        -
                      • Impact of capacity expansion and reduction:
                        • Single-node and master/standby

                          The DCS Redis 3.0, 4.0, or 5.0 instance cannot be connected for several seconds and remains read-only for about 1 minute.

                          -

                          For capacity expansion, only the memory of the instance is expanded. The CPU processing capability is not improved.

                          -

                          Data of single-node instances may not be retained because they do not support data persistence. After the scaling, check whether the data is complete and import data if required.

                          -
                        • Proxy Cluster

                          The instance can be connected, but the CPU will be occupied and the latency will increase during data migration. During capacity expansion, new Redis Server nodes are added, and data is automatically balanced to the new nodes.

                          -
                        • Redis Cluster

                          The instance can be connected, but the CPU usage and latency will increase during data migration. During capacity expansion, new Redis Server nodes are added, and data is automatically balanced to the new nodes.

                          -
                        • Backup records created before the capacity change cannot be restored.
                        +
                      +
                      • Notes on changing the number of replicas of a DCS Redis 4.0 or 5.0 instance:

                        Deleting replicas interrupts connections. If your application cannot reconnect to Redis or handle exceptions, you need to restart the application after scaling.

                  diff --git a/docs/dcs/umn/dcs-faq-0730054.html b/docs/dcs/umn/dcs-faq-0730054.html index 7c63d6435..df6aabc84 100644 --- a/docs/dcs/umn/dcs-faq-0730054.html +++ b/docs/dcs/umn/dcs-faq-0730054.html @@ -3,7 +3,7 @@

                  Can I Export Backup Data of DCS Redis Instances to RDB Files Using the Console?

                  • Redis 3.0

                    No. On the console, backup data of a DCS Redis 3.0 instance can be exported only to AOF files. To export data to RDB files, run the following command in redis-cli:

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

                    -
                  • Redis 4.0 and 5.0

                    Yes. Backup data of a DCS Redis 4.0 or 5.0 instance is exported from the console to RDB files. You cannot use redis-cli to export such data to RDB files.

                    +
                  • Redis 4.0/5.0/6.0

                    Yes. DCS Redis 4.0/5.0/6.0 instances support AOF and RDB persistence. You can back up data to RDB and AOF files on the console and download the files.

                  diff --git a/docs/dcs/umn/dcs-faq-0730057.html b/docs/dcs/umn/dcs-faq-0730057.html deleted file mode 100644 index 9229ab512..000000000 --- a/docs/dcs/umn/dcs-faq-0730057.html +++ /dev/null @@ -1,12 +0,0 @@ - - -

                  Does DCS Support Data Persistence?

                  -
                  DCS Redis instances:
                  • Single-node: Not supported
                  • Master/Standby and cluster: Supported
                  -
                  -
                  - - diff --git a/docs/dcs/umn/dcs-faq-0805001.html b/docs/dcs/umn/dcs-faq-0805001.html index 8cfa5ac76..bfec05eca 100644 --- a/docs/dcs/umn/dcs-faq-0805001.html +++ b/docs/dcs/umn/dcs-faq-0805001.html @@ -1,6 +1,6 @@ -

                  Analysis of Big Keys and Hot Keys

                  +

                  Big/Hot Key Analysis

                  diff --git a/docs/dcs/umn/dcs-faq-210706001.html b/docs/dcs/umn/dcs-faq-210706001.html new file mode 100644 index 000000000..9bf6eecd1 --- /dev/null +++ b/docs/dcs/umn/dcs-faq-210706001.html @@ -0,0 +1,14 @@ + + +

                  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%
                  +

                  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.
                  +
                  + + diff --git a/docs/dcs/umn/dcs-faq-210721003.html b/docs/dcs/umn/dcs-faq-210721003.html new file mode 100644 index 000000000..d6d21fc7c --- /dev/null +++ b/docs/dcs/umn/dcs-faq-210721003.html @@ -0,0 +1,33 @@ + + +

                  What Can I Do If Error "Cannot assign requested address" Is Returned When I Access Redis Using connect?

                  +

                  Symptom

                  Error message "Cannot assign requested address" is returned when you access Redis using connect.

                  +
                  +

                  Analysis

                  Applications that encounter this error typically use php-fpm and phpredis. In high-concurrency scenarios, a large number of TCP connections are in the TIME-WAIT state. As a result, the client cannot allocate new ports and the error message will be returned.

                  +
                  +

                  Solutions

                  • Solution 1: Use pconnect instead of connect.

                    Using pconnect reduces the number of TCP connections and prevents connections from being re-established for each request, and therefore reduces latency.

                    +

                    When using connect, the code for connecting to Redis is as follows:

                    +
                    $redis->connect('${Hostname}',${Port});
+$redis->auth('${Inst_Password}');
                    +

                    Replace connect with pconnect, and the code becomes:

                    +
                    $redis->pconnect('${Hostname}', ${Port}, 0, NULL, 0, 0, ['auth' => ['${Inst_Password}']]);
                    +
                    • Replace the connection parameters in the example with actual values. ${Hostname}, ${Port}, and ${Inst_Password} are the connection address, port number, and password of the Redis instance, respectively.
                    • phpredis must be v5.3.0 or later. You are advised to use this pconnect initialization mode to avoid NOAUTH errors during disconnection.
                    +
                    +
                  +
                  • Solution 2: Modify the tcp_max_tw_buckets parameter of the ECS where the client is located.

                    In this solution, the ports used by TIME-WAIT connections are reused. However, if retransmission occurs between the ECS and the backend service, the connection may fail. Therefore, the pconnect solution is recommended.

                    +
                    1. Connect to the ECS where the client is located
                    2. Run the following command to check the ip_local_port_range and tcp_max_tw_buckets parameters:

                      sysctl net.ipv4.tcp_max_tw_buckets net.ipv4.ip_local_port_range

                      +

                      Information similar to the following is displayed:

                      +
                      net.ipv4.tcp_max_tw_buckets = 262144
+net.ipv4.ip_local_port_range = 32768  61000
                      +
                    3. Run the following command to set the tcp_max_tw_buckets parameter to a value smaller than the value of ip_local_port_range:

                      sysctl -w net.ipv4.tcp_max_tw_buckets=10000

                      +
                    +
                  +

                  Generally, solution 1 is recommended. In special scenarios (for example, the service code involves too many components and is difficult to change), solution 2 can be used to meet high concurrency requirements.

                  +
                  +
                  +
                  +
                  +
                  Parent topic: Client and Network Connection
                  +
                  +
                  + diff --git a/docs/dcs/umn/dcs-faq-220317.html b/docs/dcs/umn/dcs-faq-220317.html new file mode 100644 index 000000000..46397b4d6 --- /dev/null +++ b/docs/dcs/umn/dcs-faq-220317.html @@ -0,0 +1,11 @@ + + +

                  Can I Migrate Data to Multiple Target Instances in One Migration Task?

                  +

                  No. A migration task allows data to be migrated to only one target instance. To migrate data to multiple target instances, create multiple migration tasks.

                  +
                  + + diff --git a/docs/dcs/umn/dcs-migration-090626001.html b/docs/dcs/umn/dcs-migration-090626001.html index 0ceb68403..d09192d53 100644 --- a/docs/dcs/umn/dcs-migration-090626001.html +++ b/docs/dcs/umn/dcs-migration-090626001.html @@ -1,28 +1,28 @@

                  Online Migration with Rump

                  -

                  Background

                  Rump is an open-source tool designed for migrating Redis data online. It supports migration between DBs of the same instance and between DBs of different instances.

                  +

                  Background

                  Rump is an open-source tool designed for migrating Redis data online. It supports migration between DBs of the same instance and between DBs of different instances.

                  -

                  Migration Principles

                  Rump uses the SCAN command to acquire keys and the DUMP/RESTORE command to get or set values.

                  -

                  Featuring time complexity O(1), SCAN is capable of quickly getting all keys. DUMP/RESTORE is used to read/write values independent from the key type.

                  -

                  Rump brings the following benefits:

                  -
                  • The SCAN command replaces the KEYS command to avoid blocking Redis.
                  • Any type of data can be migrated.
                  • SCAN and DUMP/RESTORE operations are pipelined, improving the network efficiency during data migration.
                  • No temporary file is involved, saving disk space.
                  • Buffered channels are used to optimize performance of the source server.
                  -
                  1. To cluster DCS instances, you cannot use Rump. Instead, use redis-port or redis-cli.
                  2. To prevent migration command resolution errors, do not include special characters (#@:) in the instance password.
                  3. Stop the service before migrating data. If data is kept being written in during the migration, some keys might be lost.
                  +

                  Migration Principles

                  Rump uses the SCAN command to acquire keys and the DUMP/RESTORE command to get or set values.

                  +

                  Featuring time complexity O(1), SCAN is capable of quickly getting all keys. DUMP/RESTORE is used to read/write values independent from the key type.

                  +

                  Rump brings the following benefits:

                  +
                  • The SCAN command replaces the KEYS command to avoid blocking Redis.
                  • Any type of data can be migrated.
                  • SCAN and DUMP/RESTORE operations are pipelined, improving the network efficiency during data migration.
                  • No temporary file is involved, saving disk space.
                  • Buffered channels are used to optimize performance of the source server.
                  +
                  1. To cluster DCS instances, you cannot use Rump. Instead, use redis-port or redis-cli.
                  2. To prevent migration command resolution errors, do not include special characters (#@:) in the instance password.
                  3. Stop the service before migrating data. If data is kept being written in during the migration, some keys might be lost.
                  -

                  Step 1: Installing Rump

                  1. Download Rump (release version).

                    On 64-bit Linux, run the following command:

                    -

                    wget https://github.com/stickermule/rump/releases/download/0.0.3/rump-0.0.3-linux-amd64;

                    -
                  2. After decompression, run the following commands to add the execution permission:

                    mv rump-0.0.3-linux-amd64 rump;

                    -

                    chmod +x rump;

                    +

                    Step 1: Installing Rump

                    1. Download Rump (release version).

                      On 64-bit Linux, run the following command:

                      +

                      wget https://github.com/stickermule/rump/releases/download/0.0.3/rump-0.0.3-linux-amd64;

                      +
                    2. After decompression, run the following commands to add the execution permission:

                      mv rump-0.0.3-linux-amd64 rump;

                      +

                      chmod +x rump;

                    -

                    Step 2: Migrating Data

                    rump -from {source_redis_address} -to {target_redis_address}

                    -

                    Parameter/Option description:

                    -
                    • {source_redis_address}

                      Source Redis instance address, in the format of redis://[user:password@]host:port/db. [user:password@] is optional. If the instance is accessed in password-protected mode, you must specify the password in the RFC 3986 format. user can be omitted, but the colon (:) cannot be omitted. For example, the address may be redis://:mypassword@192.168.0.45:6379/1.

                      -

                      db is the sequence number of the database. If it is not specified, the default value is 0.

                      -
                    • {target_redis_address}

                      Address of the target Redis instance, in the same format as the source.

                      -

                      In the following example, data in DB0 of the source Redis is migrated to the target Redis whose connection address is 192.168.0.153. ****** stands for the password.

                      -
                      [root@ecs ~]# ./rump -from redis://127.0.0.1:6379/0  -to redis://:******@192.168.0.153:6379/0
+
                      Step 2: Migrating Data
                      rump -from {source_redis_address}  -to {target_redis_address}
                      
+
                      Parameter/Option description:
                      
+
                      • {source_redis_address}
                        Source Redis instance address, in the format of redis://[user:password@]host:port/db. [user:password@] is optional. If the instance is accessed in password-protected mode, you must specify the password in the RFC 3986 format. user can be omitted, but the colon (:) cannot be omitted. For example, the address may be redis://:mypassword@192.168.0.45:6379/1.
                        
+
                        db is the sequence number of the database. If it is not specified, the default value is 0.
                        
+
                      • {target_redis_address}
                        Address of the target Redis instance, in the same format as the source.
                        
+
                        In the following example, data in DB0 of the source Redis is migrated to the target Redis whose connection address is 192.168.0.153. ****** stands for the password.
                        
+
                        [root@ecs ~]# ./rump -from redis://127.0.0.1:6379/0  -to redis://:******@192.168.0.153:6379/0
 .Sync done.
 [root@ecs ~]# 
                        
 
                      
diff --git a/docs/dcs/umn/dcs-pd-0326001.html b/docs/dcs/umn/dcs-pd-0326001.html
index ac91b8ce9..a7de31aed 100644
--- a/docs/dcs/umn/dcs-pd-0326001.html
+++ b/docs/dcs/umn/dcs-pd-0326001.html
@@ -15,7 +15,7 @@
                    • Command Compatibility
                      • -
                    • HA and DR Policies
                      +
                    • Disaster Recovery and Multi-Active Solution
                    • Comparing Redis Versions
                      • @@ -23,7 +23,7 @@
                    • Basic Concepts
                      • -
                    • Permissions Management
                      +
                    • Permissions
                    • Related Services
                      • diff --git a/docs/dcs/umn/dcs-pd-0326002.html b/docs/dcs/umn/dcs-pd-0326002.html index 9162fc467..7da2b6aff 100644 --- a/docs/dcs/umn/dcs-pd-0326002.html +++ b/docs/dcs/umn/dcs-pd-0326002.html @@ -4,7 +4,7 @@

                      Redis Application Scenarios

                      Many large-scale e-commerce websites and video streaming and gaming applications require fast access to large amounts of data that has simple data structures and does not need frequent join queries. In such scenarios, you can use Redis to achieve fast yet inexpensive access to data. Redis enables you to retrieve data from in-memory data stores instead of relying entirely on slower disk-based databases. In addition, you no longer need to perform additional management tasks. These features make Redis an important supplement to traditional disk-based databases and a basic service essential for internet applications receiving high-concurrency access.

                      Typical application scenarios of DCS for Redis are as follows:

                      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.

                        +

                        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.

                      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.

                        diff --git a/docs/dcs/umn/dcs-pd-0326003.html b/docs/dcs/umn/dcs-pd-0326003.html index e84dc68b9..be98125ea 100644 --- a/docs/dcs/umn/dcs-pd-0326003.html +++ b/docs/dcs/umn/dcs-pd-0326003.html @@ -16,14 +16,14 @@

    Requires 0.5 to 2 days to prepare servers.

    • Creates a Redis 3.0 instance in 5 to 15 minutes.
    • Creates a containerized Redis 4.0 or 5.0 instance within 8 seconds.
    +
    • Creates a Redis 3.0 instance in 5 to 15 minutes.
    • Creates a containerized Redis 4.0 or later instance within 8 seconds.

    Version

    -

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

    +

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

    Security

    diff --git a/docs/dcs/umn/dcs-pd-0916001.html b/docs/dcs/umn/dcs-pd-0916001.html index 1100fc9d5..64957eacb 100644 --- a/docs/dcs/umn/dcs-pd-0916001.html +++ b/docs/dcs/umn/dcs-pd-0916001.html @@ -7,87 +7,101 @@

    Single-Node Instances

    For each single-node DCS Redis instance, the available memory is less than the total memory because some memory is reserved for system overheads, as shown in Table 1. -
    Table 1 Specifications of single-node DCS Redis 3.0 instances

    Total Memory

    +
    - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + @@ -97,87 +111,101 @@

    Master/Standby Instances

    For each master/standby DCS Redis instance, the available memory is less than that of a single-node DCS Redis instance because some memory is reserved for data persistence, as shown in Table 2. The available memory of a master/standby instance can be adjusted to support background tasks such as data persistence and master/standby synchronization.

    -
    Table 1 Specifications of single-node DCS Redis 3.0 instances

    Total Memory

    (GB)

    Available Memory

    +

    Available Memory

    (GB)

    Max. Connections (Default/Limit)

    +

    Max. Connections (Default/Limit)

    (Count)

    Assured/Maximum Bandwidth

    +

    Assured/Maximum Bandwidth

    (Mbit/s)

    Reference Performance

    +

    Reference Performance

    (QPS)

    Specification Code (spec_code in the API)

    +

    2

    +

    2

    1.5

    +

    1.5

    5000/50,000

    +

    5000/50,000

    42/512

    +

    42/512

    50,000

    +

    50,000

    +

    dcs.single_node

    4

    +

    4

    3.2

    +

    3.2

    5000/50,000

    +

    5000/50,000

    64/1536

    +

    64/1536

    100,000

    +

    100,000

    +

    dcs.single_node

    8

    +

    8

    6.8

    +

    6.8

    5000/50,000

    +

    5000/50,000

    64/1536

    +

    64/1536

    100,000

    +

    100,000

    +

    dcs.single_node

    16

    +

    16

    13.6

    +

    13.6

    5000/50,000

    +

    5000/50,000

    85/3072

    +

    85/3072

    100,000

    +

    100,000

    +

    dcs.single_node

    32

    +

    32

    27.2

    +

    27.2

    5000/50,000

    +

    5000/50,000

    85/3072

    +

    85/3072

    100,000

    +

    100,000

    +

    dcs.single_node

    64

    +

    64

    58.2

    +

    58.2

    5000/60,000

    +

    5000/60,000

    128/5120

    +

    128/5120

    100,000

    +

    100,000

    +

    dcs.single_node
    Table 2 Specifications of master/standby DCS Redis 3.0 instances

    Total Memory

    +
    - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + @@ -186,65 +214,75 @@

    Proxy Cluster Instances

    In addition to larger memory, cluster instances feature more connections allowed, higher bandwidth allowed, and more QPS than single-node and master/standby instances.

    -
    Table 2 Specifications of master/standby DCS Redis 3.0 instances

    Total Memory

    (GB)

    Available Memory

    +

    Available Memory

    (GB)

    Max. Connections (Default/Limit)

    +

    Max. Connections (Default/Limit)

    (Count)

    Assured/Maximum Bandwidth

    +

    Assured/Maximum Bandwidth

    (Mbit/s)

    Reference Performance

    +

    Reference Performance

    (QPS)

    Specification Code (spec_code in the API)

    +

    2

    +

    2

    1.5

    +

    1.5

    5000/50,000

    +

    5000/50,000

    42/512

    +

    42/512

    50,000

    +

    50,000

    +

    dcs.master_standby

    4

    +

    4

    3.2

    +

    3.2

    5000/50,000

    +

    5000/50,000

    64/1536

    +

    64/1536

    100,000

    +

    100,000

    +

    dcs.master_standby

    8

    +

    8

    6.4

    +

    6.4

    5000/50,000

    +

    5000/50,000

    64/1536

    +

    64/1536

    100,000

    +

    100,000

    +

    dcs.master_standby

    16

    +

    16

    12.8

    +

    12.8

    5000/50,000

    +

    5000/50,000

    85/3072

    +

    85/3072

    100,000

    +

    100,000

    +

    dcs.master_standby

    32

    +

    32

    25.6

    +

    25.6

    5000/50,000

    +

    5000/50,000

    85/3072

    +

    85/3072

    100,000

    +

    100,000

    +

    dcs.master_standby

    64

    +

    64

    51.2

    +

    51.2

    5000/60,000

    +

    5000/60,000

    128/5120

    +

    128/5120

    100,000

    +

    100,000

    +

    dcs.master_standby
    Table 3 Specifications of Proxy Cluster DCS Redis 3.0 instances

    Specification

    +
    - - - - + - - - - - + - - - - - + - - - - - + - - - - - + diff --git a/docs/dcs/umn/dcs-pd-0916002.html b/docs/dcs/umn/dcs-pd-0916002.html index 12ca3415d..efbe7830e 100644 --- a/docs/dcs/umn/dcs-pd-0916002.html +++ b/docs/dcs/umn/dcs-pd-0916002.html @@ -3,546 +3,641 @@

    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.

    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.
    • Bandwidth: You can view the Flow Control Times metric to check whether the bandwidth has exceeded the limit.
    +
    • 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%?

      +
    • DCS Redis 4.0 and 5.0 instances are available in single-node, master/standby, and Redis Cluster types.
    • Only the x86 architecture is supported. The Arm architecture is not supported.

    Single-Node Instances

    -
    Table 3 Specifications of Proxy Cluster DCS Redis 3.0 instances

    Specification

    (GB)

    Available Memory

    +

    Available Memory

    (GB)

    Max. Connections (Default/Limit)

    +

    Max. Connections (Default/Limit)

    (Count)

    Assured/Maximum Bandwidth

    +

    Assured/Maximum Bandwidth

    (Mbit/s)

    Reference Performance

    +

    Reference Performance

    (QPS)

    Specification Code (spec_code in the API)

    +

    64

    +

    64

    64

    +

    64

    90,000/90,000

    +

    90,000/90,000

    600/5120

    +

    600/5120

    500,000

    +

    500,000

    +

    dcs.cluster

    128

    +

    128

    128

    +

    128

    180,000/180,000

    +

    180,000/180,000

    600/5120

    +

    600/5120

    500,000

    +

    500,000

    +

    dcs.cluster

    256

    +

    256

    256

    +

    256

    240,000/240,000

    +

    240,000/240,000

    600/5120

    +

    600/5120

    500,000

    +

    500,000

    +

    dcs.cluster

    512

    +

    512

    512

    +

    512

    480,000/480,000

    +

    480,000/480,000

    600/5120

    +

    600/5120

    500,000

    +

    500,000

    +

    dcs.cluster
    Table 1 Specifications of single-node DCS Redis 4.0 or 5.0 instances

    Total Memory

    +
    - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - +
    Table 1 Specifications of single-node DCS Redis 4.0 or 5.0 instances

    Total Memory

    (GB)

    Available Memory

    +

    Available Memory

    (GB)

    Max. Connections (Default/Limit)

    +

    Max. Connections (Default/Limit)

    (Count)

    Assured/Maximum Bandwidth

    +

    Assured/Maximum Bandwidth

    (Mbit/s)

    Reference Performance

    +

    Reference Performance

    (QPS)

    Specification Code (spec_code in the API)

    +

    0.125

    +

    0.125

    0.125

    +

    0.125

    10,000/10,000

    +

    10,000/10,000

    40/40

    +

    40/40

    80,000

    +

    80,000

    +

    redis.single.xu1.tiny.128

    0.25

    +

    0.25

    0.25

    +

    0.25

    10,000/10,000

    +

    10,000/10,000

    80/80

    +

    80/80

    80,000

    +

    80,000

    +

    redis.single.xu1.tiny.256

    0.5

    +

    0.5

    0.5

    +

    0.5

    10,000/10,000

    +

    10,000/10,000

    80/80

    +

    80/80

    80,000

    +

    80,000

    +

    redis.single.xu1.tiny.512

    1

    +

    1

    1

    +

    1

    10,000/50,000

    +

    10,000/50,000

    80/80

    +

    80/80

    80,000

    +

    80,000

    +

    redis.single.xu1.large.1

    2

    +

    2

    2

    +

    2

    10,000/50,000

    +

    10,000/50,000

    128/128

    +

    128/128

    80,000

    +

    80,000

    +

    redis.single.xu1.large.2

    4

    +

    4

    4

    +

    4

    10,000/50,000

    +

    10,000/50,000

    192/192

    +

    192/192

    80,000

    +

    80,000

    +

    redis.single.xu1.large.4

    8

    +

    8

    8

    +

    8

    10,000/50,000

    +

    10,000/50,000

    192/192

    +

    192/192

    100,000

    +

    100,000

    +

    redis.single.xu1.large.8

    16

    +

    16

    16

    +

    16

    10,000/50,000

    +

    10,000/50,000

    256/256

    +

    256/256

    100,000

    +

    100,000

    +

    redis.single.xu1.large.16

    24

    +

    24

    24

    +

    24

    10,000/50,000

    +

    10,000/50,000

    256/256

    +

    256/256

    100,000

    +

    100,000

    +

    redis.single.xu1.large.24

    32

    +

    32

    32

    +

    32

    10,000/50,000

    +

    10,000/50,000

    256/256

    +

    256/256

    100,000

    +

    100,000

    +

    redis.single.xu1.large.32

    48

    +

    48

    48

    +

    48

    10,000/50,000

    +

    10,000/50,000

    256/256

    +

    256/256

    100,000

    +

    100,000

    +

    redis.single.xu1.large.48

    64

    +

    64

    64

    +

    64

    10,000/50,000

    +

    10,000/50,000

    384/384

    +

    384/384

    100,000

    +

    100,000

    +

    redis.single.xu1.large.64
    -

    Master/Standby Instances

    -
    Table 2 Specifications of master/standby DCS Redis 4.0 or 5.0 instances

    Total Memory

    +

    Master/Standby Instances

    By default, a master/standby instance has two replicas (including the master). There is one master node.

    +

    Number of IP addresses occupied by a master/standby instance = Number of master nodes x Number of replicas. For example:

    +

    2 replicas: Number of occupied IP addresses = 1 x 2 = 2

    +

    3 replicas: Number of occupied IP addresses = 1 x 3 = 3

    +

    The following table lists the specification codes (spec_code) when there are two default replicas. Change the replica quantity in the specification codes based on the actual number of replicas. For example, if an 8 GB master/standby x86-based instance has two replicas, its specification code is redis.ha.xu1.large. r2.8. If it has three replicas, its specification code is redis.ha.xu1.large. r3.8.

    + +
    - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - + - - - - - +
    Table 2 Specifications of master/standby DCS Redis 4.0 or 5.0 instances

    Total Memory

    (GB)

    Available Memory

    +

    Available Memory

    (GB)

    Max. Connections (Default/Limit)

    +

    Max. Connections (Default/Limit)

    (Count)

    Assured/Maximum Bandwidth

    +

    Assured/Maximum Bandwidth

    (Mbit/s)

    Reference Performance

    +

    Reference Performance

    (QPS)

    Specification Code (spec_code in the API)

    +

    0.125

    +

    0.125

    0.125

    +

    0.125

    10,000/10,000

    +

    10,000/10,000

    40/40

    +

    40/40

    80,000

    +

    80,000

    +

    redis.ha.xu1.tiny.r2.128

    0.25

    +

    0.25

    0.25

    +

    0.25

    10,000/10,000

    +

    10,000/10,000

    80/80

    +

    80/80

    80,000

    +

    80,000

    +

    redis.ha.xu1.tiny.r2.256

    0.5

    +

    0.5

    0.5

    +

    0.5

    10,000/10,000

    +

    10,000/10,000

    80/80

    +

    80/80

    80,000

    +

    80,000

    +

    redis.ha.xu1.tiny.r2.512

    1

    +

    1

    1

    +

    1

    10,000/50,000

    +

    10,000/50,000

    80/80

    +

    80/80

    80,000

    +

    80,000

    +

    redis.ha.xu1.large.r2.1

    2

    +

    2

    2

    +

    2

    10,000/50,000

    +

    10,000/50,000

    128/128

    +

    128/128

    80,000

    +

    80,000

    +

    redis.ha.xu1.large.r2.2

    4

    +

    4

    4

    +

    4

    10,000/50,000

    +

    10,000/50,000

    192/192

    +

    192/192

    80,000

    +

    80,000

    +

    redis.ha.xu1.large.r2.4

    8

    +

    8

    8

    +

    8

    10,000/50,000

    +

    10,000/50,000

    192/192

    +

    192/192

    100,000

    +

    100,000

    +

    redis.ha.xu1.large.r2.8

    16

    +

    16

    16

    +

    16

    10,000/50,000

    +

    10,000/50,000

    256/256

    +

    256/256

    100,000

    +

    100,000

    +

    redis.ha.xu1.large.r2.16

    24

    +

    24

    24

    +

    24

    10,000/50,000

    +

    10,000/50,000

    256/256

    +

    256/256

    100,000

    +

    100,000

    +

    redis.ha.xu1.large.r2.24

    32

    +

    32

    32

    +

    32

    10,000/50,000

    +

    10,000/50,000

    256/256

    +

    256/256

    100,000

    +

    100,000

    +

    redis.ha.xu1.large.r2.32

    48

    +

    48

    48

    +

    48

    10,000/50,000

    +

    10,000/50,000

    256/256

    +

    256/256

    100,000

    +

    100,000

    +

    redis.ha.xu1.large.r2.48

    64

    +

    64

    64

    +

    64

    10,000/50,000

    +

    10,000/50,000

    384/384

    +

    384/384

    100,000

    +

    100,000

    +

    redis.ha.xu1.large.r2.64
    -

    Redis Cluster Instances

    -
    - diff --git a/docs/dcs/umn/dcs-pd-200813003.html b/docs/dcs/umn/dcs-pd-200813003.html index 0b2e784ff..ae7839350 100644 --- a/docs/dcs/umn/dcs-pd-200813003.html +++ b/docs/dcs/umn/dcs-pd-200813003.html @@ -1,6 +1,6 @@ -

    Command Restrictions for Cluster Instances

    +

    Command Restrictions

    Some Redis commands are supported by cluster DCS instances for multi-key operations in the same slot. For details, see Table 1.

    Table 3 Specifications of Redis Cluster DCS Redis 4.0 or 5.0 instances

    Specification

    +

    Redis Cluster Instances

    In addition to larger memory, Redis Cluster instances feature more connections allowed, higher bandwidth allowed, and more QPS than single-node and master/standby instances.

    +
    • The following table lists the x86 specification codes (spec_code) when there are two default replicas. Change the replica quantity in the specification codes based on the actual number of replicas. For example, if an 8 GB x86-based instance has two replicas, its specification code is redis.cluster.xu1.large.r2.8. If it has three replicas, its specification code is redis.cluster.xu1.large.r3.8.
    • IP addresses: Number of occupied IP addresses = Number of shards x Number of replicas. For example:

      4 GB | Redis Cluster | 3 replicas: Number of occupied IP addresses = 3 x 3 = 9

      +
    • Available memory per node = Instance available memory/Master node quantity. For example:

      For example, a 24 GB instance has 24 GB available memory and 3 master nodes. The available memory per node is 24/3 = 8 GB.

      +
    • Maximum connections limit per node = Maximum connections limit/Master node quantity For example:

      For example, a 4 GB instance has 3 master nodes and the maximum connections limit is 150,000. The maximum connections limit per node = 150,000/3 = 50,000.

      +
    + +
    - - - - - + - - - - - - + - - - - - - + - - - - - - + - - - - - - + - - - - - - + - - - - - - + - - - - - - + - - - - - - + - - - - - - + - - - - - - + - - - - - - + - - - - - - + - - - - - - + - - - - - - + - - - - - - + diff --git a/docs/dcs/umn/dcs-pd-0916004.html b/docs/dcs/umn/dcs-pd-0916004.html new file mode 100644 index 000000000..2d2dd6d20 --- /dev/null +++ b/docs/dcs/umn/dcs-pd-0916004.html @@ -0,0 +1,374 @@ + + +

    Redis 6.0 Instance Specifications

    +

    This section describes DCS Redis 6.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.
    • Bandwidth: You can view the Flow Control Times metric to check whether the bandwidth has exceeded the limit.
    +

    Currently, DCS for Redis 6.0 supports single-node and master/standby instances based on x86 CPUs.

    +

    Single-Node

    +
    Table 3 Specifications of Redis Cluster DCS Redis 4.0 or 5.0 instances

    Specification

    (GB)

    Available Memory

    +

    Available Memory

    (GB)

    Shards (Master Nodes)

    +

    Shards (Master Nodes)

    Max. Connections (Default/Limit)

    +

    Max. Connections (Default/Limit)

    (Count)

    Assured/Maximum Bandwidth

    +

    Assured/Maximum Bandwidth

    (Mbit/s)

    Reference Performance

    +

    Reference Performance

    (QPS)

    Specification Code (spec_code in the API)

    +

    4

    +

    4

    4

    +

    4

    3

    +

    3

    30,000

    +

    30,000

    /150,000

    2304/2304

    +

    2304/2304

    240,000

    +

    240,000

    +

    redis.cluster.xu1.large.r2.4

    8

    +

    8

    8

    +

    8

    3

    +

    3

    30,000

    +

    30,000

    /150,000

    2304/2304

    +

    2304/2304

    240,000

    +

    240,000

    +

    redis.cluster.xu1.large.r2.8

    16

    +

    16

    16

    +

    16

    3

    +

    3

    30,000

    +

    30,000

    /150,000

    2304/2304

    +

    2304/2304

    240,000

    +

    240,000

    +

    redis.cluster.xu1.large.r2.16

    24

    +

    24

    24

    +

    24

    3

    +

    3

    30,000

    +

    30,000

    /150,000

    2304/2304

    +

    2304/2304

    300,000

    +

    300,000

    redis.cluster.xu1.large.r2.24

    +

    32

    +

    32

    32

    +

    32

    3

    +

    3

    30,000

    +

    30,000

    /150,000

    2304/2304

    +

    2304/2304

    300,000

    +

    300,000

    +

    redis.cluster.xu1.large.r2.32

    48

    +

    48

    48

    +

    48

    6

    +

    6

    60,000

    +

    60,000

    /300,000

    4608/4608

    +

    4608/4608

    > 300,000

    +

    > 300,000

    +

    redis.cluster.xu1.large.r2.48

    64

    +

    64

    64

    +

    64

    8

    +

    8

    80,000

    +

    80,000

    /400,000

    6144/6144

    +

    6144/6144

    500,000

    +

    500,000

    +

    redis.cluster.xu1.large.r2.64

    96

    +

    96

    96

    +

    96

    12

    +

    12

    120,000

    +

    120,000

    /600,000

    9216/9216

    +

    9216/9216

    > 500,000

    +

    > 500,000

    +

    redis.cluster.xu1.large.r2.96

    128

    +

    128

    128

    +

    128

    16

    +

    16

    160,000

    +

    160,000

    /800,000

    12,288/12,288

    +

    12,288/12,288

    1,000,000

    +

    1,000,000

    +

    redis.cluster.xu1.large.r2.128

    192

    +

    192

    192

    +

    192

    24

    +

    24

    240,000

    +

    240,000

    /1,200,000

    18,432/18,432

    +

    18,432/18,432

    > 1,000,000

    +

    > 1,000,000

    +

    redis.cluster.xu1.large.r2.192

    256

    +

    256

    256

    +

    256

    32

    +

    32

    320,000

    +

    320,000

    /1,600,000

    24,576/24,576

    +

    24,576/24,576

    > 2,000,000

    +

    > 2,000,000

    +

    redis.cluster.xu1.large.r2.256

    384

    +

    384

    384

    +

    384

    48

    +

    48

    480,000

    +

    480,000

    /2,400,000

    36,864/36,864

    +

    36,864/36,864

    > 2,000,000

    +

    > 2,000,000

    +

    redis.cluster.xu1.large.r2.384

    512

    +

    512

    512

    +

    512

    64

    +

    64

    640,000

    +

    640,000

    /3,200,000

    49,152/49,152

    +

    49,152/49,152

    > 2,000,000

    +

    > 2,000,000

    +

    redis.cluster.xu1.large.r2.512

    768

    +

    768

    768

    +

    768

    96

    +

    96

    960,000

    +

    960,000

    /4,800,000

    73,728/73,728

    +

    73,728/73,728

    > 2,000,000

    +

    > 2,000,000

    +

    redis.cluster.xu1.large.r2.768

    1024

    +

    1024

    1024

    +

    1024

    128

    +

    128

    1,280,000

    +

    1,280,000

    /6,400,000

    98,304/98,304

    +

    98,304/98,304

    > 2,000,000

    +

    > 2,000,000

    +

    redis.cluster.xu1.large.r2.1024
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Specifications of single-node DCS Redis 6.0 instances

    Total Memory

    +

    (GB)

    +

    Available Memory

    +

    (GB)

    +

    Max. Connections (Default/Limit)

    +

    (Count)

    +

    Assured/Maximum Bandwidth

    +

    (Mbit/s)

    +

    Reference Performance

    +

    (QPS)

    +

    Specification Code (spec_code in the API)

    +

    0.125

    +

    0.125

    +

    10,000/10,000

    +

    40/40

    +

    140,000

    +

    redis.single.xu1.tiny.128

    +

    0.25

    +

    0.25

    +

    10,000/10,000

    +

    80/80

    +

    140,000

    +

    redis.single.xu1.tiny.256

    +

    0.5

    +

    0.5

    +

    10,000/10,000

    +

    80/80

    +

    140,000

    +

    redis.single.xu1.tiny.512

    +

    1

    +

    1

    +

    10,000/50,000

    +

    80/80

    +

    140,000

    +

    redis.single.xu1.large.1

    +

    2

    +

    2

    +

    10,000/50,000

    +

    128/128

    +

    140,000

    +

    redis.single.xu1.large.2

    +

    4

    +

    4

    +

    10,000/50,000

    +

    192/192

    +

    170,000

    +

    redis.single.xu1.large.4

    +

    8

    +

    8

    +

    10,000/50,000

    +

    192/192

    +

    170,000

    +

    redis.single.xu1.large.8

    +

    16

    +

    16

    +

    10,000/50,000

    +

    256/256

    +

    170,000

    +

    redis.single.xu1.large.16

    +

    24

    +

    24

    +

    10,000/50,000

    +

    256/256

    +

    170,000

    +

    redis.single.xu1.large.24

    +

    32

    +

    32

    +

    10,000/50,000

    +

    256/256

    +

    170,000

    +

    redis.single.xu1.large.32

    +

    48

    +

    48

    +

    10,000/50,000

    +

    256/256

    +

    170,000

    +

    redis.single.xu1.large.48

    +

    64

    +

    64

    +

    10,000/50,000

    +

    384/384

    +

    170,000

    +

    redis.single.xu1.large.64

    +
    +
    +
    +

    Master/Standby

    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 2 Specifications of master/standby DCS Redis 6.0 instances

    Total Memory

    +

    (GB)

    +

    Available Memory

    +

    (GB)

    +

    Max. Connections (Default/Limit)

    +

    (Count)

    +

    Assured/Maximum Bandwidth

    +

    (Mbit/s)

    +

    Reference Performance

    +

    (QPS)

    +

    Specification Code (spec_code in the API)

    +

    0.125

    +

    0.125

    +

    10,000/10,000

    +

    40/40

    +

    120,000

    +

    redis.ha.xu1.tiny.r2.128

    +

    0.25

    +

    0.25

    +

    10,000/10,000

    +

    80/80

    +

    120,000

    +

    redis.ha.xu1.tiny.r2.256

    +

    0.5

    +

    0.5

    +

    10,000/10,000

    +

    80/80

    +

    120,000

    +

    redis.ha.xu1.tiny.r2.512

    +

    1

    +

    1

    +

    10,000/50,000

    +

    80/80

    +

    120,000

    +

    redis.ha.xu1.large.r2.1

    +

    2

    +

    2

    +

    10,000/50,000

    +

    128/128

    +

    120,000

    +

    redis.ha.xu1.large.r2.2

    +

    4

    +

    4

    +

    10,000/50,000

    +

    192/192

    +

    150,000

    +

    redis.ha.xu1.large.r2.4

    +

    8

    +

    8

    +

    10,000/50,000

    +

    192/192

    +

    150,000

    +

    redis.ha.xu1.large.r2.8

    +

    16

    +

    16

    +

    10,000/50,000

    +

    256/256

    +

    150,000

    +

    redis.ha.xu1.large.r2.16

    +

    24

    +

    24

    +

    10,000/50,000

    +

    256/256

    +

    150,000

    +

    redis.ha.xu1.large.r2.24

    +

    32

    +

    32

    +

    10,000/50,000

    +

    256/256

    +

    150,000

    +

    redis.ha.xu1.large.r2.32

    +

    48

    +

    48

    +

    10,000/50,000

    +

    256/256

    +

    150,000

    +

    redis.ha.xu1.large.r2.48

    +

    64

    +

    64

    +

    10,000/50,000

    +

    384/384

    +

    150,000

    +

    redis.ha.xu1.large.r2.64

    +
    +
    +
    + +
    +
    +
    Parent topic: DCS Instance Specifications
    +
    +
    + diff --git a/docs/dcs/umn/dcs-pd-190826001.html b/docs/dcs/umn/dcs-pd-190826001.html index ac632c14d..021929c22 100644 --- a/docs/dcs/umn/dcs-pd-190826001.html +++ b/docs/dcs/umn/dcs-pd-190826001.html @@ -2,7 +2,7 @@

    Web CLI Commands

    Web CLI is a command line tool provided on the DCS console. This section describes Web CLI's compatibility with Redis commands, including supported and disabled commands. For details about the command syntax, visit the Redis official website.

    -

    Currently, only DCS for Redis 4.0 and 5.0 support Web CLI.

    +

    Currently, only DCS for Redis 4.0/5.0/6.0 support Web CLI.

    • Keys and values cannot contain spaces.
    • If the value is empty, nil is returned after the GET command is executed.

    Commands Supported by Web CLI

    The following lists the commands supported when you use Web CLI.

    diff --git a/docs/dcs/umn/dcs-pd-191224001.html b/docs/dcs/umn/dcs-pd-191224001.html new file mode 100644 index 000000000..024aba8ce --- /dev/null +++ b/docs/dcs/umn/dcs-pd-191224001.html @@ -0,0 +1,80 @@ + + +

    Comparing DCS Redis Instance Types

    +

    Table 1 describes the differences between different Redis instance types in terms of features and commands.

    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Differences between DCS instance types

    Item

    +

    Single-Node or Master/Standby

    +

    Proxy Cluster

    +

    Redis Cluster

    +

    Redis version compatibility

    +

    Redis 3.0/4.0/5.0/6.0. You can select a version when creating an instance.

    +

    Redis 3.0

    +

    Redis 4.0/5.0. You can select a version when creating an instance.

    +

    Support

    +
    • Keyspace notifications
    • Pipelining
    +
    • Pipelining, MSET command, and MGET command
    • SCAN command, KEYS command, and Redis Slow Log
    • Pub/Sub
    +
    • Keyspace notifications
    • BRPOP, BLPOP, and BRPOPLPUSH commands
    • Pub/Sub
    +

    Restrictions

    +

    Data persistence is not supported for single-node instances.

    +
    • LUA script is restricted: All keys must be in the same hash slot to avoid errors. Hash tags are recommended.
    • If a command contains multiple keys, the keys must be in the same hash slot to avoid errors. Hash tags are recommended.
    • Keyspace notifications are not supported.
    +
    • LUA script is restricted: All keys must be in the same hash slot. Hash tags are recommended.
    • The client SDK must support Redis Cluster and be able to process MOVED errors.
    • When you are using pipelining, MSET command, or MGET command, all keys must be in the same hash slot to avoid errors. Hash tags are recommended.
    • When using keyspace notifications, establish connections with every Redis server and process events on each connection.
    • When using a traversing or global command such as SCAN and KEYS, run the command on each Redis server.
    +

    Client

    +

    Any Redis client

    +

    Any Redis client (no need to support the Redis Cluster protocol)

    +

    Any client that supports the Redis Cluster protocol

    +

    Disabled commands

    +

    Command Compatibility lists commands disabled in single-node and master/standby instances.

    +

    Command Compatibility lists commands disabled in Proxy Cluster instances.

    +

    Command Compatibility lists commands disabled in Redis Cluster instances.

    +

    Replicas

    +

    A single-node instance has only one replica.

    +

    A master/standby instance has two replicas. Currently, the number of replicas cannot be customized for master/standby DCS Redis 3.0 and 6.0 instances. By default, a master/standby instance has a master node and a standby node. When creating a master/standby DCS Redis 4.0 or 5.0 instance, you can customize the number of replicas, with one of them being the master.

    +

    Each shard in the cluster has and can only have two replicas, with one of them being the master.

    +

    By default, each shard in the cluster has two replicas. The number of replicas can be customized, with one of them being the master. When creating an instance, you can set the replica quantity to one, indicating that the instance only has the master node. In this case, high data reliability cannot be ensured.

    +
    +
    +
    +
    +
    +
    Parent topic: DCS Instance Types
    +
    +
    + diff --git a/docs/dcs/umn/dcs-pd-200312001.html b/docs/dcs/umn/dcs-pd-200312001.html index b448d1f2e..cd7f3e2bf 100644 --- a/docs/dcs/umn/dcs-pd-200312001.html +++ b/docs/dcs/umn/dcs-pd-200312001.html @@ -12,6 +12,8 @@
  • Redis Cluster
    • +
  • Comparing DCS Redis Instance Types
    +
    • diff --git a/docs/dcs/umn/dcs-pd-200312003.html b/docs/dcs/umn/dcs-pd-200312003.html index dfd9e8856..970838845 100644 --- a/docs/dcs/umn/dcs-pd-200312003.html +++ b/docs/dcs/umn/dcs-pd-200312003.html @@ -10,9 +10,11 @@
  • Redis 5.0 Commands
    • +
  • Redis 6.0 Commands
    +
  • Web CLI Commands
    • -
  • Command Restrictions for Cluster Instances
    +
  • Command Restrictions
  • Other Command Usage Restrictions
    • diff --git a/docs/dcs/umn/dcs-pd-200312004.html b/docs/dcs/umn/dcs-pd-200312004.html index b143a8a02..fb207032d 100644 --- a/docs/dcs/umn/dcs-pd-200312004.html +++ b/docs/dcs/umn/dcs-pd-200312004.html @@ -2,13 +2,10 @@

    Basic Concepts

    DCS Instance

    An instance is the minimum resource unit provided by DCS.

    -

    DCS supports the Redis cache engine, and single-node, master/standby, and cluster instance types. For each instance type, multiple specifications are available.

    For details, see DCS Instance Specifications and DCS Instance Types.

    Project

    Projects are used to group and isolate OpenStack resources (computing resources, storage resources, and network resources). A project can be a department or a project team. Multiple projects can be created for one account.

    -

    Replica

    A replica is a node of a DCS instance. No replication indicates that the instance does not have a standby node. Master/Standby replication indicates that the instance has a standby node. For example, a master/standby DCS instance has a master/standby replication. Each node of a cluster DCS Redis instance has a master/standby replication.

    -

    Maintenance Time Window

    The maintenance time window is the period when the DCS service team upgrade and maintain the instance.

    DCS instance maintenance takes place only once a quarter and does not interrupt services. Even so, you are advised to select a time period when the service demand is low.

    When creating an instance, you must specify a maintenance time window, which can be modified on the Basic Information page after the instance is created.

    @@ -18,6 +15,9 @@

    When creating a master/standby or cluster DCS Redis instance, you can select a standby AZ for the standby 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.

    +
    +

    Replica

    A replica is a node in a DCS instance. A single-replica instance has no standby node. A two-replica instance has one master node and one standby node. By default, each master/standby instance has two replicas. If the number of replicas is set to three for a master/standby instance, the instance has one master node and two standby nodes. A single-node instance has only one node.

    diff --git a/docs/dcs/umn/dcs-pd-200713005.html b/docs/dcs/umn/dcs-pd-200713005.html index ce5d616cf..7e23a1e9a 100644 --- a/docs/dcs/umn/dcs-pd-200713005.html +++ b/docs/dcs/umn/dcs-pd-200713005.html @@ -4,7 +4,7 @@

    DCS for Redis 3.0 is developed based on Redis 3.0.7 and is compatible with open-source protocols and commands.

    This section describes DCS for Redis 3.0's compatibility with Redis commands, including supported commands, disabled commands, unsupported scripts and commands of later Redis versions, and restrictions on command usage. For more information about the command syntax, visit the Redis official website.

    DCS for Redis instances support most Redis commands, which are listed in Commands Supported by DCS for Redis 3.0. Any client compatible with the Redis protocol can access DCS.

    - +

    Commands Supported by DCS for Redis 3.0

    The following lists commands supported by DCS for Redis 3.0.

    • Commands available since later Redis versions are not supported by earlier-version instances. Run a command on redis-cli to check whether it is supported by DCS for Redis. If the message "(error) ERR unknown command" is returned, the command is not supported.
    • The following commands listed in the tables are not supported by Proxy Cluster instances:
      • List group: BLPOP, BRPOP, and BRPOPLRUSH
      • CLIENT commands in the Server group: CLIENT KILL, CLIENT GETNAME, CLIENT LIST, CLIENT SETNAME, CLIENT PAUSE, and CLIENT REPLY.
      • Server group: MONITOR
      • Key group: RANDOMKE (for old Proxy Cluster instances)
    diff --git a/docs/dcs/umn/dcs-pd-200813002.html b/docs/dcs/umn/dcs-pd-200813002.html index 1369909b4..0af22a499 100644 --- a/docs/dcs/umn/dcs-pd-200813002.html +++ b/docs/dcs/umn/dcs-pd-200813002.html @@ -4,7 +4,7 @@

    DCS for Redis 5.0 is developed based on Redis 5.0.9 and is compatible with open-source protocols and commands.

    This section describes DCS for Redis 5.0's compatibility with Redis commands, including supported and disabled commands. For more information about the command syntax, visit the Redis official website.

    DCS for Redis instances support most Redis commands. Any client compatible with the Redis protocol can access DCS.

    - +

    Commands Supported by DCS for Redis 5.0

    • Table 1 and Table 2 list commands supported by single-node, master/standby, and Redis Cluster DCS for Redis 5.0.
    • Commands available since later Redis versions are not supported by earlier-version instances. Run a command on redis-cli to check whether it is supported by DCS for Redis. If the message "(error) ERR unknown command" is returned, the command is not supported.
    • For DCS Redis 5.0 instances in the Redis Cluster mode, ensure that all commands in a pipeline are executed on the same shard.
    @@ -456,7 +456,7 @@

    WATCH

    SELECT

    +

    SELECT (not supported by Redis Cluster instances)

    SCRIPT KILL
    - diff --git a/docs/dcs/umn/dcs-pd-210209002.html b/docs/dcs/umn/dcs-pd-210209002.html new file mode 100644 index 000000000..2503a4a0a --- /dev/null +++ b/docs/dcs/umn/dcs-pd-210209002.html @@ -0,0 +1,657 @@ + + +

    Redis 6.0 Commands

    +

    DCS for Redis 6.0 is compatible with Redis 6.2.7 and with open-source protocols and commands.

    +

    This section describes DCS for Redis 6.0's command compatibility, including supported and disabled commands.

    +

    For more information about the command syntax, visit the Redis official website.

    +

    DCS Redis instances support most Redis commands. Any client compatible with the Redis protocol can access DCS.

    + +

    Commands Supported by DCS for Redis 6.0

    +
    Table 1 Redis commands restricted in cluster DCS instances.

    Category

    diff --git a/docs/dcs/umn/dcs-pd-200916001.html b/docs/dcs/umn/dcs-pd-200916001.html index 4f45ef6b7..5e9a2525c 100644 --- a/docs/dcs/umn/dcs-pd-200916001.html +++ b/docs/dcs/umn/dcs-pd-200916001.html @@ -4,7 +4,7 @@

    DCS for Redis 4.0 is developed based on Redis 4.0.14 and is compatible with open-source protocols and commands.

    This section describes DCS for Redis 4.0's compatibility with Redis commands, including supported and disabled commands. For more information about the command syntax, visit the Redis official website.

    DCS for Redis instances support most Redis commands, which are listed in Commands Supported by DCS for Redis 4.0. Any client compatible with the Redis protocol can access DCS.

    - +

    Commands Supported by DCS for Redis 4.0

    Table 1 and Table 2 list the Redis commands supported by single-node, master/standby, and Redis Cluster DCS Redis 4.0 instances.

    • Commands available since later Redis versions are not supported by earlier-version instances. Run a command on redis-cli to check whether it is supported by DCS for Redis. If the message "(error) ERR unknown command" is returned, the command is not supported.
    • For DCS Redis 4.0 instances in the Redis Cluster mode, ensure that all commands in a pipeline are executed on the same shard.
    @@ -446,7 +446,7 @@

    WATCH

    SELECT

    +

    SELECT (not supported by Redis Cluster instances)

    SCRIPT KILL

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Commands supported by DCS for Redis 6.0 (1)

    Generic (Key)

    +

    String

    +

    Hash

    +

    List

    +

    Set

    +

    Sorted Set

    +

    Server

    +

    DEL

    +

    APPEND

    +

    HDEL

    +

    BLPOP

    +

    SADD

    +

    ZADD

    +

    FLUSHALL

    +

    DUMP

    +

    BITCOUNT

    +

    HEXISTS

    +

    BRPOP

    +

    SCARD

    +

    ZCARD

    +

    FLUSHDB

    +

    EXISTS

    +

    BITOP

    +

    HGET

    +

    BRPOPLRUSH

    +

    SDIFF

    +

    ZCOUNT

    +

    DBSIZE

    +

    EXPIRE

    +

    BITPOS

    +

    HGETALL

    +

    LINDEX

    +

    SDIFFSTORE

    +

    ZINCRBY

    +

    TIME

    +

    MOVE

    +

    DECR

    +

    HINCRBY

    +

    LINSERT

    +

    SINTER

    +

    ZRANGE

    +

    INFO

    +

    PERSIST

    +

    DECRBY

    +

    HINCRBYFLOAT

    +

    LLEN

    +

    SINTERSTORE

    +

    ZRANGEBYSCORE

    +

    CLIENT KILL

    +

    PTTL

    +

    GET

    +

    HKEYS

    +

    LPOP

    +

    SISMEMBER

    +

    ZRANK

    +

    CLIENT LIST

    +

    RANDOMKEY

    +

    GETRANGE

    +

    HMGET

    +

    LPUSHX

    +

    SMEMBERS

    +

    ZREMRANGEBYRANK

    +

    CLIENT GETNAME

    +

    RENAME

    +

    GETSET

    +

    HMSET

    +

    LRANGE

    +

    SMOVE

    +

    ZREMRANGEBYCORE

    +

    CLIENT SETNAME

    +

    RENAMENX

    +

    INCR

    +

    HSET

    +

    LREM

    +

    SPOP

    +

    ZREVRANGE

    +

    CONFIG GET

    +

    RESTORE

    +

    INCRBY

    +

    HSETNX

    +

    LSET

    +

    SRANDMEMBER

    +

    ZREVRANGEBYSCORE

    +

    MONITOR

    +

    SORT

    +

    INCRBYFLOAT

    +

    HVALS

    +

    LTRIM

    +

    SREM

    +

    ZREVRANK

    +

    SLOWLOG

    +

    TTL

    +

    MGET

    +

    HSCAN

    +

    RPOP

    +

    SUNION

    +

    ZSCORE

    +

    ROLE

    +

    TYPE

    +

    MSET

    +

    HSTRLEN

    +

    RPOPLPU

    +

    SUNIONSTORE

    +

    ZUNIONSTORE

    +

    SWAPDB

    +

    SCAN

    +

    MSETNX

    +

    HLEN

    +

    RPOPLPUSH

    +

    SSCAN

    +

    ZINTERSTORE

    +

    MEMORY

    +

    OBJECT

    +

    PSETEX

    +

    -

    +

    RPUSH

    +

    -

    +

    ZSCAN

    +

    CONFIG

    +

    PEXPIREAT

    +

    SET

    +

    -

    +

    RPUSHX

    +

    -

    +

    ZRANGEBYLEX

    +

    -

    +

    PEXPIRE

    +

    SETBIT

    +

    -

    +

    LPUSH

    +

    -

    +

    ZLEXCOUNT

    +

    -

    +

    KEYS

    +

    SETEX

    +

    -

    +

    -

    +

    -

    +

    ZPOPMIN

    +

    -

    +

    -

    +

    SETNX

    +

    -

    +

    -

    +

    -

    +

    ZPOPMAX

    +

    -

    +

    -

    +

    SETRANGE

    +

    -

    +

    -

    +

    -

    +

    ZREMRANGEBYSCORE

    +

    -

    +

    -

    +

    STRLEN

    +

    -

    +

    -

    +

    -

    +

    ZREM

    +

    -

    +

    -

    +

    BITFIELD

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +
    +
    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 2 Commands supported by DCS for Redis 6.0 (2)

    HyperLoglog

    +

    Pub/Sub

    +

    Transactions

    +

    Connection

    +

    Scripting

    +

    Geo

    +

    Stream

    +

    PFADD

    +

    PSUBSCRIBE

    +

    DISCARD

    +

    AUTH

    +

    EVAL

    +

    GEOADD

    +

    XACK

    +

    PFCOUNT

    +

    PUBLISH

    +

    EXEC

    +

    ECHO

    +

    EVALSHA

    +

    GEOHASH

    +

    XADD

    +

    PFMERGE

    +

    PUBSUB

    +

    MULTI

    +

    PING

    +

    SCRIPT EXISTS

    +

    GEOPOS

    +

    XCLAIM

    +

    -

    +

    PUNSUBSCRIBE

    +

    UNWATCH

    +

    QUIT

    +

    SCRIPT FLUSH

    +

    GEODIST

    +

    XDEL

    +

    -

    +

    SUBSCRIBE

    +

    WATCH

    +

    SELECT

    +

    SCRIPT KILL

    +

    GEORADIUS

    +

    XGROUP

    +

    -

    +

    UNSUBSCRIBE

    +

    -

    +

    -

    +

    SCRIPT LOAD

    +

    GEORADIUSBYMEMBER

    +

    XINFO

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    XLEN

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    XPENDING

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    XRANGE

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    XREAD

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    XREADGROUP

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    XREVRANGE

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    -

    +

    XTRIM

    +
    +
    +
    +

    Commands Disabled by DCS for Redis 6.0

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

    Generic (Key)

    +

    Server

    +

    MIGRATE

    +

    SLAVEOF

    +

    -

    +

    SHUTDOWN

    +

    -

    +

    LASTSAVE

    +

    -

    +

    DEBUG commands

    +

    -

    +

    COMMAND

    +

    -

    +

    SAVE

    +

    -

    +

    BGSAVE

    +

    -

    +

    BGREWRITEAOF

    +

    -

    +

    SYNC

    +

    -

    +

    PSYNC

    +
    +
    +
    + +
    +
    +
    Parent topic: Command Compatibility
    +
    +
    + diff --git a/docs/dcs/umn/dcs-pd-210626001.html b/docs/dcs/umn/dcs-pd-210626001.html index 321e1b08f..44cb98d18 100644 --- a/docs/dcs/umn/dcs-pd-210626001.html +++ b/docs/dcs/umn/dcs-pd-210626001.html @@ -1,14 +1,14 @@ -

    Permissions Management

    +

    Permissions

    If you need to assign different permissions to employees in your enterprise to access your DCS resources, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you secure access to your resources.

    With IAM, you can use your account to create IAM users, and assign permissions to the users to control their access to specific resources. For example, some software developers in your enterprise need to use DCS resources but should not be allowed to delete DCS instances or perform any other high-risk operations. In this scenario, you can create IAM users for the software developers and grant them only the permissions required for using DCS resources.

    If your account does not require individual IAM users for permissions management, skip this section.

    DCS Permissions

    By default, new IAM users do not have permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.

    DCS is a project-level service deployed and accessed in specific physical regions. To assign DCS permissions to a user group, specify the scope as region-specific projects and select regions for the permissions to take effect. If All projects is selected, the permissions will take effect for the user group in all region-specific projects. When accessing DCS, the users need to switch to a region where they have been authorized to use this service.

    -
    You can grant users permissions by using roles and policies.
    • Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you must also assign other roles on which the permissions depend to take effect. However, roles are not an ideal choice for fine-grained authorization and secure access control.
    • Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant DCS users only the permissions for operating DCS instances. Fine-grained policies are based on APIs. The minimum granularity of a policy is API actions. For the API actions supported by DCS, see "Permissions Policies and Supported Actions".
    +
    You can grant users permissions by using roles and policies.
    • Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you must also assign other roles on which the permissions depend to take effect. However, roles are not an ideal choice for fine-grained authorization and secure access control.
    • Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant DCS users only the permissions for operating DCS instances. Fine-grained policies are based on APIs. The minimum granularity of a policy is API actions. For the API actions supported by DCS, see section "Permissions Policies and Supported Actions" in the Distributed Cache Service API Reference.
    -

    Table 1 lists all the system-defined roles and policies supported by DCS.

    +

    Table 1 lists all the system permissions supported by DCS.

    @@ -52,7 +52,7 @@

    The DCS UserAccess policy is different from the DCS FullAccess policy. If you configure both of them, you cannot create, modify, delete, or scale DCS instances because deny statements will take precedence over allowed statements.

    -

    Table 2 lists the common operations supported by each system policy of DCS. Please choose proper system policies according to this table.

    +

    Table 2 lists the common operations supported by system-defined policies for DCS.

    Table 1 System-defined roles and policies supported by DCS

    Role/Policy Name
    @@ -172,15 +172,6 @@ - - - - - - - - - -
    Table 2 Common operations supported by each system policy

    Operation

    ×

    Upgrading instance version

    -

    √

    -

    √

    -

    ×

    -

    Restoring instance data

    √

    @@ -271,15 +262,6 @@

    √

    Querying instance upgrade information

    -

    √

    -

    √

    -

    √

    -

    Querying all instances

    √

    diff --git a/docs/dcs/umn/dcs-ug-023129.html b/docs/dcs/umn/dcs-ug-023129.html new file mode 100644 index 000000000..0c6c25b38 --- /dev/null +++ b/docs/dcs/umn/dcs-ug-023129.html @@ -0,0 +1,15 @@ + + +

    Configuring SSL

    +

    DCS Redis 6.0 instances support SSL encryption to ensure data transmission security. This function is not available for other instance versions. RESP (REdis Serialization Protocol), the communication protocol of Reids, only supports plaintext transmission in versions earlier than Redis 6.0.

    +

    Procedure

    1. Log in to the DCS console.
    2. Click in the upper left corner of the management console and select the region where your instance is located.
    3. In the navigation pane, choose Cache Manager.
    4. On the Cache Manager page, click a DCS instance.
    5. In the navigation pane, choose SSL.
    6. Click next to SSL Certificate to enable or disable SSL.

      • Enabling or disabling SSL will restart the instance and disconnect it for a few seconds. Wait until off-peak hours and ensure that your application can re-connect.
      • The restart cannot be undone. For single-node DCS instances and other instances where AOF persistence is disabled (appendonly is set to no), data will be cleared and ongoing backup tasks will be stopped. Exercise caution when performing this operation.
      • Enabling SSL will deteriorate read/write performance.
      +
      +

    7. Click Download Certificate to download the SSL certificate.
    8. Decompress the SSL certificate and upload the decompressed ca.crt file to the server where the Redis client is located.
    9. Add the path of the ca.crt file to the command for connecting to the instance. If you use redis-cli to connect to an instance, refer to Accessing a DCS Redis Instance Through redis-cli.
    +
    +
    +
    +
    +
    Parent topic: Managing DCS Instances
    +
    +
    + diff --git a/docs/dcs/umn/dcs-ug-0312003.html b/docs/dcs/umn/dcs-ug-0312003.html index 4720ff487..9df32e216 100644 --- a/docs/dcs/umn/dcs-ug-0312003.html +++ b/docs/dcs/umn/dcs-ug-0312003.html @@ -6,7 +6,7 @@
    • Identifying Requirements
      • -
    • Preparing the Environment
      +
    • Preparing Required Resources
    • Creating a DCS Redis Instance
      • diff --git a/docs/dcs/umn/dcs-ug-0312004.html b/docs/dcs/umn/dcs-ug-0312004.html index be9d01377..f5bf0450b 100644 --- a/docs/dcs/umn/dcs-ug-0312004.html +++ b/docs/dcs/umn/dcs-ug-0312004.html @@ -1,14 +1,79 @@ -

      Preparing the Environment

      +

      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 a VPC, you can use it for all DCS instances you subsequently create.

      -

      Creating a VPC

      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 7. Otherwise, go to 8.

        +

        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.

          +

          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.
          -

        6. In the navigation pane on the left, choose Virtual Private Cloud > Subnets.
        7. Click Create Subnet. Create a subnet as prompted, retaining the default values unless otherwise required.

          For details about how to create a subnet, see Creating a Subnet for the VPC.

          -

        8. In the navigation pane on the left, choose Access Control > Security Groups and then click Create Security Group in the upper right corner of the displayed page. Create a security group as prompted, retaining the default values unless otherwise required.

          For details about how to create a security group, see Creating a Security Group.

          +

        9. In the navigation pane on the left, choose Virtual Private Cloud > Subnets.
        10. Click Create Subnet. Create a subnet as prompted, retaining the default values unless otherwise required.

          For details about how to create a subnet, see Creating a Subnet for the VPC.

          +

        +
        +

        Creating a Security Group

        Only DCS Redis 3.0 instances require security groups.

        +
        +
        1. Log in to the VPC console.
        2. In the navigation pane on the left, choose Access Control > Security Groups and then click Create Security Group in the upper right corner of the displayed page. Create a security group as prompted, retaining the default values unless otherwise required.

          For details about how to create a security group, see Creating a Security Group.

          +
          • Set Template to Custom.
          • After a security group is created, retain the default inbound rule that allows communication among ECSs within the security group and the default outbound rule that allows all outbound traffic.
          • To use DCS, you must add the security group rules described in the following table. You can also add other rules based on site requirements. +
            + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
            Table 1 Security group rules

            Direction

            +

            Protocol

            +

            Port

            +

            Source

            +

            Description

            +

            Inbound

            +

            TCP

            +

            36379

            +

            0.0.0.0/0

            +

            Access a DCS Redis instance (with SSL encryption enabled) through a public network.

            +

            Inbound

            +

            TCP

            +

            6379

            +

            0.0.0.0/0

            +

            Access a DCS Redis instance (with SSL encryption disabled) through a public network.

            +

            Inbound

            +

            TCP

            +

            6379

            +

            0.0.0.0/0

            +

            Access a DCS Redis instance in a private network. (SSL encryption is not supported.)

            +

            Inbound

            +

            TCP

            +

            11211

            +

            0.0.0.0/0

            +

            Access a DCS Memcached instance through a public network. (SSL encryption is not supported.)

            +
            +
            +

      diff --git a/docs/dcs/umn/dcs-ug-0312008.html b/docs/dcs/umn/dcs-ug-0312008.html index 399fc8829..9a6648acc 100644 --- a/docs/dcs/umn/dcs-ug-0312008.html +++ b/docs/dcs/umn/dcs-ug-0312008.html @@ -1,14 +1,14 @@ -

      Accessing a DCS Redis 4.0 or 5.0 Instance on the Console

      -

      Access a DCS Redis instance through Web CLI. This function is supported only by DCS Redis 4.0 and 5.0 instances, and not by DCS Redis 3.0 instances.

      +

      Accessing a DCS Redis 4.0/5.0/6.0 Instance on the Console

      +

      Access a DCS Redis instance through Web CLI. This function is supported only by DCS Redis 4.0 and later instances, and not by DCS Redis 3.0 instances.

      • Do not enter sensitive information in Web CLI to avoid disclosure.
      • Keys and values cannot contain spaces.
      • If the value is empty, nil is returned after the GET command is executed.
      -

      Prerequisites

      The DCS Redis 4.0 or 5.0 instance you want to access through Web CLI is in the Running state.

      +

      Prerequisites

      The instance is in the Running state.

      -

      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. In the row containing the desired instance, choose More > Connect to Redis to go to the Web CLI login page.
      5. Enter the password of the DCS instance. On Web CLI, select the current Redis database, enter a Redis command in the command box, and press Enter.
      -

      -

      +

      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. In the row containing the desired instance, choose More > Connect to Redis to go to the Web CLI login page.
      5. Enter the password of the DCS instance. On Web CLI, select the current Redis database, enter a Redis command in the command box, and press Enter.

        If no operation is performed for more than 5 minutes, the connection times out. You must enter the access password to connect to the instance again.

        +
        +

      diff --git a/docs/dcs/umn/dcs-ug-0312009.html b/docs/dcs/umn/dcs-ug-0312009.html index d967cff36..778495aec 100644 --- a/docs/dcs/umn/dcs-ug-0312009.html +++ b/docs/dcs/umn/dcs-ug-0312009.html @@ -4,7 +4,7 @@

      Access a DCS Redis instance through phpredis on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis official website.

      The operations described in this section apply only to single-node, master/standby, and Proxy Cluster instances. To use phpredis to connect to a Redis Cluster instance, see the phpredis description.

      -

      Prerequisites

      • A DCS Redis instance has been created and is in the Running state.
      • 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 GCC compilation environment has been installed on the ECS.
      +

      Prerequisites

      • A DCS Redis instance has been created and is in the Running state.
      • 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 GCC compilation environment has been installed on the ECS.

      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.

        The following uses CentOS as an example to describe how to access an instance through phpredis.

        @@ -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 the IP address/domain name and port 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 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.

      3. 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 dec16acb9..ccec93158 100644 --- a/docs/dcs/umn/dcs-ug-0312010.html +++ b/docs/dcs/umn/dcs-ug-0312010.html @@ -4,7 +4,7 @@

      Access a DCS Redis instance through hiredis on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis official website.

      The operations described in this section apply only to single-node, master/standby, and Proxy Cluster instances. To use C++ to connect to a Redis Cluster instance, see the C++ Redis client description.

      -

      Prerequisites

      • A DCS Redis instance has been created and is in the Running state.
      • 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 GCC compilation environment has been installed on the ECS.
      +

      Prerequisites

      • A DCS Redis instance has been created and is in the Running state.
      • 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 GCC compilation environment has been installed on the ECS.

      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.

        The following uses CentOS as an example to describe how to access an instance in C++.

        @@ -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.

      3. Run the following command to access the chosen DCS Redis instance:

        ./connRedis {redis_ip_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 the IP address/domain name and port 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 27780d266..f4cb6c441 100644
--- a/docs/dcs/umn/dcs-ug-0312011.html
+++ b/docs/dcs/umn/dcs-ug-0312011.html
@@ -4,7 +4,7 @@
 
        Access a DCS Redis instance through redis-py on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis official website.
        
 
         
        Use redis-py to connect to single-node, master/standby, and Proxy Cluster instances and redis-py-cluster to connect to Redis Cluster instances.
        
 
        
-
        Prerequisites
        • A DCS Redis instance has been created and is in the Running state.
        • 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 Python compilation environment has been installed on the ECS.
        
+
        Prerequisites
        • A DCS Redis instance has been created and is in the Running state.
        • 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 Python compilation environment has been installed on the ECS.
        
 
        
 
        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.
          The following uses CentOS as an example to describe how to access an instance using a Python client.
          
@@ -12,7 +12,7 @@
 
          yum install python
           
          The Python version must be 3.6 or later. If the default Python version is earlier than 3.6, perform the following operations to change it:
          
 
          1. Run the rm -rf python command to delete the Python symbolic link.
          2. Run the ln -s pythonX.X.X python command to create another Python link. In the command, X.X.X indicates the Python version number.
          
 
          
-
          • If the instance is a single-node, master/standby, or Proxy Cluster instance:
            1. Install Python and redis-py.
              1. If the system does not provide Python, run the following yum command to install it.
              2. Run the following command to download and decompress the redis-py package:
                wget https://github.com/andymccurdy/redis-py/archive/master.zip
                
+
                • If the instance is a single-node, master/standby, or Proxy Cluster instance:
                  1. Install Python and redis-py.
                    1. If the system does not provide Python, run the yum command to install it.
                    2. Run the following command to download and decompress the redis-py package:
                      wget https://github.com/andymccurdy/redis-py/archive/master.zip
                      
 
                      unzip master.zip
                      
 
                    3. Go to the directory where the decompressed redis-py package is saved, and install redis-py.
                      python setup.py install
                      
 
                      After the installation, run the python command. redis-py have been successfully installed if the following command output is displayed:
                      
@@ -20,7 +20,7 @@
 
                    
 
                  2. 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 the IP address/domain name and port 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,11 +30,11 @@
 
                  3. 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:
                    >>> 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"}]
+>>> 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"}]
 
->>> rc = RedisCluster(startup_nodes=startup_nodes, decode_responses=True)
+>>> rc = RedisCluster(startup_nodes=startup_nodes, decode_responses=True, password='******')
 
 >>> rc.set("foo", "bar")
 True
diff --git a/docs/dcs/umn/dcs-ug-0312012.html b/docs/dcs/umn/dcs-ug-0312012.html
index 51e4ac388..47b577b32 100644
--- a/docs/dcs/umn/dcs-ug-0312012.html
+++ b/docs/dcs/umn/dcs-ug-0312012.html
@@ -4,7 +4,7 @@
 
                      Access a DCS Redis instance through Node.js on an ECS in the same VPC. For more information about how to use other Redis clients, visit the Redis official website.
                      
 
                       
                      The operations described in this section apply only to single-node, master/standby, and Proxy Cluster instances. To use Node.js to connect to a Redis Cluster instance, see Node.js Redis client description.
                      
 
                      
-
                      Prerequisites
                      • A DCS Redis instance has been created and is in the Running state.
                      • 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 GCC compilation environment has been installed on the ECS.
                      
+
                      Prerequisites
                      • A DCS Redis instance has been created and is in the Running state.
                      • 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 GCC compilation environment has been installed on the ECS.
                      
 
                      
 
                      Procedure
                      • For client servers running Ubuntu (Debian series):
                      
 
                      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.
                        
@@ -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 DCS instance and port indicates the port number of DCS instance. For details about how to obtain the IP address/domain name and port, see 1. Change the IP address/domain name and port 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
                      
 
                    
 
                    
@@ -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 DCS instance and port indicates the port number of DCS instance. For details about how to obtain the IP address/domain name and port, see 1. Change the IP address/domain name and port 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 01aaeacef..466842545 100644
--- a/docs/dcs/umn/dcs-ug-0312013.html
+++ b/docs/dcs/umn/dcs-ug-0312013.html
@@ -2,7 +2,7 @@
 
 
          C#
          
 
          Access a DCS Redis instance through C# Client StackExchange.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.
          • 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 GCC compilation environment has been installed on the ECS.
          
+
          Prerequisites
          • A DCS Redis instance has been created and is in the Running state.
          • 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 GCC compilation environment has been installed on the ECS.
          
 
          
 
          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.
            A Windows ECS is used as an example.
            
@@ -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 the IP address/domain name and port as required. ******** indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.

        +

        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.

      4. 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-0312015.html b/docs/dcs/umn/dcs-ug-0312015.html index 947b702fe..8956d20b1 100644 --- a/docs/dcs/umn/dcs-ug-0312015.html +++ b/docs/dcs/umn/dcs-ug-0312015.html @@ -21,9 +21,5 @@
    • Command Renaming
    - -
    -
    Parent topic: Operation Guide
    -
    diff --git a/docs/dcs/umn/dcs-ug-0312016.html b/docs/dcs/umn/dcs-ug-0312016.html index 9d1bb9fc6..2f863baf5 100644 --- a/docs/dcs/umn/dcs-ug-0312016.html +++ b/docs/dcs/umn/dcs-ug-0312016.html @@ -3,145 +3,121 @@

    Viewing Details of a DCS Instance

    On the DCS console, you can view DCS instance details.

    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. Search for DCS instances using any of the following methods:

      • Search by keyword.

        Enter a keyword to search.

        -
      • Select attributes and enter their keywords to search.

        Currently, you can search by name, ID, connection address (IP address:port number), AZ, status, instance type, and cache engine.

        +
      • Select attributes and enter their keywords to search.

        Attributed that can be filtered: Name, ID, IP Address, AZ, Status, Type, Cache Engine

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

      -

    5. On the DCS instance list, click the name of a DCS instance to display more details about it. Table 1 describes the parameters.

      -

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

      Section

      +

    6. On the DCS instance list, click the name of a DCS instance to display more details about it. The following table describes the parameters.

      +

      - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
      Table 1 Parameter description

      Section

      Parameter

      +

      Parameter

      Description

      +

      Description

      Instance Details

      -

      -

      -

      -

      -

      -

      -

      -

      -

      -

      -

      -

      -

      -

      -

      -

      -

      -

      -

      -

      -

      -

      -

      -

      -

      +

      Instance Details

      Name

      +

      Name

      Name of the chosen instance. To modify the instance name, click the icon.

      +

      Name of the DCS instance. To modify the instance name, click .

      Status

      +

      Status

      State of the chosen instance.

      +

      State of the chosen instance.

      ID

      +

      ID

      ID of the chosen instance.

      +

      ID of the chosen instance.

      Cache Engine

      +

      Cache Engine

      Cache engine and cache engine version used by the DCS instance. For example, Redis 3.0.

      +

      Cache engine and cache engine version used by the DCS instance. For example, Redis 4.0.

      Instance Type

      +

      Instance Type

      Type of the selected instance. Currently, supported types include single-node, master/standby, Proxy Cluster, and Redis Cluster.

      +

      Type of the selected instance. Currently, supported types include single-node, master/standby, Proxy Cluster, and Redis Cluster.

      Cache Size

      +

      Cache Size

      Specification of the chosen instance.

      +

      Specification of the chosen instance.

      Used/Available Memory (MB)

      +

      Used/Available Memory (MB)

      The used memory space and maximum available memory space of the chosen instance.

      -

      The used memory space includes:

      -
      • Size of data stored on the DCS instance
      • Size of Redis-server buffers (including client buffer and repl-backlog) and internal data structures
      +

      The used memory space and maximum available memory space of the chosen instance.

      +

      The used memory space includes:

      +
      • Size of data stored on the DCS instance
      • Size of Redis-server buffers (including client buffer and repl-backlog) and internal data structures

      CPU

      +

      CPU

      CPU of the DCS instance.

      +

      CPU of the DCS instance.

      Created

      +

      Created

      Time at which the chosen instance started to be created.

      +

      Time at which the chosen instance started to be created.

      Run

      +

      Run

      Time at which the instance was created.

      +

      Time at which the instance was created.

      Maintenance

      +

      Description

      Time range for any scheduled maintenance activities on cache nodes of this DCS instance. To modify the time window, click the icon.

      +

      Description of the DCS instance. To modify the description, click .

      Description

      +

      Maintenance

      Description of the chosen DCS instance. To modify the description, 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.

      IP Address

      +

      IP Address

      IP address and port number of the chosen instance.

      +

      IP address and port number of the chosen instance.

      Network

      +

      Network

      AZ

      +

      AZ

      Availability zone in which the cache node running the selected DCS instance resides.

      +

      Availability zone in which the cache node running the selected DCS instance resides.

      VPC

      +

      VPC

      VPC in which the chosen instance resides.

      +

      VPC in which the chosen instance resides.

      Subnet

      +

      Subnet

      Subnet in which the chosen instance resides.

      +

      Subnet in which the chosen instance resides.

      Security Group

      +

      Security Group

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

      -

      This parameter is displayed only for DCS Redis 3.0 instances. DCS for Redis 4.0 and 5.0 are based on VPC endpoints and do not support security groups.

      +

      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.
      +

      7. diff --git a/docs/dcs/umn/dcs-ug-0312017.html b/docs/dcs/umn/dcs-ug-0312017.html index d021c6d15..4a2360c03 100644 --- a/docs/dcs/umn/dcs-ug-0312017.html +++ b/docs/dcs/umn/dcs-ug-0312017.html @@ -7,7 +7,7 @@

      Prerequisites

      The DCS instance for which you want to perform a master/standby node switchover is in the Running state.

      -

      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. In the Operation column of the instance, choose More > Master/Standby Switchover.
      +

      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. In the Operation column of the instance, choose More > Master/Standby Switchover, then click OK.
      diff --git a/docs/dcs/umn/dcs-ug-0312018.html b/docs/dcs/umn/dcs-ug-0312018.html index 718861bc0..dada868f8 100644 --- a/docs/dcs/umn/dcs-ug-0312018.html +++ b/docs/dcs/umn/dcs-ug-0312018.html @@ -1,9 +1,11 @@

      Clearing DCS Instance Data

      -

      On the DCS console, you can clear data only for DCS Redis 4.0 and 5.0 instances.

      +

      You can clear data of DCS Redis 4.0 and later instances on the console.

      Clearing instance data cannot be undone and cleared data cannot be recovered. Exercise caution when performing this operation.

      -

      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. Select one or more DCS2.0 instances to clear.
      5. Click Clear data above the instance list.
      6. In the displayed dialog box, click Yes.
      +

      Prerequisites

      The instance is in the Running state.

      +
      +

      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. Select one or more DCS instances.
      5. Click Clear data above the instance list.
      6. In the displayed dialog box, click Yes.
      diff --git a/docs/dcs/umn/dcs-ug-0312019.html b/docs/dcs/umn/dcs-ug-0312019.html index e1f0b28d5..ab1c5f040 100644 --- a/docs/dcs/umn/dcs-ug-0312019.html +++ b/docs/dcs/umn/dcs-ug-0312019.html @@ -2,8 +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 the search bar. In the displayed drop-down list, select the filter criteria to query the desired DCS instances.
      5. Click above the instance list.

        Click the export result displayed in the lower left corner of the page.

        -

      +

      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.
      diff --git a/docs/dcs/umn/dcs-ug-0312022.html b/docs/dcs/umn/dcs-ug-0312022.html index 56cf4846b..ce03577b0 100644 --- a/docs/dcs/umn/dcs-ug-0312022.html +++ b/docs/dcs/umn/dcs-ug-0312022.html @@ -18,18 +18,16 @@
    7. Managing Shards and Replicas
      8. -
    8. Cache Analysis
      +
    9. Analyzing Big Keys and Hot Keys
    10. Managing IP Address Whitelist
      11. -
    11. Viewing Redis Slow Logs
      +
    12. Viewing Redis Slow Queries
    13. Viewing Redis Run Logs
      14. +
    14. Configuring SSL
      +
      15. - -
      -
      Parent topic: Operation Guide
      -
      diff --git a/docs/dcs/umn/dcs-ug-0312024.html b/docs/dcs/umn/dcs-ug-0312024.html index 208fab46e..c5eca32f3 100644 --- a/docs/dcs/umn/dcs-ug-0312024.html +++ b/docs/dcs/umn/dcs-ug-0312024.html @@ -4,7 +4,7 @@

      You can modify the configuration parameters of your DCS instance to optimize DCS performance based on your requirements.

      For example, if you do not need data persistence, set appendonly to no.

      After the instance configuration parameters are modified, the modification takes effect immediately without the need to manually restart the instance. For a cluster instance, the modification takes effect on all shards.

      -

      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. On the Cache Manager page, click the name of the DCS instance you want to configure.
      5. Choose Parameters.
      6. On the Parameters page, click Modify.
      7. Modify parameters based on your requirements.

        Table 1 describes the parameters. In most cases, retain the default values.

        +

        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. On the Cache Manager page, click the name of the DCS instance you want to configure.
        5. Choose Instance Configuration > Parameters.
        6. On the Parameters page, click Modify.
        7. Modify parameters based on your requirements.

          Table 1 describes the parameters. In most cases, retain the default values.

          @@ -19,6 +19,7 @@ @@ -27,7 +28,7 @@ - - @@ -116,6 +118,7 @@ @@ -206,7 +209,7 @@ @@ -230,6 +233,7 @@

          e: Evicted events (events generated when a key is evicted for maxmemory)

          A: an alias for "g$lshzxe"

          The parameter value must contain either K or E. A cannot be used together with any of the characters in "g$lshzxe". For example, the value Kl means that Redis will notify Pub/Sub clients about keyspace events and list commands. The value AKE means Redis will notify Pub/Sub clients about all events.

          +

          Proxy Cluster instances do not have this parameter.

          @@ -259,7 +263,7 @@
          Table 1 DCS Redis instance configuration parameters

          Parameter

          timeout

          The maximum amount of time (in seconds) a connection between a client and the DCS instance can be allowed to remain idle before the connection is terminated. A setting of 0 means that this function is disabled.

          +

          Proxy Cluster instances do not have this parameter.

          0–7200 seconds

          appendfsync

          Controls how often fsync() transfers cached data to the disk. Note that some OSs will perform a complete data transfer but some others only make a "best-effort" attempt.

          +

          Controls how often fsync() transfers cached data to the disk. Note that some OSs will perform a complete data transfer but some others only make a "best-effort" attempt. Single-node instances do not have this parameter.

          There are three settings:

          no: fsync() is never called. The OS will flush data when it is ready. This mode offers the highest performance.

          always: fsync() is called after every write to the AOF. This mode is very slow, but also very safe.

          @@ -35,7 +36,7 @@
          • no
          • always
          • everysec

          everysec

          +

          no

          appendonly

          @@ -107,6 +108,7 @@

          master-read-only

          Sets the instance to be read-only. All write operations will fail.

          +

          Proxy Cluster instances do not have this parameter.
          • yes
          • no

          maxclients

          The maximum number of clients allowed to be concurrently connected to a DCS instance.

          +

          Proxy Cluster instances do not have this parameter.

          Depends on the instance type and specifications.

          latency-monitor-threshold

          Threshold time in latency monitoring. Unit: millisecond.

          -

          Set to 0: Latency monitoring is disabled.

          +

          Set to 0: Latency monitoring is disabled.

          Set to more than 0: All with at least this many milliseconds of latency will be logged.

          By running the LATENCY command, you can perform operations related to latency monitoring, such as obtaining statistical data, and configuring and enabling latency monitoring.

          See the parameter description.

          1. For more information about the parameters described in Table 1, visit https://redis.io/topics/memory-optimization.
          2. The latency-monitor-threshold parameter is usually used for fault location. After locating faults based on the latency information collected, change the value of latency-monitor-threshold to 0 to avoid unnecessary latency.
          3. More about the notify-keyspace-events parameter:
            • The parameter setting must contain at least a K or E.
            • A is an alias for "g$lshzxe" and cannot be used together with any of the characters in "g$lshzxe".
            • For example, the value Kl means that Redis will notify Pub/Sub clients about keyspace events and list commands. The value AKE means Redis will notify Pub/Sub clients about all events.
            -
          +
        8. Configurable parameters and their values vary depending on the instance type.

    15. After you have finished setting the parameters, click Save.
    16. Click Yes to confirm the modification.
      17. diff --git a/docs/dcs/umn/dcs-ug-0312025.html b/docs/dcs/umn/dcs-ug-0312025.html index 08f197b45..b7e745732 100644 --- a/docs/dcs/umn/dcs-ug-0312025.html +++ b/docs/dcs/umn/dcs-ug-0312025.html @@ -4,7 +4,7 @@

      On the DCS console, after creating a DCS instance, you can modify the maintenance time window of the DCS instance on the instance's Basic Information page.

      Prerequisites

      At least one DCS instance has been created.

      -

      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 the DCS instance for which you want to modify the maintenance time window.
      5. Click the Basic Information tab. In the Instance Details area, click the icon next to the Maintenance parameter.
      6. Select a new maintenance time window from the drop-down list. Click to save the modification or to discard the modification.

        The modification will take effect immediately, that is, the new maintenance time window will appear on the Basic Information tab page immediately.

        +

        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 the DCS instance for which you want to modify the maintenance time window.
        5. Click the Basic Information tab. In the Instance Details area, click the icon next to the Maintenance parameter.
        6. Select a new maintenance time window from the drop-down list. Click to save the modification or to discard the modification.

          The modification will take effect immediately, that is, the new maintenance time window will appear on the Basic Information tab page immediately.

      diff --git a/docs/dcs/umn/dcs-ug-0312026.html b/docs/dcs/umn/dcs-ug-0312026.html index b18c54362..b669add04 100644 --- a/docs/dcs/umn/dcs-ug-0312026.html +++ b/docs/dcs/umn/dcs-ug-0312026.html @@ -2,10 +2,10 @@

      Modifying the Security Group

      On the DCS console, after creating a DCS instance, you can modify the security group of the DCS instance on the instance's Basic Information page.

      -

      You can modify the security groups of DCS Redis 3.0 instances but cannot modify those of DCS Redis 4.0 or 5.0 instances.

      +

      You can modify the security groups of DCS Redis 3.0 instances but cannot modify those of DCS Redis 4.0/5.0/6.0 instances.

      Prerequisites

      At least one DCS instance has been created.

      -

      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 the DCS instance for which you want to modify the security group.
      5. Click the Basic Information tab. In the Network area, click next to the Security Group parameter.
      6. Select a new security group from the drop-down list. Click to save the modification or to discard the modification.

        Only the security groups that have been created can be selected from the drop-down list. If you need to create a security group, follow the procedure described Security Group Configurations.

        +

        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 the DCS instance for which you want to modify the security group.
        5. Click the Basic Information tab. In the Network area, click next to the Security Group parameter.
        6. Select a new security group from the drop-down list. Click to save the modification or to discard the modification.

          Only the security groups that have been created can be selected from the drop-down list. If you need to create a security group, follow the procedure described Security Group Configurations.

          The modification will take effect immediately, that is, the new maintenance time window will appear on the Basic Information tab page immediately.

        diff --git a/docs/dcs/umn/dcs-ug-0312029.html b/docs/dcs/umn/dcs-ug-0312029.html index 1ba239aea..b0c840381 100644 --- a/docs/dcs/umn/dcs-ug-0312029.html +++ b/docs/dcs/umn/dcs-ug-0312029.html @@ -5,7 +5,8 @@

        You can only view data storage statistics of DCS Redis 3.0 Proxy Cluster instances. Instances of other types, for example, master/standby, only have one node, and you can view the used memory on the instance details page.

        A Redis Cluster instance has multiple storage nodes. You can check the data storage statistics of a Redis Cluster instance in its Redis Server monitoring data.

        -

        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 Redis cluster instance to view the basic information.
        5. Click the Node Management tab.

          The data volume of each node in the cluster instance is displayed.

          +

          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.

            Filter DCS instances to find the desired one.

            +

          4. Click the name of the desired Proxy Cluster instance to go to the instance details page.
          5. Click the Node Management tab.

            The data volume of each node in the cluster instance is displayed.

            When the data storage capacity of a node in a cluster is used up, you can scale up the instance according to Modifying DCS Instance Specifications.

          diff --git a/docs/dcs/umn/dcs-ug-0312030.html b/docs/dcs/umn/dcs-ug-0312030.html index 1d839e4ce..3c924ebad 100644 --- a/docs/dcs/umn/dcs-ug-0312030.html +++ b/docs/dcs/umn/dcs-ug-0312030.html @@ -6,7 +6,7 @@ - -
          -
          Parent topic: Operation Guide
          -
        diff --git a/docs/dcs/umn/dcs-ug-0312031.html b/docs/dcs/umn/dcs-ug-0312031.html index cfd89c81c..b6abaa386 100644 --- a/docs/dcs/umn/dcs-ug-0312031.html +++ b/docs/dcs/umn/dcs-ug-0312031.html @@ -1,32 +1,33 @@ -

        Configuring a Backup Policy

        +

        Configuring an Automatic Backup Policy

        On the DCS console, you can configure an automatic backup policy. The system then backs up data in your instances according to the backup policy.

        +

        By default, automatic backup is disabled. To enable it, perform the operations described in this section. Single-node instances do not support backup and restoration.

        If automatic backup is not required, disable the automatic backup function in the backup policy.

        -

        Prerequisites

        At least one master/standby DCS instance has been created.

        +

        Prerequisites

        A master/standby or cluster DCS instance is in the Running state.

        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 the DCS instance to display more details about the DCS instance.
        5. On the instance details page, click Backups & Restorations.
        6. Slide to the right to enable automatic backup. Backup policies will be displayed.

          -

          Table 1 Parameters in a backup policy

          Parameter

          +
          - - - - - - -
          Table 1 Parameters in a backup policy

          Parameter

          Description

          +

          Description

          Backup Schedule

          +

          Backup Schedule

          Day of a week on which data in the chosen DCS instance is automatically backed up.

          +

          Day of a week on which data in the chosen DCS instance is automatically backed up.

          You can select one or multiple days of a week.

          Retention Period (days)

          +

          Retention Period (days)

          The number of days that automatically backed up data is retained.

          +

          The number of days that automatically backed up data is retained.

          Backup data will be permanently deleted at the end of retention period and cannot be restored. Value range: 1–7.

          Start Time

          +

          Start Time

          Time at which automatic backup starts. Value: the full hour between 00:00 to 23:00

          +

          Time at which automatic backup starts. Value: the full hour between 00:00 to 23:00

          The DCS checks backup policies once every hour. If the backup start time in a backup policy has arrived, data in the corresponding instance is backed up.

          NOTE:

          Instance backup takes 5 to 30 minutes. The data added or modified during the backup process will not be backed up. To reduce the impact of backup on services, it is recommended that data should be backed up during off-peak periods.

          Only instances in the Running state can be backed up.

          @@ -36,7 +37,8 @@
          -

        7. Click OK.
          8. +

        8. Click OK.
        9. Automatic backup starts at the scheduled time. You can view backup records on the current page.

          After the backup is complete, click Download, Restore, or Delete next to the backup record as required.

          +

          10. diff --git a/docs/dcs/umn/dcs-ug-0312032.html b/docs/dcs/umn/dcs-ug-0312032.html index c951b9c79..5285cca56 100644 --- a/docs/dcs/umn/dcs-ug-0312032.html +++ b/docs/dcs/umn/dcs-ug-0312032.html @@ -5,7 +5,7 @@

          By default, manually backed up data is permanently retained. If backup data is no longer in use, you can delete it manually.

          Prerequisites

          At least one master/standby DCS instance is in the Running state.

          -

          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 the DCS instance to display more details about the DCS instance.
          5. On the instance details page, click Backups & Restorations.
          6. Click Create Backup.
          7. Select a backup file format.

            Only DCS Redis 4.0 and 5.0 instances support backup file format selection.

            +

            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 the DCS instance to display more details about the DCS instance.
            5. On the instance details page, click Backups & Restorations.
            6. Click Create Backup.
            7. Select a backup file format.

              Only DCS Redis 4.0 and later instances support backup file format selection.

            8. In the Create Backup dialog box, click OK.

              Information in the Description text box cannot exceed 128 bytes.

              Instance backup takes 10 to 15 minutes. The data added or modified during the backup process will not be backed up.

              diff --git a/docs/dcs/umn/dcs-ug-0312033.html b/docs/dcs/umn/dcs-ug-0312033.html index 34fa20a3e..4ebc3a699 100644 --- a/docs/dcs/umn/dcs-ug-0312033.html +++ b/docs/dcs/umn/dcs-ug-0312033.html @@ -6,7 +6,7 @@

            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 the DCS instance to display more details about the DCS instance.
            5. On the instance details page, click Backups & Restorations.

              A list of historical backup tasks is then displayed.

            6. Click Restore in the same row as the chosen backup task.
            7. Click OK to start instance restoration.

              Information in the Description text box cannot exceed 128 bytes.

              -
              The Restoration History tab page displays the result of the instance restoration task.

              Instance restoration takes 5 to 30 minutes.

              +
              The Restoration History tab page displays the result of the instance restoration task.

              Instance restoration takes 1 to 30 minutes.

              While being restored, DCS instances do not accept data operation requests from clients because existing data is being overwritten by the backup data.

              diff --git a/docs/dcs/umn/dcs-ug-0312034.html b/docs/dcs/umn/dcs-ug-0312034.html index 0ecf0441c..d923a9adc 100644 --- a/docs/dcs/umn/dcs-ug-0312034.html +++ b/docs/dcs/umn/dcs-ug-0312034.html @@ -1,11 +1,12 @@

              Downloading a Backup File

              -

              Due to the limitations of automatic and manual backups (automatically backed up data can be retained for a maximum of 7 days, and manually backed up data takes space in OBS), you should download the backup files and permanently save them on the local host.

              -

              This function is supported only by master/standby and cluster instances, and not by single-node instances.

              +

              Automatically backed up data can be retained for a maximum of 7 days. Manually backed up data is not free of charge and takes space in OBS. Due to these limitations, you are advised to download the RDB and AOF backup files and permanently save them on the local host.

              +

              This function is supported only by master/standby and cluster instances, and not by single-node instances. To export the data of a single-node instance to an RDB file, you can use redis-cli. For details, see How Do I Export DCS Redis Instance Data?

              Prerequisites

              The instance has been backed up and the backup is still valid.

              -

              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 the DCS instance to display more details about the DCS instance.
              5. On the instance details page, click Backups & Restorations.

                A list of historical backup tasks is then displayed.

                +

                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.

                  Filter DCS instances to find the desired one.

                  +

                4. Click the name of the DCS instance to display more details about the DCS instance.
                5. On the instance details page, click Backups & Restorations.

                  A list of historical backup tasks is then displayed.

                6. Select the historical backup data to be downloaded, and click Download.
                7. In the displayed, Download Backup File dialog box, select either of the following two download methods.

                  Download methods:
                  • By URL
                    1. Set the URL validity period and click Query.
                    2. Download the backup file by using the URL list.

                      If you choose to copy URLs, use quotation marks to quote the URLs when running the wget command in Linux. For example:

                      wget 'https://obsEndpoint.com:443/redisdemo.rdb?parm01=value01&parm02=value02'

                      This is because the URL contains the special character and (&), which will confuse the wget command. Quoting the URL facilitates URL identification.

                      diff --git a/docs/dcs/umn/dcs-ug-0312035.html b/docs/dcs/umn/dcs-ug-0312035.html index 65575a33d..c2f4f18e2 100644 --- a/docs/dcs/umn/dcs-ug-0312035.html +++ b/docs/dcs/umn/dcs-ug-0312035.html @@ -15,9 +15,5 @@
                    3. Migrating Data Online
                  - -
                  -
                  Parent topic: Operation Guide
                  -
                  diff --git a/docs/dcs/umn/dcs-ug-0312036.html b/docs/dcs/umn/dcs-ug-0312036.html index f2a8e028b..79487b9bd 100644 --- a/docs/dcs/umn/dcs-ug-0312036.html +++ b/docs/dcs/umn/dcs-ug-0312036.html @@ -1,140 +1,137 @@

                  Introduction to Migration with DCS

                  -

                  Migration Modes

                  DCS for Redis provides the following migration modes:

                  -
                  • Backup file import: The data source can be an OBS bucket or a Redis instance.
                    • Importing data from an OBS bucket: Download the source Redis data and then upload it to an OBS bucket in the same region as the target DCS Redis instance. DCS will read the backup data from the OBS bucket and migrate the data into the target instance.

                      This migration mode can be used for migrating data from other Redis vendors or self-hosted Redis to DCS for Redis.

                      +

                      Migration Modes

                      DCS for Redis supports online migration (in full or incrementally) and backup migration (by importing backup files).

                      +
                      • Backup migration is suitable when the source and target Redis instances are not connected, and the source Redis instance does not support the SYNC and PSYNC commands. The data source can be an OBS bucket or a Redis instance.
                        • Importing data from an OBS bucket: Download the source Redis data and then upload it to an OBS bucket in the same region as the target DCS Redis instance. DCS will read the backup data from the OBS bucket and migrate the data into the target instance.

                          This migration mode can be used for migrating data from other Redis vendors or self-hosted Redis to DCS for Redis.

                        • Importing data from a Redis instance: Back up the source Redis data and then migrate the backup data to DCS for Redis.
                        -
                      • Migrating data online: If the source and target instances are interconnected and the SYNC and PSYNC commands are supported in the source instance, data can be migrated online in full or incrementally from the source to the target.
                      +
                    • Migrating data online: If the source and target instances are interconnected and the SYNC and PSYNC commands are supported in the source instance, data can be migrated online in full or incrementally from the source to the target.

                    The following table describes data migration modes supported by DCS.

                    -

                    Data can be migrated only from DCS Redis instances or self-hosted Redis. After data migration, change the instance connection address to the target instance address.

                    -

                    Data migration is not supported if the DCS instance is created by another service, such as ROMA Connect, or by calling an API.

                    -
                    -
                    Table 1 DCS data migration modes

                    Migration Mode

                    +
                    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                    Table 1 DCS data migration modes

                    Migration Mode

                    Source

                    +

                    Source

                    Target: DCS

                    +

                    Target: DCS

                    Single-Node and Master/Standby

                    +

                    Single-node or master/standby

                    Proxy Cluster

                    +

                    Proxy Cluster

                    Redis Cluster

                    +

                    Redis Cluster

                    Importing backup files

                    +

                    Importing backup files

                    AOF files in OBS

                    -
                    NOTE:

                    AOF files exported from Redis 4.0/5.0 instances and other instances with RDB compression enabled cannot be imported.

                    +

                    AOF file

                    +
                    NOTE:

                    AOF files exported from Redis 4.0/5.0/6.0 instances and other instances with RDB compression enabled cannot be imported.

                    √

                    +

                    √

                    √

                    +

                    √

                    ×

                    +

                    ×

                    RDB files in OBS

                    +

                    RDB file

                    √

                    +

                    √

                    √

                    +

                    √

                    √

                    +

                    √

                    Migrating data online

                    +

                    Migrating data online

                    DCS for Redis: single-node or master/standby

                    +

                    DCS for Redis: single-node or master/standby

                    √

                    +

                    √

                    √

                    +

                    √

                    √

                    +

                    √

                    DCS for Redis: Proxy Cluster

                    +

                    DCS for Redis: Proxy Cluster

                    NOTE:

                    Proxy Cluster DCS Redis 3.0 instances cannot be used as the source, while Proxy Cluster DCS Redis 4.0 or 5.0 instances can.

                    √

                    +

                    √

                    √

                    +

                    √

                    √

                    +

                    √

                    DCS for Redis: Redis Cluster

                    +

                    DCS for Redis: Redis Cluster

                    √

                    +

                    √

                    √

                    +

                    √

                    √

                    +

                    √

                    Self-hosted Redis: single-node or master/standby

                    +

                    Self-hosted Redis: single-node or master/standby

                    √

                    +

                    √

                    √

                    +

                    √

                    √

                    +

                    √

                    Self-hosted Redis: proxy-based cluster

                    +

                    Self-hosted Redis: proxy-based cluster

                    √

                    +

                    √

                    √

                    +

                    √

                    √

                    +

                    √

                    Self-hosted Redis: Redis Cluster

                    +

                    Self-hosted Redis: Redis Cluster

                    √

                    +

                    √

                    √

                    +

                    √

                    √

                    +

                    √

                    Other Redis: single-node or master/standby

                    +

                    Other Redis: single-node or master/standby

                    ×

                    +

                    ×

                    ×

                    +

                    ×

                    ×

                    +

                    ×

                    Other Redis: proxy-based cluster

                    +

                    Other Redis: proxy-based cluster

                    ×

                    +

                    ×

                    ×

                    +

                    ×

                    ×

                    +

                    ×

                    Other Redis: Redis Cluster

                    +

                    Other Redis: Redis Cluster

                    ×

                    +

                    ×

                    ×

                    +

                    ×

                    ×

                    +

                    ×
                    -
                    • DCS for Redis refers to Redis instances provided by DCS
                    • Self-hosted Redis refers to self-hosted Redis on the cloud, from other cloud vendors, or in on-premises data centers.
                    • Other Redis refers to Redis services provided by other cloud vendors.
                    • √: Supported. ×: Not supported.
                    +
                    • DCS for Redis refers to Redis instances provided by DCS
                    • Self-hosted Redis refers to self-hosted Redis on the cloud, from other cloud vendors, or in on-premises data centers.
                    • Other Redis refers to Redis services provided by other cloud vendors.
                    • √: Supported. ×: Not supported.
                    diff --git a/docs/dcs/umn/dcs-ug-0312037.html b/docs/dcs/umn/dcs-ug-0312037.html index 2669d4ca8..5d9e80c97 100644 --- a/docs/dcs/umn/dcs-ug-0312037.html +++ b/docs/dcs/umn/dcs-ug-0312037.html @@ -1,33 +1,33 @@

                    Importing Backup Files from an OBS Bucket

                    -

                    Scenario

                    Use the DCS console to migrate Redis data from Redis of other vendors or self-hosted Redis to DCS for Redis.

                    -

                    Simply download the source Redis 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.

                    +

                    Scenario

                    Use the DCS console to migrate Redis data from Redis of other vendors or self-hosted Redis to DCS for Redis.

                    +

                    Simply download the source Redis 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.
                    • .rdb backup files of self-hosted Redis 5.0 cannot be imported. .rdb backup files of self-hosted Redis 3.0 or 4.0 can be exported using redis-cli. .rdb files of other cloud Redis can be exported only by creating backup tasks, and cannot be exported by running commands in redis-cli.
                    • 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 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.
                    -

                    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 must clear the instance data before the migration.
                      • If the target instance is Redis 4.0 or 5.0, 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.
                      -
                    -

                    You can use a DCS Redis 3.0, 4.0, or 5.0 instance as the target instance.

                    +

                    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.
                    +

                    -

                    Step 2: Create an OBS Bucket and Upload Backup Files

                    1. Create an OBS bucket.

                      1. Log in to the OBS Console and click Create Bucket.
                      2. Select a region.

                        The OBS bucket must be in the same region as the target DCS Redis instance.

                        -
                      3. Specify Bucket Name.

                        The bucket name must meet the naming rules specified on the console.

                        -
                      4. Set Storage Class to Standard, Warm or Cold.
                      5. Set Bucket Policy to Private, Public Read, or Public Read and Write.
                      6. Configure default encryption.
                      7. Click Create Now.
                      -

                    2. Upload the backup data files to the OBS bucket by using OBS Browser+.

                      If the backup file to be uploaded does not exceed 5 GB, upload the file using the OBS console by referring to step 3.

                      -

                      If the backup file to be uploaded is larger than 5 GB, perform the following steps to upload the file using OBS Browser+.

                      -
                      1. Download OBS Browser+.

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

                        -
                      2. Install OBS Browser+.

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

                        -
                      3. Log in to OBS Browser+.

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

                        -
                      4. Creates a bucket.
                      5. Upload backup data.
                      -

                    3. 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. A maximum of 100 files can be uploaded at a time. The total size cannot exceed 5 GB.

                        To upload objects, drag files or folders to the Upload Object area or click add file.

                        +

                        Step 2: Create an OBS Bucket and Upload Backup Files

                        1. Create an OBS bucket.

                          1. Log in to the OBS Console and click Create Bucket.
                          2. Select a region.

                            The OBS bucket must be in the same region as the target DCS Redis instance.

                            +
                          3. Specify Bucket Name.

                            The bucket name must meet the naming rules specified on the console.

                            +
                          4. Set Storage Class to Standard, Warm or Cold.
                          5. Set Bucket Policy to Private, Public Read, or Public Read and Write.
                          6. Configure default encryption.
                          7. Click Create Now.
                          +

                        2. Upload the backup data files to the OBS bucket by using OBS Browser+.

                          If the backup file to be uploaded does not exceed 5 GB, upload the file using the OBS console by referring to step 3.

                          +

                          If the backup file to be uploaded is larger than 5 GB, perform the following steps to upload the file using OBS Browser+.

                          +
                          1. Download OBS Browser+.

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

                            +
                          2. Install OBS Browser+.

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

                            +
                          3. Log in to OBS Browser+.

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

                            +
                          4. Create a bucket.
                          5. Upload backup data.
                          +

                        3. 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. Click Upload.

                        -

                        Step 3: Create a Migration Task

                        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 Data Migration.
                        4. Click Create Backup Import Task.
                        5. Specify Task Name and Description.
                        6. Select OBS Bucket as the data source and then select the OBS bucket to which you have uploaded backup files.

                          You can upload files in the .aof, .rdb, .zip, or .tar.gz format.

                          +

                          Step 3: Create a Migration Task

                          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 Data Migration.
                          4. Click Create Backup Import Task.
                          5. Specify Task Name and Description.
                          6. Select OBS Bucket as the data source and then select the OBS bucket to which you have uploaded backup files.

                            You can upload files in the .aof, .rdb, .zip, or .tar.gz format.

                            -

                          7. Select the backup files whose data is to be migrated.
                          8. Select the target DCS Redis instance prepared in Step 1: Prepare the Target DCS Redis Instance.
                          9. Enter the password of the target instance. Click Test Connection to verify the password.
                          10. Click Next.
                          11. Confirm the migration task details and click Submit.

                            Go back to the data migration task list. After the migration is successful, the task status changes to Successful.

                            +

                          12. Select the backup files whose data is to be migrated.
                          13. Select the target DCS Redis instance prepared in Step 1: Prepare the Target DCS Redis Instance.
                          14. Enter the password of the target instance. Click Test Connection to verify the password.
                          15. Click Next.
                          16. Confirm the migration task details and click Submit.

                            Go back to the data migration task list. After the migration is successful, the task status changes to Successful.

                          diff --git a/docs/dcs/umn/dcs-ug-0312038.html b/docs/dcs/umn/dcs-ug-0312038.html index 0ec80218c..588cbd3ca 100644 --- a/docs/dcs/umn/dcs-ug-0312038.html +++ b/docs/dcs/umn/dcs-ug-0312038.html @@ -1,54 +1,57 @@

                          Migrating Data Online

                          -

                          Scenario

                          If the source and target instances are interconnected and the SYNC and PSYNC commands are supported in the source instance, data can be migrated online in full or incrementally from the source to the target.

                          +

                          Scenario

                          If the source and target instances are interconnected and the SYNC and PSYNC commands are supported in the source instance, data can be migrated online in full or incrementally from the source to the target.

                          -

                          Prerequisites

                          • Before migrating data, read through Introduction to Migration with DCS to learn about the DCS data migration function and select an appropriate target instance.
                          • To migrate data from a single-node or master/standby instance to a Redis Cluster instance, check if any data exists in DBs other than DB0 in the source instance. If yes, move the data to DB0 by using the open-source tool Rump. Otherwise, the migration will fail because a Redis Cluster instance has only one DB. For details about the migration operations, see Online Migration with Rump.
                          +

                          Impacts on Services

                          During online migration, data is essentially synchronized in full to a new replica. Therefore, perform online migration during low-demand hours.

                          -

                          Obtaining Information About the Source Redis Instance

                          • If the source is a cloud Redis instance, obtain its name.
                          • If the source is self-hosted Redis, obtain its IP address or domain name and port number.
                          +

                          Prerequisites

                          • Before migrating data, read through Introduction to Migration with DCS to learn about the DCS data migration function and select an appropriate target instance.
                          • To migrate data from a single-node or master/standby instance to a cluster instance, check if any data exists in DBs other than DB0 in the source instance. If yes, move the data to DB0 by using the open-source tool Rump. Otherwise, the migration will fail because a cluster instance has only one DB. For details about the migration operations, see Online Migration with Rump.
                          -

                          Prepare the Target DCS Redis Instance

                          • If a target DCS Redis instance is not available, create one first. For details, see Creating a DCS Redis Instance.
                          • If a target instance is available, you do not need to create a new one. However, you must clear the instance data before the migration. For details, see Clearing DCS Instance Data.
                          +

                          Step 1: Obtain Information About the Source Redis Instance

                          • If the source is a cloud Redis instance, obtain its name.
                          • If the source is self-hosted Redis, obtain its IP address or domain name and port number.
                          -

                          Requirements on the Network Between the Online Migration Task, Source Redis, and Target Redis

                          • If the source or target of online migration is Redis in the cloud, the selected Redis instance must be in the same VPC as the migration task. Otherwise, the migration task may fail to connect to the cloud Redis instance.
                          • In special scenarios, if you have enabled cross-VPC access between the migration task and the cloud Redis instance, the cloud Redis instance and the migration task can be in different VPCs.
                          +

                          Step 2: Prepare the Target DCS Redis Instance

                          • If a target DCS Redis instance is not available, create one first. For details, see Creating a DCS Redis Instance.
                          • If a target instance is available, you do not need to create a new one. However, you must clear the instance data before the migration. For details, see Clearing DCS Instance 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.

                            +
                          +
                          +

                          Step 3: Check the Network

                          • If the source or target of online migration is Redis in the cloud, the selected Redis instance must be in the same VPC as the migration task. Otherwise, the migration task may fail to connect to the cloud Redis instance.
                          • In special scenarios, if you have enabled cross-VPC access between the migration task and the cloud Redis instance, the cloud Redis instance and the migration task can be in different VPCs.

                          Table 1 lists the requirements on the network between the online migration task, source Redis, and target Redis.

                          -
                          Table 1 Requirements on the network between the online migration task, source Redis, and target Redis

                          Source Redis Type

                          +
                          - - - - - - - - - - - - - - @@ -56,40 +59,48 @@
                          Table 1 Requirements on the network between the online migration task, source Redis, and target Redis

                          Source Redis Type

                          Target Redis Type

                          +

                          Target Redis Type

                          Network Requirement on Online Migration

                          +

                          Network Requirement on Online Migration

                          Redis in the cloud

                          +

                          Redis in the cloud

                          Redis in the cloud

                          +

                          Redis in the cloud

                          When creating an online migration task, ensure that the online migration task is in the same VPC as the source and target Redis. If they are not in the same VPC, enable cross-network access between the migration task and the source and target Redis. To enable cross-network access, create a VPC peering connection by referring to section "VPC Peering Connection" in Creating a VPC.

                          +

                          When creating an online migration task, ensure that the online migration task is in the same VPC as the source and target Redis. If they are not in the same VPC, enable cross-network access between the migration task and the source and target Redis. To enable cross-network access, create a VPC peering connection by referring to section "VPC Peering Connection" in Creating a VPC.

                          Redis in the cloud

                          +

                          Redis in the cloud

                          Self-hosted Redis

                          +

                          Self-hosted Redis

                          When creating an online migration task, ensure that the migration task and the source Redis are in the same VPC. Then, enable cross-network access between the migration task and the target Redis.

                          +

                          When creating an online migration task, ensure that the migration task and the source Redis are in the same VPC. Then, enable cross-network access between the migration task and the target Redis.

                          To enable cross-network access, create a VPC peering connection by referring to section "VPC Peering Connection" in Creating a VPC.

                          Self-hosted Redis

                          +

                          Self-hosted Redis

                          Redis in the cloud

                          +

                          Redis in the cloud

                          When creating an online migration task, ensure that the migration task and the target Redis are in the same VPC. Then, enable cross-network access between the migration task and the source Redis.

                          +

                          When creating an online migration task, ensure that the migration task and the target Redis are in the same VPC. Then, enable cross-network access between the migration task and the source Redis.

                          To enable cross-network access, create a VPC peering connection by referring to section "VPC Peering Connection" in Creating a VPC.

                          Self-hosted Redis

                          +

                          Self-hosted Redis

                          Self-hosted Redis

                          +

                          Self-hosted Redis

                          After creating an online migration task, enable cross-network access between the migration task and the source and target Redis, respectively.

                          +

                          After creating an online migration task, enable cross-network access between the migration task and the source and target Redis, respectively.

                          To enable cross-network access, create a VPC peering connection by referring to section "VPC Peering Connection" in Creating a VPC.
                          -

                          Create a Migration Task

                          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 Data Migration. The migration task list is displayed.
                          4. Click Create Online Migration Task.
                          5. Enter the task name and description.
                          6. Select a VPC and security group.
                          7. Click Next.
                          8. Click Submit.
                          +

                          Step 4: Create a Migration Task

                          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 Data Migration. The migration task list is displayed.
                          4. Click Create Online Migration Task.
                          5. Enter the task name and description.
                          6. Configure the VPC, subnet, and security group for the migration task.

                            The VPC, subnet, and security group facilitate the migration. Ensure that the migration resources can access the source and target Redis instances.

                            +
                            • The migration task uses a tenant IP address (Migration ECS displayed on the Basic Information page of the task.) If a whitelist is configured for the source or target instance, add the migration IP address to the whitelist or disable the whitelist.
                            • To allow the VM used by the migration task to access the source and target instances, set an outbound rule for the task's security group to allow traffic through the IP addresses and ports of the source and target instances. By default, all outbound traffic is allowed.
                            +
                            +

                          7. Click Next.
                          8. Click Submit.

                          Configuring the Online Migration Task

                          1. On the Online Migration tab page, click Configure in the row containing the online migration task you just created.
                          2. Specify Migration Type.

                            Supported migration types are Full and Full + incremental, which are described in Table 2.

                            -
                            Table 2 Migration type description

                            Migration Type

                            +
                            - - - - -
                            Table 2 Migration type description

                            Migration Type

                            Description

                            +

                            Description

                            Full

                            +

                            Full

                            Suitable for scenarios where services can be interrupted. Data is migrated at one time. Source instance data updated during the migration will not be migrated to the target instance.

                            +

                            Suitable for scenarios where services can be interrupted. Data is migrated at one time. Source instance data updated during the migration will not be migrated to the target instance.

                            Full + incremental

                            +

                            Full + incremental

                            Suitable for scenarios requiring minimal service downtime. The incremental migration parses logs to ensure data consistency between the source and target instances.

                            +

                            Suitable for scenarios requiring minimal service downtime. The incremental migration parses logs to ensure data consistency between the source and target instances.

                            Once incremental migration starts, it remains Migrating until you click Stop in the Operation column. After the migration is stopped, data in the source instance will not be lost, but data will not be written to the target instance. When the transmission network is stable, the delay of incremental migration is within seconds. The actual delay depends on the transmission quality of the network link.
                            -

                          3. Configure source Redis and target Redis.

                            1. Source Redis Type: Select Redis in the cloud or Self-hosted Redis as required.
                              • Redis in the cloud: a DCS Redis instance that is in the same VPC as the migration task
                              • Self-hosted Redis: self-hosted Redis in another cloud, or in on-premises data centers. If you select this option, enter Redis addresses.
                              -
                            2. If the instance is password-protected, you can click Test Connection to check whether the instance password is correct and whether the network is connected.
                            -

                          4. For Target Instance, select the DCS Redis Instance prepared in Prepare the Target DCS Redis Instance.

                            If the instance is password-protected, you can click Test Connection to check whether the instance password meets the requirements.

                            -

                            If the source and target Redis instances are connected but are in different regions of DCS, you can only select Self-hosted Redis for Target Redis Type and enter the instance addresses, regardless of whether the target Redis instance is self-hosted or in the cloud.

                            +

                          5. Configure source Redis and target Redis.

                            1. Source Redis Type: Select Redis in the cloud or Self-hosted Redis as required.
                              • Redis in the cloud: a DCS Redis instance that is in the same VPC as the migration task
                              • Self-hosted Redis: self-hosted Redis in another cloud, or in on-premises data centers. If you select this option, enter Redis addresses.
                              +
                            2. If the instance is password-protected, you can click Test Connection to check whether the instance password is correct and whether the network is connected.
                            +

                          6. For Target Instance, select the DCS Redis Instance prepared in Step 2: Prepare the Target DCS Redis Instance.

                            If the instance is password-protected, you can click Test Connection to check whether the instance password meets the requirements.

                            +

                            If the source and target Redis instances are connected but are in different regions of DCS, you can only select Self-hosted Redis for Target Redis Type and enter the instance addresses, regardless of whether the target Redis instance is self-hosted or in the cloud.

                            -

                          7. Click Next.
                          8. Confirm the migration task details and click Submit.

                            Go back to the data migration task list. After the migration is successful, the task status changes to Successful.

                            -

                            If the migration type is full+incremental, the migration task status will remain Migrating until you click Stop.

                            +

                          9. Click Next.
                          10. Confirm the migration task details and click Submit.

                            Go back to the data migration task list. After the migration is successful, the task status changes to Successful.

                            +

                            If the migration type is full+incremental, the migration task status will remain Migrating until you click Stop.

                            11. +

                            Verifying the Migration

                            After the migration is complete, use redis-cli to connect the source and target Redis instances to check data integrity.

                            +
                            1. Connect to the source Redis and the target Redis.
                            2. Run the info keyspace command to check the values of keys and expires.

                              +
                            3. Calculate the differences between the values of keys and expires of the source Redis and the target Redis. If the differences are the same, the data is complete and the migration is successful.
                            +

                            During full migration, source Redis data updated during the migration will not be migrated to the target instance.

                            +

                            diff --git a/docs/dcs/umn/dcs-ug-0312039.html b/docs/dcs/umn/dcs-ug-0312039.html index 84de3888e..fb21c829f 100644 --- a/docs/dcs/umn/dcs-ug-0312039.html +++ b/docs/dcs/umn/dcs-ug-0312039.html @@ -9,9 +9,5 @@
                          11. Changing Instance Passwords
                            12. - -
                            -
                            Parent topic: Operation Guide
                            -
                            diff --git a/docs/dcs/umn/dcs-ug-0326008.html b/docs/dcs/umn/dcs-ug-0326008.html index 020316803..26015d7ee 100644 --- a/docs/dcs/umn/dcs-ug-0326008.html +++ b/docs/dcs/umn/dcs-ug-0326008.html @@ -4,37 +4,39 @@

                            You can create one or more DCS Redis instances with the required computing capabilities and storage space based on service requirements.

                            The system automatically schedules the task every 3 minutes for checking whether resources are available or sold out.

                            -

                            Creating a DCS Redis Instance

                            1. Log in to the DCS console.
                            2. Click in the upper left corner of the management console and select a region and a project.
                            3. Click Create DCS Instance.
                            4. Select a region closest to your application to reduce latency and accelerate access.
                            5. Specify the following instance parameters based on the information collected in Identifying Requirements.

                              1. Cache Engine:

                                Select Redis.

                                -
                              2. Version:

                                Currently, 3.0, 4.0, and 5.0 versions are supported.

                                -
                                • When creating a Proxy Cluster instance, you can only select version 3.0.
                                • When creating a Redis Cluster instance, you can select versions 4.0 or 5.0.
                                +

                                Prerequisites

                                You have prepared necessary resources.

                                +
                                +

                                Creating a DCS Redis Instance

                                1. Log in to the DCS console.
                                2. Click in the upper left corner of the management console and select a region and a project.
                                3. Click Create DCS Instance.
                                4. Select a region closest to your application to reduce latency and accelerate access.
                                5. Specify the following instance parameters based on the information collected in Identifying Requirements.

                                  1. Cache Engine:

                                    Select Redis.

                                    +
                                  2. Version:

                                    Currently, versions 3.0/4.0/5.0/6.0 are supported.

                                    +
                                    • When creating a Proxy Cluster instance, you can only select version 3.0.
                                    • When creating a Redis Cluster instance, you can select versions 4.0 or 5.0.
                                    • The Redis version cannot be changed once the instance is created. To use a later Redis version, create another DCS Redis instance and then migrate data from the old instance to the new one.
                                    • The method of connecting a client to a Redis Cluster instance is different from that of connecting a client to other types of instances. For details, see Accessing a DCS Redis Instance Through redis-cli.
                                    -
                                  3. Set Instance Type to Single-node, Master/Standby, Proxy Cluster or Redis Cluster.
                                  4. Set CPU Architecture to x86.
                                  5. Set Replicas. The default value is 2 (including the master).

                                    This parameter is displayed only when you select Redis 4.0 or Redis 5.0 and the instance type is master/standby or Redis Cluster.

                                    +
                                  6. Set Instance Type to Single-node, Master/Standby, Proxy Cluster or Redis Cluster.
                                  7. Set CPU Architecture to x86.
                                  8. Set Replicas. The default value is 2 (including the master).

                                    This parameter is displayed only when you select Redis 4.0/5.0/6.0 and the instance type is master/standby or Redis Cluster.

                                  9. Select an AZ.

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

                                    • To accelerate access, deploy your instance and your application in the same AZ.
                                    • There are multiple AZs in each region. If resources are insufficient in an AZ, the AZ will be unavailable. In this case, select another AZ.
                                  10. Instance Specification:

                                    The remaining quota is displayed on the console.

                                    To apply to increase quota, click Increase quota below the specifications.

                                  -

                                6. Configure the instance network parameters.

                                  1. For VPC, select a created VPC, subnet, and specify the IP address.

                                    You can choose to obtain an automatically assigned IP address or manually specify an IP address that is available in the selected subnet.

                                    -

                                    For a DCS Redis 4.0 or 5.0 instance, you can specify a port numbering in the range from 1 to 65535. If no port is specified, the default port 6379 will be used. For a DCS Redis 3.0 instance, the port cannot be customized. Port 6379 will be used.

                                    +

                                  2. Configure the instance network parameters.

                                    1. Select a VPC and a subnet.
                                    2. Configure the IP address.

                                      Redis Cluster instances only support automatically-assigned IP addresses. The other instance types support both automatically-assigned IP addresses and manually-specified IP addresses. You can manually specify an IP address available in your subnet.

                                      +

                                      For a DCS Redis 4.0 or later instance, you can specify a port numbering in the range from 1 to 65535. If no port is specified, the default port 6379 will be used. For a DCS Redis 3.0 instance, the port cannot be customized. Port 6379 will be used.

                                    3. Select a security group.

                                      A security group is a set of rules that control access to ECSs. It provides access policies for mutually trusted ECSs with the same security protection requirements in the same VPC.

                                      -

                                      This parameter is displayed only for DCS Redis 3.0 instances. DCS Redis 4.0 and 5.0 instances are based on VPC endpoints and do not support security groups. To control access to a DCS Redis 4.0 or 5.0 instance, configure a whitelist after instance creation. For details, see Managing IP Address Whitelist.

                                      +

                                      This parameter is displayed only for DCS Redis 3.0 instances. DCS Redis 4.0/5.0/6.0 instances are based on VPC endpoints and do not support security groups. To control access to a DCS Redis 4.0/5.0/6.0 instance, configure a whitelist after instance creation. For details, see Managing IP Address Whitelist.

                                    -

                                  3. Set the instance password.

                                    This password is used for accessing the DCS Redis instance.

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

                                    -

                                    The password must meet the following requirements:

                                    -
                                    • Cannot be left blank.
                                    • Can contain 8 to 32 characters.
                                    • Must contain at least three of the following character types:
                                      • Lowercase letters
                                      • Uppercase letters
                                      • Digits
                                      • special characters (`~!@#$^&*()-_=+\|{}:,<.>/?)
                                      -
                                    +

                                  4. Set the instance password.

                                    • Select Yes or No for Password Protected.
                                      • Password-free access carries security risks. Exercise caution when selecting this mode.
                                      -
                                -

                              3. Click More Settings to display more configurations, including auto backup.

                                1. Specify Name and Description.

                                  The value of Name can contain 4 to 64 characters.

                                  -
                                2. Choose whether to enable Auto Backup.

                                  This parameter is displayed only when the instance type is master/standby or cluster. You can enable and schedule automated backup now or after the instance is created. For more information on how to configure a backup policy, see Backing Up and Restoring DCS Instances.

                                  -
                                3. Rename critical commands.

                                  Command Renaming is displayed for Redis 4.0 and 5.0. Currently, you can only rename the COMMAND, KEYS, FLUSHDB, FLUSHALL, and HGETALL commands.

                                  +
                                4. Password and Confirm Password: These parameters indicate the password of accessing the DCS Redis instance, and are displayed only when Password Protected is set to Yes.

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

                                  +
                                  +
                                  5. +

                                5. Configure Parameter Configuration.

                                  You can select Default Templates or Use custom template.

                                  +
                                  • 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.
                                  +
                                  +

                                6. 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.

                                  +

                                7. Specify the quantity.
                                8. 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.

                                  +

                                9. 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.

                                10. Click Create Now.

                                  The displayed page shows the instance information you have specified.

                                  -

                                11. Confirm the instance information and click Submit.
                                12. Return to the Cache Manager page to view and manage your DCS instances.

                                  1. Creating a single-node or master/standby DCS Redis 3.0 instance takes 5 to 15 minutes. Creating a cluster DCS Redis 3.0 instance takes 30 minutes.

                                    DCS Redis 4.0 and 5.0 instances are containerized and can be created within seconds.

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

                                13. Confirm the instance information and click Submit.
                                14. Return to the Cache Manager page to view and manage your DCS instances.

                                  1. Creating a single-node or master/standby DCS Redis 3.0 instance takes 5 to 15 minutes. Creating a cluster DCS Redis 3.0 instance takes 30 minutes.DCS Redis 4.0 and later instances are containerized and can be created within seconds.
                                  2. After a DCS instance has been successfully created, it enters the Running state by default.
                                  • If the new DCS instance failed to be created, delete the unsuccessful instance creation task by following the procedure in Deleting Instance Creation Tasks That Have Failed to Run. Then, create the DCS instance again. If the DCS instance still fails to be created, contact customer service.
                                  • There is the management plane and the tenant plane. The tenant plane is also called the pod zone. During the creation of a DCS instance, a VM is created in the pod zone. If the instance creation fails, the instance status changes to Faulty, and the error message "Failed to connect to the instance. Network exceptions may have occurred in the pod zone." is displayed, indicating that the management plane cannot be connected to the tenant plane.

                                diff --git a/docs/dcs/umn/dcs-ug-0326009.html b/docs/dcs/umn/dcs-ug-0326009.html index 9837aa9b5..b0ce7bb58 100644 --- a/docs/dcs/umn/dcs-ug-0326009.html +++ b/docs/dcs/umn/dcs-ug-0326009.html @@ -2,10 +2,11 @@

                                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 5.0, 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

                                    +
                                    • 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}

                                    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.
                                    @@ -18,13 +19,13 @@

                                    make

                                    cd src

                              -

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

                              Perform the following procedure to access a DCS Redis 3.0 instance, or a single-node or master/standby DCS Redis 4.0 or 5.0 instance.

                              +

                            7. 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 ${instance IP} -p 6379 -a ${password}

                              1. If the instance is password-free, connect it by running the ./redis-cli -h ${instance IP} -p 6379 command.
                              2. If the instance is password-protected, connect it by running the ./redis-cli -h ${instance IP} -p 6379 -a ${password} command.

                            8. 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

                                -

                                {dcs_instance_address} indicates the IP address 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 and port number are obtained in 1.

                                +

                                {dcs_instance_address} indicates the IP address 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 and port number are obtained in 1.

                                Example:
                                root@ecs-redis:~/redis-5.0.8/src# ./redis-cli -h 192.168.0.85 -p 6379 -a ****** -c
 192.168.0.85:6379>
                                @@ -63,7 +64,7 @@ OK

                            Procedure (Windows)

                            Download the compilation package of the Redis client for Windows. (This is not the source code package.) Decompress the package in any directory, open the CLI tool cmd.exe, and go to the directory. Then, run the following command to access the DCS Redis instance:

                            redis-cli.exe -h XXX -p 6379

                            -

                            XXX indicates the IP address of the DCS instance and 6379 is an example port number used for accessing a DCS instance. For details about how to obtain the IP address and port number, see Viewing Details of a DCS Instance. Change the IP address and port as required.

                            +

                            XXX indicates the IP address of the DCS instance and 6379 is an example port number used for accessing the DCS instance. For details about how to obtain the IP address and port number, see Viewing Details of a DCS Instance. Change the IP address and port as required.

                            diff --git a/docs/dcs/umn/dcs-ug-0326010.html b/docs/dcs/umn/dcs-ug-0326010.html deleted file mode 100644 index 91a60aeed..000000000 --- a/docs/dcs/umn/dcs-ug-0326010.html +++ /dev/null @@ -1,23 +0,0 @@ - - - -

                            Operation Guide

                            - -

                            -
                            - - - diff --git a/docs/dcs/umn/dcs-ug-0326011.html b/docs/dcs/umn/dcs-ug-0326011.html index 42253396b..912d9201f 100644 --- a/docs/dcs/umn/dcs-ug-0326011.html +++ b/docs/dcs/umn/dcs-ug-0326011.html @@ -4,50 +4,68 @@

                            On the DCS console, you can scale a DCS Redis instance to a larger or smaller capacity.

                            • Modify instance specifications during off-peak hours.
                            • If your DCS instances are too old to support scaling, contact technical support to upgrade the instances.
                            • Services may be interrupted for seconds during the modification. Therefore, services connected to Redis must support reconnection.
                            +

                            Change of the Instance Type

                            • Supported instance type changes:
                              • From single-node to master/standby: Supported by Redis 3.0, and not by Redis 4.0/5.0/6.0.
                              • From master/standby to Proxy Cluster: Supported by Redis 3.0, and not by Redis 4.0/5.0/6.0.

                                If the data of a master/standby DCS Redis 3.0 instance is stored in multiple databases, or in non-DB0 databases, the instance cannot be changed to the Proxy Cluster type. A master/standby instance can be changed to the Proxy Cluster type only if its data is stored only on DB0.

                                +
                              • From cluster types to other types: Not supported.
                              +
                            • Impact of instance type changes:
                              • From single-node to master/standby for a DCS Redis 3.0 instance:

                                The instance cannot be connected for several seconds and remains read-only for about 1 minute.

                                +
                              • From master/standby to Proxy Cluster for a DCS Redis 3.0 instance:

                                The instance cannot be connected and remains read-only for 5 to 30 minutes.

                                +
                              +
                            +

                            Scaling

                            • The following table lists scaling options supported by different DCS instances. -
                              Table 1 Scaling options supported by different DCS instances

                              Cache Engine

                              +
                              - - - - - - - - - - - - - - - - - - - + + + + + + @@ -55,12 +73,13 @@

                              If the reserved memory of a DCS Redis 3.0 instance is insufficient, the scaling may fail when the memory is used up.

                              -
                            • Impact of scaling:
                              • Single-node and master/standby
                                • A DCS Redis 4.0 or 5.0 instance will be disconnected for several seconds and remain read-only for about 1 minute.
                                • A DCS Redis 3.0 instance will be disconnected and remain read-only for 5 to 30 minutes.
                                • For scaling up, only the memory of the instance is expanded. The CPU processing capability is not improved.
                                • Data of single-node instances may be lost because they do not support data persistence. After scaling, check whether the data is complete and import data if required.
                                • Backup records of master/standby instances cannot be restored after scaling down.
                                +
                              • Impact of scaling:
                                • Single-node and master/standby
                                  • A DCS Redis 4.0/5.0/6.0 instance will be disconnected for several seconds and remain read-only for about 1 minute.
                                  • A DCS Redis 3.0 instance will be disconnected and remain read-only for 5 to 30 minutes.
                                  • For scaling up, only the memory of the instance is expanded. The CPU processing capability is not improved.
                                  • Data of single-node instances may be lost because they do not support data persistence. After scaling, check whether the data is complete and import data if required.
                                  • Backup records of master/standby instances cannot be used after scaling down.
                                • Cluster
                                  • If the shard quantity is not decreased, the instance can always be connected, but the CPU usage will increase, compromising performance by up to 20%, and the latency will increase during data migration.
                                  • During scaling up, new Redis Server nodes are added, and data is automatically balanced to the new nodes.
                                  • Nodes will be deleted if the shard quantity decreases. To prevent disconnection, ensure that the deleted nodes are not directly referenced in your application.
                                  • Ensure that the used memory of each node is less than 70% of the maximum memory per node of the new flavor. Otherwise, you cannot perform the scale-in.
                                  • If the memory becomes full during scaling due to a large amount of data being written, scaling will fail. Modify specifications during off-peak hours.
                                  • Scaling involves data migration. The latency for accessing the key being migrated increases. For a Redis Cluster instance, ensure that the client can properly process the MOVED and ASK commands. Otherwise, requests will fail.
                                  • Before scaling, perform cache analysis to ensure that no big keys (≥ 512 MB) exist in the instance. Otherwise, scaling may fail.
                                  • Backup records created before scaling cannot be restored.
                                +
                              • Notes on changing the number of replicas of a DCS Redis 4.0 or 5.0 instance:

                                Deleting replicas interrupts connections. If your application cannot reconnect to Redis or handle exceptions, you need to restart the application after scaling.

                              -

                              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.
                              1. Choose More > Modify Specifications in the row containing the DCS instance.
                              2. On the Modify Specifications page, select the desired specification and click Next.
                              3. Click Submit.

                                On the displayed Background Tasks page, view the modification status. For more information, see Viewing Background Tasks.

                                +

                                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.
                                1. Choose More > Modify Specifications in the row containing the DCS instance.
                                2. On the Modify Specifications page, select the desired specification.
                                3. Click Submit to start modifying the DCS instance.

                                  You can go to Background Tasks page to view the modification status. For more information, see Viewing Background Tasks.

                                  Specification modification of a single-node or master/standby DCS instance takes about 5 to 30 minutes to complete, while that of a cluster DCS instance takes a longer time. After an instance is successfully modified, it changes to the Running state.
                                  • If the specification modification of a single-node DCS instance fails, the instance is temporarily unavailable for use. The specification remains unchanged. Some management operations (such as parameter configuration and specification modification) are temporarily not supported. After the specification modification is completed in the backend, the instance changes to the new specification and becomes available for use again.
                                  • If the specification modification of a master/standby or cluster DCS instance fails, the instance is still available for use with its original specifications. Some management operations (such as parameter configuration, backup, restoration, and specification modification) are temporarily not supported. Remember not to read or write more data than allowed by the original specifications; otherwise, data loss may occur.
                                  • After the specification modification is successful, the new specification of the instance takes effect.
                                  diff --git a/docs/dcs/umn/dcs-ug-0326013.html b/docs/dcs/umn/dcs-ug-0326013.html index 7a0234ba4..625fb30c1 100644 --- a/docs/dcs/umn/dcs-ug-0326013.html +++ b/docs/dcs/umn/dcs-ug-0326013.html @@ -2,11 +2,11 @@

                                  Restarting DCS Instances

                                  On the DCS console, you can restart one or multiple DCS instances at a time.

                                  -
                                  • After a single-node DCS instance is restarted, data will be deleted from the instance.
                                  • While a DCS instance is restarting, it cannot be read from or written to.
                                  • An attempt to restart a DCS instance while it is being backed up may result in a failure.
                                  +
                                  • After a single-node DCS instance is restarted, data will be deleted from the instance.
                                  • While a DCS instance is restarting, it cannot be read from or written to.
                                  • An attempt to restart a DCS instance while it is being backed up may result in a failure.
                                  • Restarting a DCS instance will disconnect the original client. You are advised to configure automatic reconnection in your application.

                                  Prerequisites

                                  The DCS instances you want to restart are in the Running or Faulty state.

                                  -

                                  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. On the Cache Manager page, select one or more DCS instances you want to restart.
                                  5. Click Restart above the DCS instance list.
                                  6. In the displayed dialog box, click Yes.

                                    It takes 1 to 30 minutes to restart DCS instances. After DCS instances are restarted, their status changes to Running.

                                    +

                                    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. On the Cache Manager page, select one or more DCS instances you want to restart.
                                    5. Click Restart above the DCS instance list.
                                    6. In the displayed dialog box, click Yes.

                                      It takes 10 seconds to 30 minutes to restart DCS instances. After DCS instances are restarted, their status changes to Running.

                                      • To restart a single instance, you can also click Restart in the same row as the instance.
                                      • The time required for restarting a DCS instance depends on the cache size of the instance.

                                    diff --git a/docs/dcs/umn/dcs-ug-0326014.html b/docs/dcs/umn/dcs-ug-0326014.html index 0b6f10677..974e03ea6 100644 --- a/docs/dcs/umn/dcs-ug-0326014.html +++ b/docs/dcs/umn/dcs-ug-0326014.html @@ -8,8 +8,8 @@

                                    Procedure

                                    Deleting DCS Instances

                                    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. On the Cache Manager page, select one or more DCS instances you want to delete.

                                      DCS instances in the Creating, Restarting, Upgrading, Resizing, Clearing data, Backing up, or Restoring state cannot be deleted.

                                      -

                                    5. Choose More > Delete above the instance list.
                                    6. In the displayed dialog box, click Yes.

                                      It takes 1 to 30 minutes to delete DCS instances.

                                      -

                                      To delete a single instance, choose Operation > More > Delete in the same row as the instance.

                                      +

                                    7. Choose More > Delete above the instance list.
                                    8. Click Yes to delete the instance.

                                      It takes 1 to 30 minutes to delete DCS instances.

                                      +

                                      To delete a single instance, choose Operation > More > Delete in the same row as the instance.

                                    Deleting Instance Creation Tasks That Have Failed to Run

                                    diff --git a/docs/dcs/umn/dcs-ug-0326017.html b/docs/dcs/umn/dcs-ug-0326017.html index f33076f54..4440a3beb 100644 --- a/docs/dcs/umn/dcs-ug-0326017.html +++ b/docs/dcs/umn/dcs-ug-0326017.html @@ -1,11 +1,8 @@ - -

                                    Auditing

                                    - -

                                    +

                                    Auditing

                                    +

                                    -
                                    • Operations That Can Be Recorded by CTS
                                      diff --git a/docs/dcs/umn/dcs-ug-0326018.html b/docs/dcs/umn/dcs-ug-0326018.html index 4ca3abbbc..920dbad97 100644 --- a/docs/dcs/umn/dcs-ug-0326018.html +++ b/docs/dcs/umn/dcs-ug-0326018.html @@ -208,6 +208,34 @@
                              • + + + + + + + + + + + + + + + +
                              Table 1 Scaling options supported by different DCS instances

                              Cache Engine

                              Single-Node

                              +

                              Single-Node

                              Master/Standby

                              +

                              Master/Standby

                              Redis Cluster

                              +

                              Redis Cluster

                              Proxy Cluster

                              +

                              Proxy Cluster

                              Redis 3.0

                              +

                              Redis 3.0

                              Scaling up/down

                              +

                              Scaling up/down

                              Scaling up/down

                              +

                              Scaling up/down

                              N/A

                              +

                              N/A

                              Scaling up

                              +

                              Scaling up

                              Redis 4.0

                              +

                              Redis 4.0

                              Scaling up/down

                              +

                              Scaling up/down

                              Scaling up/down

                              +

                              Scaling up/down

                              Scaling up

                              +

                              Scaling up

                              N/A

                              +

                              N/A

                              Redis 5.0

                              +

                              Redis 5.0

                              Scaling up/down

                              +

                              Scaling up/down

                              Scaling up/down

                              +

                              Scaling up/down

                              Scaling up

                              +

                              Scaling up

                              N/A

                              +

                              N/A

                              +

                              Redis 6.0

                              +

                              Scaling up/down

                              +

                              Scaling up/down

                              +

                              N/A

                              +

                              N/A

                              submitFlushDCSInstanceRequest

                              Accessing Web CLI

                              +

                              Redis

                              +

                              webCliLogin

                              +

                              Running commands in Web CLI

                              +

                              Redis

                              +

                              webCliCommand

                              +

                              Exiting Web CLI

                              +

                              Redis

                              +

                              webCliLogout

                              +

                              Migrating offline data

                              +

                              Redis

                              +

                              offlineMigrate

                              +
                              diff --git a/docs/dcs/umn/dcs-ug-0326019.html b/docs/dcs/umn/dcs-ug-0326019.html index 4ed82096a..3e4c87592 100644 --- a/docs/dcs/umn/dcs-ug-0326019.html +++ b/docs/dcs/umn/dcs-ug-0326019.html @@ -2,19 +2,71 @@

                              DCS Metrics

                              Introduction

                              This section describes DCS metrics reported to Cloud Eye as well as their namespaces and dimensions. You can use the Cloud Eye console or call APIs to query the DCS metrics and alarms.

                              -

                              Different types of instances are monitored on different dimensions.

                              -
                              • Single-node:

                                Single-node instances are monitored on the instance dimension. The monitoring is conducted on the Redis Server.

                                -
                              • Master/standby:

                                Master/Standby instances are monitored on the instance and Redis Server dimensions. Instance monitoring covers the master node, while Redis Server monitoring covers the master and standby nodes.

                                -
                              • Cluster:

                                Proxy Cluster instances are monitored on the instance, Redis Server, and proxy dimensions. Instance monitoring covers the aggregated master node data, Redis Server monitoring covers each shard in the cluster, and proxy monitoring covers each proxy in the cluster.

                                -

                                Redis Cluster instances are monitored on the instance and Redis Server dimensions. Instance monitoring covers the aggregated master node data and Redis Server monitoring covers each shard in the cluster.

                                -
                              + +
                              + + + + + + + + + + + + + + + + + + + + + + + + + + +
                              Table 1 Monitoring dimensions for different instance types

                              Instance Type

                              +

                              Instance Monitoring

                              +

                              Redis Server Monitoring

                              +

                              Proxy Monitoring

                              +

                              Single-node

                              +

                              Supported

                              +

                              The monitoring on the instance dimension is conducted on the Redis Server.

                              +

                              N/A

                              +

                              N/A

                              +

                              Master/standby

                              +

                              Supported

                              +

                              The master node is monitored.

                              +

                              Supported

                              +

                              The master and standby nodes is monitored.

                              +

                              N/A

                              +

                              Proxy Cluster

                              +

                              Supported

                              +

                              The monitoring data is the aggregated master node data.

                              +

                              Supported

                              +

                              Each shard is monitored.

                              +

                              Supported

                              +

                              Each proxy is monitored.

                              +

                              Redis Cluster

                              +

                              Supported

                              +

                              The monitoring data is the aggregated master node data.

                              +

                              Supported

                              +

                              Each shard is monitored.

                              +

                              N/A

                              +
                              +

                              Namespace

                              SYS.DCS

                              -

                              DCS Redis 3.0 Instance Metrics

                              The Monitored Objects and Dimensions column lists instances and dimensions that support the corresponding metrics.

                              +

                              DCS Redis 3.0 Instance Metrics

                              • The Monitored Object column lists instances that support the corresponding metrics.
                              • Dimensions lists the metric dimensions.
                              -
                              Table 1 DCS Redis 3.0 instance metrics

                              Metric ID

                              +
                              @@ -22,7 +74,7 @@ - @@ -37,10 +89,7 @@ - @@ -54,10 +103,7 @@ - @@ -71,10 +117,7 @@ - @@ -88,10 +131,7 @@ - @@ -104,10 +144,7 @@ - @@ -120,10 +157,7 @@ - @@ -136,10 +170,7 @@ - @@ -153,10 +184,7 @@ - @@ -169,10 +197,7 @@ - @@ -186,10 +211,7 @@ - @@ -203,10 +225,7 @@ - @@ -220,10 +239,7 @@ - @@ -237,10 +253,7 @@ - @@ -253,10 +266,7 @@ - @@ -269,10 +279,7 @@ - @@ -285,10 +292,7 @@ - @@ -301,10 +305,7 @@ - @@ -318,10 +319,7 @@ - @@ -335,10 +333,7 @@ - @@ -352,10 +347,7 @@ - @@ -369,10 +361,7 @@ - @@ -385,10 +374,7 @@ - @@ -401,10 +387,7 @@ - @@ -417,10 +400,7 @@ - @@ -433,10 +413,7 @@ - @@ -449,10 +426,7 @@ - @@ -465,10 +439,7 @@ - @@ -481,10 +452,7 @@ - @@ -498,10 +466,7 @@ - @@ -515,10 +480,7 @@ - @@ -531,10 +493,7 @@ - @@ -544,13 +503,12 @@ - @@ -563,10 +521,7 @@ - @@ -575,10 +530,10 @@
                              Table 2 DCS Redis 3.0 instance metrics

                              Metric ID

                              Metric

                              Value Range

                              Monitored Object and Dimension

                              +

                              Monitored Object

                              Monitoring Period (Raw Data)

                              0–100%

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              0–100%

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              -

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0 kbits/s

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0 kbits/s

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              0–100%

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0 ms

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node or master/standby DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node or master/standby DCS Redis instance

                              1 minute

                              Slow Query Logs

                              Existence of slow query logs in the instance

                              +
                              NOTE:

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

                              +
                              • 1: yes
                              • 0: no

                              Monitored object:

                              -

                              Single-node or master/standby DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node or master/standby DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node or master/standby DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node or master/standby DCS Redis instance

                              1 minute

                              -

                              DCS Redis 4.0 and 5.0 Instance Metrics

                              The Monitored Objects and Dimensions column lists instances and dimensions that support the corresponding metrics.

                              +

                              DCS Redis 4.0/5.0/6.0 Instance Metrics

                              • The Monitored Object column lists instances that support the corresponding metrics.
                              • Dimensions lists the metric dimensions.
                              -
                              Table 2 DCS Redis 4.0 and 5.0 instance metrics

                              Metric ID

                              +
                              @@ -586,7 +541,7 @@ - @@ -601,10 +556,7 @@ - @@ -618,10 +570,7 @@ - @@ -634,10 +583,7 @@ - @@ -647,13 +593,12 @@ - - @@ -667,10 +612,7 @@ - @@ -683,10 +625,7 @@ - @@ -700,10 +639,7 @@ - @@ -717,10 +653,7 @@ - @@ -734,10 +667,7 @@ - @@ -751,10 +681,7 @@ - @@ -768,10 +695,7 @@ - @@ -784,10 +708,7 @@ - @@ -800,10 +721,7 @@ - @@ -816,15 +734,12 @@ - - @@ -833,15 +748,12 @@ - - @@ -850,15 +762,12 @@ - - @@ -867,31 +776,25 @@ - - - - - @@ -900,15 +803,12 @@ - - @@ -917,15 +817,13 @@ - - @@ -934,10 +832,7 @@ - @@ -950,10 +845,7 @@ - @@ -966,10 +858,7 @@ - @@ -983,10 +872,7 @@ - @@ -999,10 +885,7 @@ - @@ -1016,10 +899,7 @@ - @@ -1032,10 +912,7 @@ - @@ -1049,10 +926,7 @@ - @@ -1066,10 +940,7 @@ - @@ -1083,10 +954,7 @@ - @@ -1100,10 +968,7 @@ - @@ -1117,10 +982,7 @@ - @@ -1134,10 +996,7 @@ - @@ -1151,10 +1010,7 @@ - @@ -1168,10 +1024,7 @@ - @@ -1184,10 +1037,7 @@ - @@ -1201,10 +1051,7 @@ - @@ -1218,10 +1065,7 @@ - @@ -1234,10 +1078,7 @@ - @@ -1250,10 +1091,7 @@ - @@ -1267,10 +1105,7 @@ - @@ -1284,10 +1119,7 @@ - @@ -1301,10 +1133,7 @@ - @@ -1318,10 +1147,7 @@ - @@ -1335,10 +1161,7 @@ - @@ -1352,10 +1175,7 @@ - @@ -1368,10 +1188,7 @@ - @@ -1384,10 +1201,7 @@ - @@ -1400,10 +1214,7 @@ - @@ -1416,10 +1227,7 @@ - @@ -1428,11 +1236,11 @@
                              Table 3 DCS Redis 4.0/5.0/6.0 instance metrics

                              Metric ID

                              Metric

                              Value Range

                              Monitored Object and Dimension

                              +

                              Monitored Object

                              Monitoring Period (Raw Data)

                              0–100%

                              Monitored object:

                              -

                              Single-node or master/standby DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node or master/standby DCS Redis instance

                              1 minute

                              ≥ 0 ms

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              Slow Query Logs

                              Existence of slow query logs in the instance

                              +
                              NOTE:

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

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

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              0–100%

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              0–100%

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              0–100%

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              rx_controlled

                              +

                              rx_controlled

                              Flow Control Times

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              bandwidth_usage

                              +

                              bandwidth_usage

                              Bandwidth Usage

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              connections_usage

                              +

                              connections_usage

                              Connection Usage

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              Instance Node Status

                              +

                              Instance Node Status

                              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.

                              -

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              command_max_rt

                              +

                              command_max_rt

                              Maximum Latency

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node DCS Redis instance

                              1 minute

                              command_avg_rt

                              +

                              command_avg_rt

                              Average Latency

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node DCS Redis instance

                              +

                              1 minute

                              cpu_avg_usage

                              +

                              cpu_avg_usage

                              Average CPU Usage

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node or master/standby DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              0–500,000

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              0–500,000

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              0–500,000

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              0–500,000

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              0–500,000

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              0–500,000

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              0–500,000

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              0–500,000

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0 KB/s

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0 KB/s

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              0–500,000

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              0–500,000

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              0–500,000

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              0–500,000

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              0–500,000

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Redis Cluster instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              0–200%

                              Monitored object:

                              -

                              Redis Cluster instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              0–100%

                              Monitored object:

                              -

                              Single-node, master/standby, or cluster DCS Redis instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              +

                              Single-node, master/standby, or cluster DCS Redis instance

                              1 minute

                              -

                              Node Metrics of DCS Redis Instances

                              • The following describes the metrics for cluster DCS instances. For Proxy Cluster DCS Redis 3.0 instances, the monitoring covers Redis Servers and Proxies. For Redis Cluster DCS Redis 4.0 and 5.0 instances, the monitoring only covers Redis Servers. For details, see Table 3 and Table 4.
                              -
                              • The Monitored Objects and Dimensions column lists instances and dimensions that support the corresponding metrics.
                              +

                              Redis Server Metrics of DCS Redis Instances

                              • For Proxy Cluster instances, the monitoring covers Redis Servers and proxies. For Redis Cluster instances, the monitoring covers Redis Servers.
                              +
                              • The Monitored Object column lists instances that support the corresponding metrics.
                              • Dimensions lists the metric dimensions.
                              -
                              Table 3 Redis Server metrics of DCS instances

                              Metric ID

                              +
                              @@ -1440,7 +1248,7 @@ - @@ -1455,11 +1263,8 @@ - @@ -1473,10 +1278,8 @@ - @@ -1489,11 +1292,8 @@ - @@ -1506,11 +1306,7 @@ - @@ -1524,11 +1320,7 @@ - @@ -1541,11 +1333,8 @@ - @@ -1560,11 +1349,8 @@ - @@ -1578,11 +1364,8 @@ - @@ -1596,11 +1379,8 @@ - @@ -1614,11 +1394,8 @@ - @@ -1627,15 +1404,12 @@ - - @@ -1648,11 +1422,8 @@ - @@ -1665,12 +1436,8 @@ - @@ -1683,11 +1450,8 @@ - @@ -1701,12 +1465,8 @@ - @@ -1720,12 +1480,8 @@ - @@ -1739,11 +1495,8 @@ - @@ -1757,11 +1510,8 @@ - @@ -1774,12 +1524,8 @@ - @@ -1792,11 +1538,8 @@ - @@ -1809,11 +1552,8 @@ - @@ -1826,11 +1566,8 @@ - @@ -1843,11 +1580,8 @@ - @@ -1861,11 +1595,8 @@ - @@ -1879,11 +1610,8 @@ - @@ -1893,14 +1621,13 @@ - - @@ -1913,11 +1640,8 @@ - @@ -1926,16 +1650,13 @@ - - @@ -1944,16 +1665,13 @@ - - @@ -1966,11 +1684,7 @@ - @@ -1979,16 +1693,13 @@ - - @@ -1997,16 +1708,13 @@ - - @@ -2015,16 +1723,13 @@ - - @@ -2033,16 +1738,13 @@ - - @@ -2051,16 +1753,13 @@ - - @@ -2069,16 +1768,13 @@ - - @@ -2087,16 +1783,13 @@ - - @@ -2105,16 +1798,13 @@ - - @@ -2123,16 +1813,13 @@ - - @@ -2141,16 +1828,13 @@ - - @@ -2159,16 +1843,13 @@ - - @@ -2182,11 +1863,8 @@ - @@ -2199,11 +1877,8 @@ - @@ -2211,242 +1886,201 @@
                              Table 4 Redis Server metrics

                              Metric ID

                              Metric

                              Value Range

                              Monitored Object and Dimension

                              +

                              Monitored Object

                              Monitoring Period (Raw Data)

                              0–100%

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              0–100%

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              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

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              ≥ 0 KB/s

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              ≥ 0 KB/s

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              0–100%

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              ≥ 0 ms

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              Slow Query Logs

                              Existence of slow query logs in the node

                              +
                              NOTE:

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

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

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              Sadd

                              Number of SADD commands processed per second

                              +

                              Number of SADD commands processed per second

                              Unit: count/s

                              0–500,000

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 3.0, 4.0, or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              Smembers

                              Number of SMEMBERS commands processed per second

                              +

                              Number of SMEMBERS commands processed per second

                              Unit: count/s

                              0–500,000

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 4.0 or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              -

                              Monitored object:

                              -

                              Replica of a cluster DCS Redis 4.0 or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Replica of a cluster DCS Redis 4.0 or 5.0 instance

                              1 minute

                              DEL

                              Number of DEL commands processed per second

                              +

                              Number of DEL commands processed per second

                              Unit: count/s

                              0–500,000

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 4.0 or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              EXPIRE

                              Number of EXPIRE commands processed per second

                              +

                              Number of EXPIRE commands processed per second

                              Unit: count/s

                              0–500,000

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 4.0 or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              GET

                              Number of GET commands processed per second

                              +

                              Number of GET commands processed per second

                              Unit: count/s

                              0–500,000

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 4.0 or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              HDEL

                              Number of HDEL commands processed per second

                              +

                              Number of HDEL commands processed per second

                              Unit: count/s

                              0–500,000

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 4.0 or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              HGET

                              Number of HGET commands processed per second

                              +

                              Number of HGET commands processed per second

                              Unit: count/s

                              0–500,000

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 4.0 or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              HMGET

                              Number of HMGET commands processed per second

                              +

                              Number of HMGET commands processed per second

                              Unit: count/s

                              0–500,000

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 4.0 or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              HMSET

                              Number of HMSET commands processed per second

                              +

                              Number of HMSET commands processed per second

                              Unit: count/s

                              0–500,000

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 4.0 or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              HSET

                              Number of HSET commands processed per second

                              +

                              Number of HSET commands processed per second

                              Unit: count/s

                              0–500,000

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 4.0 or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              MGET

                              Number of MGET commands processed per second

                              +

                              Number of MGET commands processed per second

                              Unit: count/s

                              0–500,000

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 4.0 or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              MSET

                              Number of MSET commands processed per second

                              +

                              Number of MSET commands processed per second

                              Unit: count/s

                              0–500,000

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 4.0 or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              SET

                              Number of SET commands processed per second

                              +

                              Number of SET commands processed per second

                              Unit: count/s

                              0–500,000

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 4.0 or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              ≥ 0

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 4.0 or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute

                              0–200%

                              Monitored object:

                              -

                              Redis Server of a cluster DCS Redis 4.0 or 5.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_redis_node

                              +

                              Redis Server of a cluster DCS instance

                              +

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

                              1 minute
                              + +

                              Proxy Metrics

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

                              Metric ID

                              +
                              - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                              Table 5 Proxy metrics of Proxy Cluster DCS Redis 3.0 instances

                              Metric ID

                              Metric

                              +

                              Metric

                              Description

                              +

                              Description

                              Value Range

                              +

                              Value Range

                              Monitored Object and Dimension

                              +

                              Monitored Object and Dimension

                              Monitoring Period (Raw Data)

                              +

                              Monitoring Period (Raw Data)

                              cpu_usage

                              +

                              cpu_usage

                              CPU Usage

                              +

                              CPU Usage

                              The monitored object's maximum CPU usage among multiple sampling values in a monitoring period

                              +

                              The monitored object's maximum CPU usage among multiple sampling values in a monitoring period

                              Unit: %

                              0–100%

                              +

                              0–100%

                              Monitored object:

                              -

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_proxy_node

                              +

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              1 minute

                              +

                              1 minute

                              memory_usage

                              +

                              memory_usage

                              Memory Usage

                              +

                              Memory Usage

                              Memory consumed by the monitored object

                              +

                              Memory consumed by the monitored object

                              Unit: %

                              0–100%

                              +

                              0–100%

                              Monitored object:

                              -

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_proxy_node

                              +

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              1 minute

                              +

                              1 minute

                              p_connected_clients

                              +

                              p_connected_clients

                              Connected Clients

                              +

                              Connected Clients

                              Number of connected clients

                              +

                              Number of connected clients

                              ≥ 0

                              +

                              ≥ 0

                              Monitored object:

                              -

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_proxy_node

                              +

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              1 minute

                              +

                              1 minute

                              max_rxpck_per_sec

                              +

                              max_rxpck_per_sec

                              Max. NIC Data Packet Receive Rate

                              +

                              Max. NIC Data Packet Receive Rate

                              Maximum number of data packets received by the proxy NIC per second during the monitoring period

                              +

                              Maximum number of data packets received by the proxy NIC per second during the monitoring period

                              Unit: packages/second

                              0–10,000,000

                              +

                              0–10,000,000

                              Monitored object:

                              -

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_proxy_node

                              +

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              1 minute

                              +

                              1 minute

                              max_txpck_per_sec

                              +

                              max_txpck_per_sec

                              Max. NIC Data Packet Transmit Rate

                              +

                              Max. NIC Data Packet Transmit Rate

                              Maximum number of data packets transmitted by the proxy NIC per second during the monitoring period

                              +

                              Maximum number of data packets transmitted by the proxy NIC per second during the monitoring period

                              Unit: packages/second

                              0–10,000,000

                              +

                              0–10,000,000

                              Monitored object:

                              -

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_proxy_node

                              +

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              1 minute

                              +

                              1 minute

                              max_rxkB_per_sec

                              +

                              max_rxkB_per_sec

                              Maximum Inbound Bandwidth

                              +

                              Maximum Inbound Bandwidth

                              Largest volume of data received by the proxy NIC per second

                              +

                              Largest volume of data received by the proxy NIC per second

                              Unit: KB/s

                              ≥ 0 KB/s

                              +

                              ≥ 0 KB/s

                              Monitored object:

                              -

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_proxy_node

                              +

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              1 minute

                              +

                              1 minute

                              max_txkB_per_sec

                              +

                              max_txkB_per_sec

                              Maximum Outbound Bandwidth

                              +

                              Maximum Outbound Bandwidth

                              Largest volume of data transmitted by the proxy NIC per second

                              +

                              Largest volume of data transmitted by the proxy NIC per second

                              Unit: KB/s

                              ≥ 0 KB/s

                              +

                              ≥ 0 KB/s

                              Monitored object:

                              -

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_proxy_node

                              +

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              1 minute

                              +

                              1 minute

                              avg_rxpck_per_sec

                              +

                              avg_rxpck_per_sec

                              Average NIC Data Packet Receive Rate

                              +

                              Average NIC Data Packet Receive Rate

                              Average number of data packets received by the proxy NIC per second during the monitoring period

                              +

                              Average number of data packets received by the proxy NIC per second during the monitoring period

                              Unit: packages/second

                              0–10,000,000

                              +

                              0–10,000,000

                              Monitored object:

                              -

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_proxy_node

                              +

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              1 minute

                              +

                              1 minute

                              avg_txpck_per_sec

                              +

                              avg_txpck_per_sec

                              Average NIC Data Packet Transmit Rate

                              +

                              Average NIC Data Packet Transmit Rate

                              Average number of data packets transmitted by the proxy NIC per second during the monitoring period

                              +

                              Average number of data packets transmitted by the proxy NIC per second during the monitoring period

                              Unit: packages/second

                              0–10,000,000

                              +

                              0–10,000,000

                              Monitored object:

                              -

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_proxy_node

                              +

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              1 minute

                              +

                              1 minute

                              avg_rxkB_per_sec

                              +

                              avg_rxkB_per_sec

                              Average Inbound Bandwidth

                              +

                              Average Inbound Bandwidth

                              Average volume of data received by the proxy NIC per second

                              +

                              Average volume of data received by the proxy NIC per second

                              Unit: KB/s

                              ≥ 0 KB/s

                              +

                              ≥ 0 KB/s

                              Monitored object:

                              -

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_proxy_node

                              +

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              1 minute

                              +

                              1 minute

                              avg_txkB_per_sec

                              +

                              avg_txkB_per_sec

                              Average Outbound Bandwidth

                              +

                              Average Outbound Bandwidth

                              Average volume of data transmitted by the proxy NIC per second

                              +

                              Average volume of data transmitted by the proxy NIC per second

                              Unit: KB/s

                              ≥ 0 KB/s

                              +

                              ≥ 0 KB/s

                              Monitored object:

                              -

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              -

                              Dimension:

                              -

                              dcs_instance_id

                              -

                              dcs_cluster_proxy_node

                              +

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              1 minute

                              +

                              1 minute
                              -

                              Dimensions

                              -

                              Key

                              +

                              Dimensions

                              +
                              - - - - - - - diff --git a/docs/dcs/umn/dcs-ug-0326026.html b/docs/dcs/umn/dcs-ug-0326026.html index d7b212ace..aa22538b3 100644 --- a/docs/dcs/umn/dcs-ug-0326026.html +++ b/docs/dcs/umn/dcs-ug-0326026.html @@ -8,7 +8,19 @@ - + + + + + + @@ -60,19 +72,19 @@ diff --git a/docs/dcs/umn/dcs-ug-0713005.html b/docs/dcs/umn/dcs-ug-0713005.html index ef6639c08..cdb3754b3 100644 --- a/docs/dcs/umn/dcs-ug-0713005.html +++ b/docs/dcs/umn/dcs-ug-0713005.html @@ -1,94 +1,61 @@

                              Jedis

                              -

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

                              -
                              • If a password was set during DCS Redis instance creation, configure the password for connecting to Redis using a Jedis client. Do not hard code the plaintext password.
                              • When using JedisCluster to connect to a Redis Cluster DCS Redis 4.0 or 5.0 instance, the cluster topology is automatically refreshed. The client needs to reconnect to Redis by itself.
                              -
                              -

                              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 Java compilation environment has been installed on the ECS.
                              +

                              Access a DCS Redis instance through Jedis 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.
                              • An ECS has been created. For details about how to create an ECS, see the Elastic Cloud Server User Guide.
                              • If the ECS runs the Linux OS, ensure that the Java compilation environment has been installed on the ECS.
                              -

                              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 where you want to install Docker.
                              3. Use Maven to add the following dependency to the pom.xml file:

                                <dependency>
+
                                Procedure
                                1. View the IP address 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. Use Maven to add the following dependency to the pom.xml file:
                                  <dependency>
     <groupId>redis.clients</groupId>
     <artifactId>jedis</artifactId>
     <version>4.1.1</version>
 </dependency>
                                  
-
                                4. Access the DCS instance by using Jedis.
                                  Obtain the source code of the Jedis client. Use either of the following two methods to access a DCS Redis instance through Jedis:
                                  • Single Jedis connection
                                  • Jedis pool
                                  
+
                                5. Access the DCS instance by using Jedis.
                                  Obtain the source code of the Jedis client. Use either of the following two methods to access a DCS Redis instance through Jedis:
                                  • Single Jedis connection
                                  • Jedis pool
                                  
 
                                  
-
                                  Example code:
                                  
-
                                  1. Example of using Jedis to connect to a single-node, master/standby, or Proxy Cluster DCS Redis instance with a single connection
                                    // Creating a connection in password mode
- String host = "192.168.0.150"; 
- int port = 6379; 
- String pwd = "passwd"; 
+
                                    Example code:
                                    
+
                                    1. Example of using Jedis to connect to a single-node, master/standby, or Proxy Cluster DCS Redis instance with a single connection
                                      //Creating a connection in password mode
+ String host = "192.168.0.150"; 
+ int port = 6379; 
+ String pwd = "passwd"; 
   
  Jedis client = new Jedis(host, port); 
  client.auth(pwd);
  client.connect(); 
-// Run the set command
+//Run the SET command.
  String result = client.set("key-string", "Hello, Redis!"); 
-System.out.println( String.format("set instruction execution result:%s", result) );
-// Run the get command
+ System.out.println( String.format("set command result:%s", result) );
+//Run the GET command.
  String value = client.get("key-string"); 
- System.out.println( String.format("get command result:%s", value) );
+System.out.println( String.format("get command result:%s", value) );
 
-// Creating a connection in password-free mode
- String host = "192.168.0.150"; 
- int port = 6379; 
+//Creating a connection in password-free mode
+ String host = "192.168.0.150"; 
+ int port = 6379; 
   
  Jedis client = new Jedis(host, port); 
  client.connect(); 
-// Run the set command
+//Run the SET command.
  String result = client.set("key-string", "Hello, Redis!"); 
-     System.out.println( String.format("set command result:%s", result) ); 
-// Run the get command
+ System.out.println( String.format("set command result:%s", result) );
+//Run the GET command.
  String value = client.get("key-string"); 
  System.out.println( String.format("get command result:%s", value) );
                                      
-
                                      host indicates the example IP address/domain name of DCS instance and port indicates the port number of DCS instance. For details about how to obtain the IP address/domain name and port, see 1. Change the IP address and port as required. pwd indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.
                                      
-
                                    2. Example of using Jedis to connect to a single-node, master/standby, or Proxy Cluster DCS Redis instance with connection pooling
                                      // Generate configuration information of a Jedis pool
- String ip = "192.168.0.150"; 
- int port = 6379; 
- String pwd = "passwd"; 
- GenericObjectPoolConfig config = new GenericObjectPoolConfig(); 
- config.setTestOnBorrow(false); 
- config.setTestOnReturn(false); 
- config.testWhileIdle(true);
- config.setMaxTotal(100); 
- config.setMaxIdle(100); 
- config.setMaxWaitMillis(2000); 
-JedisPool pool = new JedisPool(config, ip, port, 100000, pwd);//Generate a Jedis pool when the application is being initialized
-// Get a Jedis connection from the Jedis pool when a service operation occurs
- Jedis client = pool.getResource(); 
- try { 
-     // Run commands
-     String result = client.set("key-string", "Hello, Redis!"); 
-     System.out.println( String.format("set command result:%s", result) ); 
-     String value = client.get("key-string"); 
-     System.out.println( String.format("get command result:%s", value) ); 
- } catch (Exception e) { 
-     // TODO: handle exception
- } finally { 
-     // Return the Jedis connection to the Jedis connection pool after the client's request is processed
-     if (null != client) { 
-         pool.returnResource(client); 
-     } 
- } // end of try block
- // Destroy the Jedis pool when the application is closed
- pool.destroy();
-
-// Configure the connection pool in the password-free mode
- String ip = "192.168.0.150"; 
- int port = 6379; 
- GenericObjectPoolConfig config = new GenericObjectPoolConfig(); 
- config.setTestOnBorrow(false); 
- config.setTestOnReturn(false); 
- config.testWhileIdle(true);
+
                                      host indicates the example IP address of the DCS instance and port indicates the port number of the DCS instance. For details about how to obtain the IP address and port, see 1. Change them as required. pwd indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.
                                      
+
                                    3. Example of using Jedis to connect to a single-node, master/standby, or Proxy Cluster DCS Redis instance with connection pooling
                                      //Generate configuration information of a Jedis pool
+ String ip = "192.168.0.150"; 
+ int port = 6379; 
+ String pwd = "passwd"; 
+ GenericObjectPoolConfig config = new GenericObjectPoolConfig(); 
+ config.setTestOnBorrow(false); 
+ config.setTestOnReturn(false); 
  config.setMaxTotal(100); 
  config.setMaxIdle(100); 
  config.setMaxWaitMillis(2000); 
- JedisPool pool = new JedisPool(config, ip, port, 100000);//Generate a JedisPool when the application is being initialized
-// Get a Jedis connection from the Jedis pool when a service operation occurs
+JedisPool pool = new JedisPool(config, ip, port, 100000, pwd);//Generate a Jedis pool when the application is being initialized
+//Get a Jedis connection from the Jedis pool when a service operation occurs
  Jedis client = pool.getResource(); 
  try { 
-     // Run commands
+     //Run commands
      String result = client.set("key-string", "Hello, Redis!"); 
      System.out.println( String.format("set command result:%s", result) ); 
      String value = client.get("key-string"); 
@@ -96,26 +63,54 @@ JedisPool pool = new Jedis
  } catch (Exception e) { 
      // TODO: handle exception
  } finally { 
-     // Return the Jedis connection to the Jedis connection pool after the client's request is processed
+     //Return the Jedis connection to the Jedis pool when the service operation is completed
      if (null != client) { 
          pool.returnResource(client); 
      } 
  } // end of try block
- // Destroy the Jedis pool when the application is closed
+ //Destroy the Jedis pool when the application is closed
+ pool.destroy();
+
+//Configure the connection pool in password-free mode
+ String ip = "192.168.0.150"; 
+ int port = 6379; 
+ GenericObjectPoolConfig config = new GenericObjectPoolConfig(); 
+ config.setTestOnBorrow(false); 
+ config.setTestOnReturn(false); 
+ config.setMaxTotal(100); 
+ config.setMaxIdle(100); 
+ config.setMaxWaitMillis(2000); 
+ JedisPool pool = new JedisPool(config, ip, port, 100000);//Generate a JedisPool when the application is being initialized
+ //Get a Jedis connection from the Jedis pool when a service operation occurs
+ Jedis client = pool.getResource(); 
+ try { 
+     //Run commands
+     String result = client.set("key-string", "Hello, Redis!"); 
+     System.out.println( String.format("set command result:%s", result) ); 
+     String value = client.get("key-string"); 
+     System.out.println( String.format("get command result:%s", value) ); 
+ } catch (Exception e) { 
+     // TODO: handle exception
+ } finally { 
+     //Return the Jedis connection to the Jedis pool when the service operation is completed
+     if (null != client) { 
+         pool.returnResource(client); 
+     } 
+ } // end of try block
+ //Destroy the Jedis pool when the application is closed
  pool.destroy();
                                      
-
                                      ip indicates the IP address/domain name of DCS instance and port indicates the port number of DCS instance. For details about how to obtain the IP address/domain name and port, see 1. Change the IP address and port as required. pwd indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.
                                      
-
                                      Automatic reconnection is supported if the testOnBorrow parameter of the connection pool is enabled. When the service tries to obtain a Redis connection from the connection pool, the connection pool checks connections. After detecting a normal connection, the connection pool provides the connection to the service at the cost of performance. If you require high performance, do not enable this parameter and configure the upper-layer application for it to handle exceptions and retries.
                                      
-
                                    4. Example code for connecting to Redis Cluster using a single connection
                                      • With a password
                                        //The following shows password-protected access.
+
                                        ip indicates the IP address of the DCS instance and port indicates the port number of the DCS instance. For details about how to obtain the IP address and port, see 1. Change them as required. pwd indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.
                                        
+
                                      • Example code for connecting to Redis Cluster using a single connection
                                        • With a password
                                          //The following shows password-protected access.
 int port = 6379;
 String host = "192.168.144.37";
 //Create JedisCluster.
 Set<HostAndPort> nodes = new HashSet<HostAndPort>();
 nodes.add(new HostAndPort(host, port));
-JedisCluster cluster = new JedisCluster(nodes, 5000, 3000, 10, "password", new JedisPoolConfig());
+JedisCluster cluster = new JedisCluster(nodes, 5000, 3000, 10, "password", new JedisPoolConfig());
 cluster.set("key", "value");
 System.out.println("Connected to RedisCluster:" + cluster.get("key"));
 cluster.close();
                                          
-
                                        • Without a password
                                          int port = 6379;
+
                                        • Without a password
                                          int port = 6379;
 String host = "192.168.144.37";
 //Create JedisCluster.
 Set<HostAndPort> nodes = new HashSet<HostAndPort>();
@@ -125,9 +120,9 @@ cluster.set("key", "value");
 System.out.println("Connected to RedisCluster:" + cluster.get("key"));
 cluster.close();
                                          
 
                                        
-
                                        host indicates the example IP address/domain name of DCS instance and port indicates the port number of DCS instance. For details about how to obtain the IP address/domain name and port, see 1. Change the IP address and port 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.
                                        
+
                                        host indicates the example IP address of the DCS instance and port indicates the port number of the DCS instance. For details about how to obtain the IP address and port, see 1. Change them as required. password indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.
                                        
 
                                    
-
                                  2. Compile code according to the readme file in the source code of the Jedis client. Run the Jedis client to access the chosen DCS Redis instance.
                                  
+
                                6. Compile code according to the readme file in the source code of the Jedis client. Run the Jedis client to access the chosen DCS Redis instance.
                              diff --git a/docs/dcs/umn/dcs-ug-0911001.html b/docs/dcs/umn/dcs-ug-0911001.html index 2094b7b45..a15f4a065 100644 --- a/docs/dcs/umn/dcs-ug-0911001.html +++ b/docs/dcs/umn/dcs-ug-0911001.html @@ -7,7 +7,7 @@

                              Prerequisites

                              The DCS instances you want to start are in the Stopped state.

                              -

                              Procedure

                              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 Application > Distributed Cache Service to launch the DCS console.
                              4. In the navigation pane, choose Cache Manager.
                              5. On the Cache Manager page, select one or more DCS instances you want to restart.
                              6. Click Start above the DCS instance list.
                              7. In the Start dialog box, click Yes to confirm that you want to start the instances.

                                • It takes 1 to 30 minutes to start DCS instances.
                                • After DCS instances are started, their statuses change from Stopped to Running.
                                +

                                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. On the Cache Manager page, select one or more DCS instances you want to restart.
                                5. Click Start above the DCS instance list.
                                6. In the Start dialog box, click Yes to confirm that you want to start the instances.

                                  • It takes 1 to 30 minutes to start DCS instances.
                                  • After DCS instances are started, their statuses change from Stopped to Running.

                                  To start a single instance, you can also click Start in the Operation column in the same row as the instance.

                                diff --git a/docs/dcs/umn/dcs-ug-0916002.html b/docs/dcs/umn/dcs-ug-0916002.html index 511a928f8..5adff4f6c 100644 --- a/docs/dcs/umn/dcs-ug-0916002.html +++ b/docs/dcs/umn/dcs-ug-0916002.html @@ -12,7 +12,7 @@
                              8. Access in Different Languages
                                9. -
                              9. Accessing a DCS Redis 4.0 or 5.0 Instance on the Console
                                +
                              10. Accessing a DCS Redis 4.0/5.0/6.0 Instance on the Console
                                11. diff --git a/docs/dcs/umn/dcs-ug-1009001.html b/docs/dcs/umn/dcs-ug-1009001.html index 9c0a67b39..6846ff1aa 100644 --- a/docs/dcs/umn/dcs-ug-1009001.html +++ b/docs/dcs/umn/dcs-ug-1009001.html @@ -2,7 +2,8 @@

                                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.

                                -

                                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.

                                  +

                                  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.

                                diff --git a/docs/dcs/umn/dcs-ug-1009002.html b/docs/dcs/umn/dcs-ug-1009002.html index 7e8822434..a9d391bc4 100644 --- a/docs/dcs/umn/dcs-ug-1009002.html +++ b/docs/dcs/umn/dcs-ug-1009002.html @@ -1,8 +1,8 @@

                                Command Renaming

                                -

                                After creating a DCS Redis 4.0 or 5.0 instance, you can rename the following critical commands: COMMAND, KEYS, FLUSHDB, FLUSHALL, and HGETALL.

                                -

                                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. In the Operation column of an instance, choose More > Command Renaming.
                                5. Select a command, enter a new name, and click OK.

                                  • You can rename multiple commands at a time.
                                  • The new command names will take effect only after you restart the instance. Remember the new command names because they will not be displayed on the console for security purposes.
                                  • To use the original name of a command, rename the command again.
                                  • The new name must contain at least four characters.
                                  +

                                  After creating a DCS Redis 4.0 or later instance, you can rename the following critical commands: Currently, you can only rename the COMMAND, KEYS, FLUSHDB, and FLUSHALL commands.

                                  +

                                  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. In the Operation column of an instance, choose More > Command Renaming.
                                  5. Select a command, enter a new name, and click OK.

                                    • You can rename multiple commands at a time.
                                    • The new command names will take effect only after you restart the instance. Remember the new command names because they will not be displayed on the console for security purposes.
                                    • To use the original name of a command, rename the command again.
                                    • The new name can contain 4 to 64 characters including letters, digits, underscores (_), and hyphens (-), and must start with a letter.

                                  diff --git a/docs/dcs/umn/dcs-ug-190808001.html b/docs/dcs/umn/dcs-ug-190808001.html index 112c6af61..38b1a6b1f 100644 --- a/docs/dcs/umn/dcs-ug-190808001.html +++ b/docs/dcs/umn/dcs-ug-190808001.html @@ -1,19 +1,19 @@ -

                                  Cache Analysis

                                  +

                                  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.

                                  Notes on hot key analysis:

                                  -
                                  • Only DCS Redis 4.0 and 5.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.
                                  +
                                  • 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.

                                  -

                                  Big Key Analysis 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 Redis instance.
                                  5. Click the Cache Analysis tab.
                                  6. On the Big Key Analysis tab page, manually perform big key analysis or schedule daily automatic analysis.
                                  7. After an analysis task completes, click View to view the analysis results.

                                    You can view the analysis results of different data types.

                                    +

                                    Big Key Analysis 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 Redis instance.
                                    5. Choose Analysis and Diagnosis > Cache Analysis.
                                    6. On the Big Key Analysis tab page, manually perform big key analysis or schedule daily automatic analysis.
                                    7. After an analysis task completes, click View to view the analysis results.

                                      You can view the analysis results of different data types.

                                      A maximum of 20 big key analysis records are retained for Strings and 80 are retained for Lists, Sets, Zsets, and Hashes.

                                    -

                                    Hot Key Analysis 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 Redis instance.
                                    5. Click the Cache Analysis tab.
                                    6. On the Hot Key Analysis tab page, manually perform hot key analysis or schedule daily automatic analysis.

                                      The default value of the maxmemory-policy parameter of a Redis 4.0 or 5.0 instance is noeviction. To perform hot key analysis, set this parameter to allkeys-lfu or volatile-lfu. If this parameter has already been set to allkeys-lfu or volatile-lfu, perform hot key analysis right away.

                                      +

                                      Hot Key Analysis 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 Redis instance.
                                      5. Choose Analysis and Diagnosis > Cache Analysis.
                                      6. On the Hot Key Analysis tab page, manually perform hot key analysis or schedule daily automatic analysis.

                                        If hot key analysis cannot be performed, set maxmemory-policy to allkeys-lfu or volatile-lfu. If this parameter has already been set to allkeys-lfu or volatile-lfu, perform hot key analysis right away.

                                      7. After an analysis task completes, click View to view the analysis results.

                                        The hot key analysis results are displayed.

                                        The console displays a maximum of 100 hot key analysis records for each instance.

                                        diff --git a/docs/dcs/umn/dcs-ug-190812001.html b/docs/dcs/umn/dcs-ug-190812001.html index 7aedfc4f2..4ef559f92 100644 --- a/docs/dcs/umn/dcs-ug-190812001.html +++ b/docs/dcs/umn/dcs-ug-190812001.html @@ -2,11 +2,11 @@

                                        Managing IP Address Whitelist

                                        DCS helps you control access to your DCS instances in the following ways, depending on the deployment mode:

                                        -
                                        • To control access to Redis 3.0 instances, you can use security groups. Whitelists are not supported. For details about how to configure a security group, see Security Group Configurations.
                                        • To control access to Redis 4.0 and 5.0 instances, you can use whitelists. Security groups are not supported.
                                        -

                                        The following describes how to manage whitelists of a Redis 4.0 or 5.0 instance to allow access only from whitelisted IP addresses. If no whitelists are added for the instance or the whitelist function is disabled, all IP addresses that can communicate with the VPC can access the instance.

                                        +
                                        • To control access to DCS Redis 3.0 instances, you can use security groups. Whitelists are not supported. For details about how to configure a security group, see Security Group Configurations.
                                        • To control access to DCS Redis 4.0/5.0/6.0 instances, you can use whitelists. Security groups are not supported.
                                        +

                                        The following describes how to manage whitelists of a Redis 4.0/5.0/6.0 instance to allow access only from whitelisted IP addresses. If no whitelists are added for the instance or the whitelist function is disabled, all IP addresses that can communicate with the VPC can access the instance.

                                        Creating a Whitelist Group

                                        1. Log in to the DCS console.
                                        2. Click in the upper left corner of the management console and select a region.

                                          Select the same region as your application service.

                                          -

                                        3. In the navigation pane, choose Cache Manager.
                                        4. Click the name of a DCS instance.
                                        5. Click the Whitelist tab and then click Create Whitelist Group.
                                        6. In the Create Whitelist Group dialogue box, specify Group Name and IP Address/Range.

                                          +

                                        7. In the navigation pane, choose Cache Manager.
                                        8. Click the name of a DCS instance.
                                        9. Choose Instance Configuration > Whitelist and then click Create Whitelist Group.
                                        10. In the Create Whitelist Group dialogue box, specify Group Name and IP Address/Range.

                              Key

                              Value

                              +

                              Value

                              dcs_instance_id

                              +

                              dcs_instance_id

                              DCS Redis instance

                              +

                              DCS Redis instance

                              dcs_cluster_redis_node

                              +

                              dcs_cluster_redis_node

                              Redis Server

                              +

                              Redis Server

                              dcs_cluster_proxy_node

                              +

                              dcs_cluster_proxy_node

                              Proxy

                              +

                              Proxy in a Proxy Cluster DCS Redis 3.0 instance

                              2022-10-19

                              +

                              2023-04-17

                              +

                              Modified the following content:

                              + +

                              2023-01-31

                              +

                              Modified the following content:

                              + +

                              2022-10-19

                              Added the following FAQs:

                              Why Does a Key Disappear in Redis?

                              @@ -16,19 +28,19 @@

                              How Do I View Current Concurrent Connections and Maximum Connections of a DCS Redis Instance?

                              Why Is the Rejected Connections Metric Displayed?

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

                              -

                              Analysis of Big Keys and Hot Keys

                              +

                              Big/Hot Key Analysis

                              2022-08-29

                              Modified the following content:

                              -

                              Added description about security groups and whitelist configuration in sections Creating a DCS Redis Instance, Security Group Configurations, What Should I Do If an Error Is Returned When I Use the Jedis Connection Pool?, How Do I Troubleshoot Redis Connection Failures?, and Why Aren't Security Groups Configured for DCS Redis 4.0 and 5.0 Instances?

                              +

                              Added description about security groups and whitelist configuration in sections Creating a DCS Redis Instance, Security Group Configurations, What Should I Do If an Error Is Returned When I Use the Jedis Connection Pool?, How Do I Troubleshoot Redis Connection Failures?, and Why Aren't Security Groups Configured for DCS Redis 4.0/5.0/6.0 Instances?

                              2022-08-09

                              Modified the following content:

                              - +

                              2022-07-13

                              @@ -47,7 +59,7 @@

                              2021-06-30

                              Modified the following content:

                              -

                              2021-07-13

                              Modified the following content:

                              -

                              Added detailed description about permissions management in sections Permissions Management and Permissions Management.

                              +

                              Added detailed description about permissions management in sections Permissions and Permissions Management.

                              2020-10-13

                              Modified the following content:

                              - +

                              2020-09-30

                              Modified the following content:

                              - +

                              2020-07-17

                              @@ -84,13 +96,13 @@

                              2020-05-30

                              Modified the following content:

                              -
                              • Changed the cluster instance type to Proxy Cluster in section What Is DCS?
                              • Removed description about creating multiple instances in batches and modified password complexity requirements in section Creating a DCS Redis Instance.
                              • Removed the instance topology parameter in section Viewing Details of a DCS Instance.
                              • Changed the default value of the reserved-memory-percent parameter to 0 and added a note clarifying that the configuration parameters supported by single-node and master/standby instances are different in section Modifying Configuration Parameters.
                              • Modified the special characters that the passwords cannot contain in section Changing Instance Passwords.
                              • Removed the section which describes the function of viewing data storage statics of a Proxy Cluster instance.
                              • Added a note clarifying that the backup policy function is not supported by single-node instances in section Configuring a Backup Policy.
                              • Removed Redis Server and Proxy metrics from section Monitoring.
                              +
                              • Changed the cluster instance type to Proxy Cluster in section What Is DCS?
                              • Removed description about creating multiple instances in batches and modified password complexity requirements in section Creating a DCS Redis Instance.
                              • Removed the instance topology parameter in section Viewing Details of a DCS Instance.
                              • Changed the default value of the reserved-memory-percent parameter to 0 and added a note clarifying that the configuration parameters supported by single-node and master/standby instances are different in section Modifying Configuration Parameters.
                              • Modified the special characters that the passwords cannot contain in section Changing Instance Passwords.
                              • Removed the section which describes the function of viewing data storage statics of a Proxy Cluster instance.
                              • Added a note clarifying that the backup policy function is not supported by single-node instances in section Configuring an Automatic Backup Policy.
                              • Removed Redis Server and Proxy metrics from section Monitoring.

                              2020-03-25

                              Modified the following content:

                              - +

                              2019-04-12

                              @@ -121,7 +133,7 @@

                              2017-11-08

                              Added the following content:

                              - +
                              • Added some FAQs in chapter FAQs.
                              Table 1 Whitelist parameters

                              Parameter

                              Description

                              diff --git a/docs/dcs/umn/dcs-ug-190905001.html b/docs/dcs/umn/dcs-ug-190905001.html index 891b9c7d1..51c319590 100644 --- a/docs/dcs/umn/dcs-ug-190905001.html +++ b/docs/dcs/umn/dcs-ug-190905001.html @@ -27,6 +27,7 @@

                              Consider capacity expansion based on the service analysis.

                              The CPU capacity of a single-node or master/standby instance cannot be expanded. If you need larger capacity, use a cluster instance instead.

                              +

                              This metric is available only for single-node, master/standby, and Proxy Cluster instances. For Redis Cluster instances, this metric is available only on the Redis Server level. You can view the metric on the Redis Server tab page on the Performance Monitoring page of the instance.

                              Memory Usage

                              @@ -54,6 +55,7 @@

                              Optimize the connection pool in the service code to prevent the number of connections from exceeding the maximum limit.

                              For single-node and master/standby instances, the maximum number of connections allowed is 10,000. You can adjust the threshold based on service requirements.

                              +

                              Configure this alarm policy on the instance level for single-node and master/standby instances. For cluster instances, configure this alarm policy on the Redis Server and Proxy level.

                              New Connections

                              @@ -68,6 +70,7 @@

                              -

                              Check whether connect is used and whether the client connection is abnormal. Use persistent connections ("pconnect" in Redis terminology) to ensure performance.

                              +

                              Configure this alarm policy on the instance level for single-node and master/standby instances. For cluster instances, configure this alarm policy on the Redis Server and Proxy level.

                              Input Flow

                              @@ -107,7 +110,7 @@

                            • Locate the CPU Usage metric. Hover over the metric and click to create an alarm rule for the metric.

                              The Create Alarm Rule page is displayed.

                            • Specify the alarm rule details.

                              1. Specify the alarm policy and alarm severity.

                                For example, the alarm policy shown in the following figure indicates that an alarm will be triggered if the CPU usage exceeds the threshold for two consecutive periods.

                                Figure 2 Setting the alarm content
                                -
                              2. Set the alarm notification configurations. If you enable Alarm Notification, set the validity period, notification object, and trigger condition.
                              3. Click Create.

                                For more information about creating alarm rules, see the Cloud Eye User Guide > Using the Alarm Function > Creating Alarm Rules.

                                +
                              4. Set the alarm notification configurations. If you enable Alarm Notification, set the validity period, notification object, and trigger condition.
                              5. Click Create.
                                • For more information about creating alarm rules, see the Cloud Eye User Guide > Using the Alarm Function > Creating Alarm Rules.
                                • For details about how to modify or disable the created alarms, see "Using the Alarm Function" > "Alarm Rule Management" in the Cloud Eye User Guide.

                              • diff --git a/docs/dcs/umn/dcs-ug-190926001.html b/docs/dcs/umn/dcs-ug-190926001.html index c44ddd241..a3ef2ed25 100644 --- a/docs/dcs/umn/dcs-ug-190926001.html +++ b/docs/dcs/umn/dcs-ug-190926001.html @@ -1,14 +1,14 @@ -

                              Viewing Redis Slow Logs

                              +

                              Viewing Redis Slow Queries

                              Redis logs queries that exceed a specified execution time. You can view the slow query log on the DCS console to identify performance issues.

                              For details about the commands, visit the Redis official website.

                              Configure the slow log with the following parameters:

                              -
                              • slowlog-log-slower-than: The maximum time allowed, in microseconds, for command execution. If this threshold is exceeded, Redis will log the command. The default value is 10,000. That is, if command execution exceeds 10 ms, the command will be logged.
                              • slowlog-max-len: The maximum allowed number of slow logs that can be logged. The default value is 128. That is, if the number of slow logs exceeds 128, the earliest record will be deleted to make room for new ones.
                              +
                              • slowlog-log-slower-than: The maximum time allowed, in microseconds, for command execution. If this threshold is exceeded, Redis will log the command. The default value is 10,000. That is, if command execution exceeds 10 ms, the command will be logged.
                              • slowlog-max-len: The maximum allowed number of slow queries that can be logged. The default value is 128. That is, if the number of slow queries exceeds 128, the earliest record will be deleted to make room for new ones.

                              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 Logs 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 Slow Log.
                              6. Select a start date and an end date to view the slow log 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.

                                  Figure 1 Slow query log of an instance

                                diff --git a/docs/dcs/umn/dcs-ug-210107001.html b/docs/dcs/umn/dcs-ug-210107001.html index 136d6a4a3..f9eca37c2 100644 --- a/docs/dcs/umn/dcs-ug-210107001.html +++ b/docs/dcs/umn/dcs-ug-210107001.html @@ -1,12 +1,14 @@

                                Managing Shards and Replicas

                                -

                                This section describes how to query the shards and replicas of a DCS Redis 4.0 or 5.0 instance and how to manually promote a replica to master.

                                +

                                This section describes how to query the shards and replicas of a DCS Redis 4.0/5.0/6.0 instance and how to manually promote a replica to master.

                                Currently, this function is supported only by Redis Cluster DCS Redis 4.0 or 5.0 instances.

                                • A Redis Cluster instance has multiple shards. Each shard has one master and one replica by default. On the Shards and Replicas page, you can view the sharding information and manually switch the master and replica roles. For details about the number of shards corresponding to different instance specifications, see Redis Cluster.

                                Promoting a Replica to Master

                                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. The Cache Manager page is displayed.
                                1. Click an instance.
                                2. Click the Shards and Replicas tab.

                                  The page displays all shards in the instance and the list of replicas of each shard.

                                3. Click to show all replicas of a shard.

                                  Figure 1 Lists of shards and replicas
                                  -

                                4. Click Promote to Master in the row containing another replica which is in the "Replica" role.
                                5. Click Yes.
                                +
                                • For a cluster instance, you can promote a replica in a shard to be master.
                                  1. Click Promote to Master in the row containing another replica which is in the "Replica" role.
                                  2. Click Yes.
                                  +
                                +

                              diff --git a/docs/dcs/umn/dcs-ug-210226001.html b/docs/dcs/umn/dcs-ug-210226001.html index 9f6d273e7..97fb2aff8 100644 --- a/docs/dcs/umn/dcs-ug-210226001.html +++ b/docs/dcs/umn/dcs-ug-210226001.html @@ -1,18 +1,17 @@

                              Importing Backup Files from Redis

                              -

                              Scenario

                              Use the DCS console to migrate Redis data from self-hosted Redis to DCS for Redis.

                              -

                              Simply back up your Redis data, create a migration task on the DCS console, and then import the backup to a DCS Redis instance.

                              +

                              Scenario

                              Use the DCS console to migrate Redis data from self-hosted Redis to DCS for Redis.

                              +

                              Simply back up your Redis data, create a migration task on the DCS console, and then import the backup to a DCS Redis instance.

                              -

                              Prerequisites

                              A master/standby or cluster DCS Redis instance has been created as the target for the migration. The source instance has data and has been backed up.

                              +

                              Prerequisites

                              A master/standby or cluster DCS Redis instance has been created as the target for the migration. The source instance has data and has been backed up.

                              Step 1: Obtain the Source Instance Name and Password

                              Obtain the name of the source Redis instance.

                              -

                              Step 2: 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 must clear the instance data before the migration.
                                • If the target instance is Redis 4.0 or 5.0, 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.
                                +

                                Step 2: 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.
                                -

                                You can use a DCS Redis 3.0, 4.0, or 5.0 instance as the target instance.

                                -

                                Step 3: Create a Migration Task

                                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 Data Migration.
                                4. Click Create Backup Import Task.
                                5. Enter the task name and description.
                                6. Set Data Source to Redis.
                                7. For source Redis, select the instance prepared in Step 1: Obtain the Source Instance Name and Password.
                                8. Select the backup task whose data is to be migrated.
                                9. Select the target instance created in Step 2: Prepare the Target DCS Redis Instance.
                                10. Enter the password of the target instance. Click Test Connection to verify the password.
                                11. Click Next.
                                12. Confirm the migration task details and click Submit.

                                  Go back to the data migration task list. After the migration is successful, the task status changes to Successful.

                                  +

                                  Step 3: Create a Migration Task

                                  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 Data Migration.
                                  4. Click Create Backup Import Task.
                                  5. Enter the task name and description.
                                  6. Set Data Source to Redis.
                                  7. For source Redis, select the instance prepared in Step 1: Obtain the Source Instance Name and Password.
                                  8. Select the backup task whose data is to be migrated.
                                  9. Select the target instance created in Step 2: Prepare the Target DCS Redis Instance.
                                  10. Enter the password of the target instance. Click Test Connection to verify the password.
                                  11. Click Next.
                                  12. Confirm the migration task details and click Submit.

                                    Go back to the data migration task list. After the migration is successful, the task status changes to Successful.

                                diff --git a/docs/dcs/umn/dcs-ug-210622001.html b/docs/dcs/umn/dcs-ug-210622001.html new file mode 100644 index 000000000..f653be60c --- /dev/null +++ b/docs/dcs/umn/dcs-ug-210622001.html @@ -0,0 +1,17 @@ + + +

                                Parameter Templates

                                +
                                + + diff --git a/docs/dcs/umn/dcs-ug-210622002.html b/docs/dcs/umn/dcs-ug-210622002.html new file mode 100644 index 000000000..25ac9ed0a --- /dev/null +++ b/docs/dcs/umn/dcs-ug-210622002.html @@ -0,0 +1,273 @@ + + +

                                Viewing Parameter Templates

                                +

                                This section describes how to view parameter templates on the DCS console.

                                +

                                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 Parameter Templates.
                                4. Choose the Default Templates or Custom Templates tab.
                                5. View parameter templates.

                                  Currently, you can enter a keyword in the search box to search for a parameter template by template name.

                                  +

                                6. Click a parameter template. The parameters contained in the template are displayed. For details about the parameters, see Table 1.

                                  +

                                  + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                  Table 1 DCS Redis instance configuration parameters

                                  Parameter

                                  +

                                  Description

                                  +

                                  Value Range

                                  +

                                  Default Value

                                  +

                                  timeout

                                  +

                                  The maximum amount of time (in seconds) a connection between a client and the DCS instance can be allowed to remain idle before the connection is terminated. A setting of 0 means that this function is disabled.

                                  +

                                  Proxy Cluster instances do not have this parameter.

                                  +

                                  0–7200 seconds

                                  +

                                  0

                                  +

                                  appendfsync

                                  +

                                  Controls how often fsync() transfers cached data to the disk. Note that some OSs will perform a complete data transfer but some others only make a "best-effort" attempt. Single-node instances do not have this parameter.

                                  +

                                  There are three settings:

                                  +

                                  no: fsync() is never called. The OS will flush data when it is ready. This mode offers the highest performance.

                                  +

                                  always: fsync() is called after every write to the AOF. This mode is very slow, but also very safe.

                                  +

                                  everysec: fsync() is called once per second. This mode provides a compromise between safety and performance.

                                  +
                                  • no
                                  • always
                                  • everysec
                                  +

                                  no

                                  +

                                  appendonly

                                  +

                                  Indicates whether to log each modification of the instance. By default, data is written to disks asynchronously in Redis. If this function is disabled, recently-generated data might be lost in the event of a power failure. Options:

                                  +

                                  yes: enabled

                                  +

                                  no: disabled

                                  +
                                  • yes
                                  • no
                                  +

                                  yes

                                  +

                                  client-output-buffer-limit-slave-soft-seconds

                                  +

                                  Number of seconds that the output buffer remains above client-output-buffer-slave-soft-limit before the client is disconnected.

                                  +

                                  0–60

                                  +

                                  60

                                  +

                                  client-output-buffer-slave-hard-limit

                                  +

                                  Hard limit (in bytes) on the output buffer of replica clients. Once the output buffer exceeds the hard limit, the client is immediately disconnected.

                                  +

                                  Depends on the instance type and specifications.

                                  +

                                  +

                                  Depends on the instance type and specifications.

                                  +

                                  client-output-buffer-slave-soft-limit

                                  +

                                  Soft limit (in bytes) on the output buffer of replica clients. Once the output buffer exceeds the soft limit and continuously remains above the limit for the time specified by the client-output-buffer-limit-slave-soft-seconds parameter, the client is disconnected.

                                  +

                                  Depends on the instance type and specifications.

                                  +

                                  +

                                  Depends on the instance type and specifications.

                                  +

                                  maxmemory-policy

                                  +

                                  The deletion policy to apply when the maxmemory limit is reached. Options:

                                  +

                                  volatile-lru: Evict keys by trying to remove the less recently used (LRU) keys first, but only among keys that have an expire set. (Recommended)

                                  +

                                  allkeys-lru: Evict keys by trying to remove the LRU keys first.

                                  +

                                  volatile-random: evict keys randomly, but only evict keys with an expire set.

                                  +

                                  allkeys-random: Evict keys randomly.

                                  +

                                  volatile-ttl: Evict keys with an expire set, and try to evict keys with a shorter time to live (TTL) first.

                                  +

                                  noeviction: Do not delete any keys and only return errors when the memory limit was reached.

                                  +

                                  volatile-lfu: Evict keys by trying to remove the less frequently used (LFU) keys first, but only among keys that have an expire set.

                                  +

                                  allkeys-lfu: Evict keys by trying to remove the LFU keys first.

                                  +

                                  Depends on the instance version.

                                  +

                                  Depends on the instance version and type.

                                  +

                                  lua-time-limit

                                  +

                                  Maximum time allowed for executing a Lua script (in milliseconds).

                                  +

                                  100–5000

                                  +

                                  5,000

                                  +

                                  master-read-only

                                  +

                                  Sets the instance to be read-only. All write operations will fail.

                                  +

                                  Proxy Cluster instances do not have this parameter.

                                  +
                                  • yes
                                  • no
                                  +

                                  no

                                  +

                                  maxclients

                                  +

                                  The maximum number of clients allowed to be concurrently connected to a DCS instance.

                                  +

                                  Proxy Cluster instances do not have this parameter.

                                  +

                                  Depends on the instance type and specifications.

                                  +

                                  Depends on the instance type and specifications.

                                  +

                                  proto-max-bulk-len

                                  +

                                  Maximum size of a single element request (in bytes).

                                  +

                                  1,048,576–536,870,912

                                  +

                                  536,870,912

                                  +

                                  repl-backlog-size

                                  +

                                  The replication backlog size (bytes). The backlog is a buffer that accumulates replica data when replicas are disconnected from the master. When a replica reconnects, a partial synchronization is performed to synchronize the data that was missed while replicas were disconnected.

                                  +

                                  16,384–1,073,741,824

                                  +

                                  1,048,576

                                  +

                                  repl-backlog-ttl

                                  +

                                  The amount of time, in seconds, before the backlog buffer is released, starting from the last a replica was disconnected. The value 0 indicates that the backlog is never released.

                                  +

                                  0–604,800

                                  +

                                  3,600

                                  +

                                  repl-timeout

                                  +

                                  Replication timeout (in seconds).

                                  +

                                  30–3,600

                                  +

                                  60

                                  +

                                  hash-max-ziplist-entries

                                  +

                                  Hashes are encoded using a memory efficient data structure when the number of entries in hashes is less than the value of this parameter.

                                  +

                                  1–10,000

                                  +

                                  512

                                  +

                                  hash-max-ziplist-value

                                  +

                                  Hashes are encoded using a memory efficient data structure when the biggest entry in hashes does not exceed the length threshold indicated by this parameter.

                                  +

                                  1–10,000

                                  +

                                  64

                                  +

                                  set-max-intset-entries

                                  +

                                  When a set is composed of just strings that happen to be integers in radix 10 in the range of 64 bit signed integers, sets are encoded using a memory efficient data structure.

                                  +

                                  1–10,000

                                  +

                                  512

                                  +

                                  zset-max-ziplist-entries

                                  +

                                  Sorted sets are encoded using a memory efficient data structure when the number of entries in sorted sets is less than the value of this parameter.

                                  +

                                  1–10,000

                                  +

                                  128

                                  +

                                  zset-max-ziplist-value

                                  +

                                  Sorted sets are encoded using a memory efficient data structure when the biggest entry in sorted sets does not exceed the length threshold indicated by this parameter.

                                  +

                                  1–10,000

                                  +

                                  64

                                  +

                                  latency-monitor-threshold

                                  +

                                  Threshold time in latency monitoring. Unit: millisecond.

                                  +

                                  Set to 0: Latency monitoring is disabled.

                                  +

                                  Set to more than 0: All with at least this many milliseconds of latency will be logged.

                                  +

                                  By running the LATENCY command, you can perform operations related to latency monitoring, such as obtaining statistical data, and configuring and enabling latency monitoring.

                                  +

                                  0–86,400,000 ms

                                  +

                                  0

                                  +

                                  notify-keyspace-events

                                  +

                                  Controls which keyspace events notifications are enabled for. If the value is an empty string, this function is disabled. A combination of different values can be used to enable notifications for multiple event types. Possible values:

                                  +

                                  K: Keyspace events, published with the __keyspace@__ prefix.

                                  +

                                  E: Keyevent events, published with __keyevent@__ prefix

                                  +

                                  g: Generic commands (non-type specific) such as DEL, EXPIRE, and RENAME

                                  +

                                  $: String commands

                                  +

                                  l: List commands

                                  +

                                  s: Set commands

                                  +

                                  h: Hash commands

                                  +

                                  z: Sorted set commands

                                  +

                                  x: Expired events (events generated every time a key expires)

                                  +

                                  e: Evicted events (events generated when a key is evicted for maxmemory)

                                  +

                                  A: an alias for "g$lshzxe"

                                  +

                                  The parameter value must contain either K or E. A cannot be used together with any of the characters in "g$lshzxe". For example, the value Kl means that Redis will notify Pub/Sub clients about keyspace events and list commands. The value AKE means Redis will notify Pub/Sub clients about all events.

                                  +

                                  Proxy Cluster instances do not have this parameter.

                                  +

                                  See the parameter description.

                                  +

                                  Ex

                                  +

                                  slowlog-log-slower-than

                                  +

                                  Redis records queries that exceed a specified execution time.

                                  +

                                  slowlog-log-slower-than is the maximum time allowed, in microseconds, for command execution. If this threshold is exceeded, Redis will record the query.

                                  +

                                  0–1,000,000

                                  +

                                  10,000

                                  +

                                  slowlog-max-len

                                  +

                                  The maximum allowed number of slow queries that can be logged. Slow query log consumes memory, but you can reclaim this memory by running the SLOWLOG RESET command.

                                  +

                                  0–1000

                                  +

                                  128

                                  +
                                  +
                                  +
                                  1. The default values and value ranges of the maxclients, reserved-memory-percent, client-output-buffer-slave-soft-limit, and client-output-buffer-slave-hard-limit parameters are related to the instance specifications. Therefore, these parameters are not displayed in the parameter template.
                                  2. For more information about the parameters described in Table 1, visit https://redis.io/topics/memory-optimization.
                                  +
                                  +

                                +
                                +
                                +
                                +
                                +
                                Parent topic: Parameter Templates
                                +
                                +
                                + diff --git a/docs/dcs/umn/dcs-ug-210622003.html b/docs/dcs/umn/dcs-ug-210622003.html new file mode 100644 index 000000000..0308f8806 --- /dev/null +++ b/docs/dcs/umn/dcs-ug-210622003.html @@ -0,0 +1,278 @@ + + +

                                Creating a Custom Parameter Template

                                +

                                You can create custom parameter templates for different cache engine versions and instance types based on service requirements.

                                +

                                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 Parameter Templates.
                                4. Click the Default Templates or Custom Templates tab to create a template based on a default template or an existing custom template.

                                  • If you select Default Templates, click Customize in the Operation column of the row containing the desired cache engine version.
                                  • If you select Custom Templates, click Copy in the Operation column in the row containing the desired custom template.
                                  +

                                5. Specify Template Name and Description.

                                  The template name can contain 4 to 64 characters and must start with a letter or digit. Only letters, digits, hyphens (-), underscores (_), and periods (.) are allowed. The description can be empty.

                                  +
                                  +

                                6. Select Modifiable parameters.

                                  Currently, you can enter a keyword in the search box to search for a parameter by parameter name.

                                  +

                                7. In the row that contains the parameter to be modified, enter a value in the Assigned Value column.

                                  Table 1 describes the parameters. In most cases, default values are retained.

                                  + +
                                  + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                  Table 1 DCS Redis instance configuration parameters

                                  Parameter

                                  +

                                  Description

                                  +

                                  Value Range

                                  +

                                  Default Value

                                  +

                                  timeout

                                  +

                                  The maximum amount of time (in seconds) a connection between a client and the DCS instance can be allowed to remain idle before the connection is terminated. A setting of 0 means that this function is disabled.

                                  +

                                  Proxy Cluster instances do not have this parameter.

                                  +

                                  0–7200 seconds

                                  +

                                  0

                                  +

                                  appendfsync

                                  +

                                  Controls how often fsync() transfers cached data to the disk. Note that some OSs will perform a complete data transfer but some others only make a "best-effort" attempt. Single-node instances do not have this parameter.

                                  +

                                  There are three settings:

                                  +

                                  no: fsync() is never called. The OS will flush data when it is ready. This mode offers the highest performance.

                                  +

                                  always: fsync() is called after every write to the AOF. This mode is very slow, but also very safe.

                                  +

                                  everysec: fsync() is called once per second. This mode provides a compromise between safety and performance.

                                  +
                                  • no
                                  • always
                                  • everysec
                                  +

                                  no

                                  +

                                  appendonly

                                  +

                                  Indicates whether to log each modification of the instance. By default, data is written to disks asynchronously in Redis. If this function is disabled, recently-generated data might be lost in the event of a power failure. Options:

                                  +

                                  yes: enabled

                                  +

                                  no: disabled

                                  +
                                  • yes
                                  • no
                                  +

                                  yes

                                  +

                                  client-output-buffer-limit-slave-soft-seconds

                                  +

                                  Number of seconds that the output buffer remains above client-output-buffer-slave-soft-limit before the client is disconnected.

                                  +

                                  0–60

                                  +

                                  60

                                  +

                                  client-output-buffer-slave-hard-limit

                                  +

                                  Hard limit (in bytes) on the output buffer of replica clients. Once the output buffer exceeds the hard limit, the client is immediately disconnected.

                                  +

                                  Depends on the instance type and specifications.

                                  +

                                  +

                                  Depends on the instance type and specifications.

                                  +

                                  client-output-buffer-slave-soft-limit

                                  +

                                  Soft limit (in bytes) on the output buffer of replica clients. Once the output buffer exceeds the soft limit and continuously remains above the limit for the time specified by the client-output-buffer-limit-slave-soft-seconds parameter, the client is disconnected.

                                  +

                                  Depends on the instance type and specifications.

                                  +

                                  +

                                  Depends on the instance type and specifications.

                                  +

                                  maxmemory-policy

                                  +

                                  The deletion policy to apply when the maxmemory limit is reached. Options:

                                  +

                                  volatile-lru: Evict keys by trying to remove the less recently used (LRU) keys first, but only among keys that have an expire set. (Recommended)

                                  +

                                  allkeys-lru: Evict keys by trying to remove the LRU keys first.

                                  +

                                  volatile-random: evict keys randomly, but only evict keys with an expire set.

                                  +

                                  allkeys-random: Evict keys randomly.

                                  +

                                  volatile-ttl: Evict keys with an expire set, and try to evict keys with a shorter time to live (TTL) first.

                                  +

                                  noeviction: Do not delete any keys and only return errors when the memory limit was reached.

                                  +

                                  volatile-lfu: Evict keys by trying to remove the less frequently used (LFU) keys first, but only among keys that have an expire set.

                                  +

                                  allkeys-lfu: Evict keys by trying to remove the LFU keys first.

                                  +

                                  Depends on the instance version.

                                  +

                                  Depends on the instance version and type.

                                  +

                                  lua-time-limit

                                  +

                                  Maximum time allowed for executing a Lua script (in milliseconds).

                                  +

                                  100–5000

                                  +

                                  5,000

                                  +

                                  master-read-only

                                  +

                                  Sets the instance to be read-only. All write operations will fail.

                                  +

                                  Proxy Cluster instances do not have this parameter.

                                  +
                                  • yes
                                  • no
                                  +

                                  no

                                  +

                                  maxclients

                                  +

                                  The maximum number of clients allowed to be concurrently connected to a DCS instance.

                                  +

                                  Proxy Cluster instances do not have this parameter.

                                  +

                                  Depends on the instance type and specifications.

                                  +

                                  Depends on the instance type and specifications.

                                  +

                                  proto-max-bulk-len

                                  +

                                  Maximum size of a single element request (in bytes).

                                  +

                                  1,048,576–536,870,912

                                  +

                                  536,870,912

                                  +

                                  repl-backlog-size

                                  +

                                  The replication backlog size (bytes). The backlog is a buffer that accumulates replica data when replicas are disconnected from the master. When a replica reconnects, a partial synchronization is performed to synchronize the data that was missed while replicas were disconnected.

                                  +

                                  16,384–1,073,741,824

                                  +

                                  1,048,576

                                  +

                                  repl-backlog-ttl

                                  +

                                  The amount of time, in seconds, before the backlog buffer is released, starting from the last a replica was disconnected. The value 0 indicates that the backlog is never released.

                                  +

                                  0–604,800

                                  +

                                  3,600

                                  +

                                  repl-timeout

                                  +

                                  Replication timeout (in seconds).

                                  +

                                  30–3,600

                                  +

                                  60

                                  +

                                  hash-max-ziplist-entries

                                  +

                                  Hashes are encoded using a memory efficient data structure when the number of entries in hashes is less than the value of this parameter.

                                  +

                                  1–10,000

                                  +

                                  512

                                  +

                                  hash-max-ziplist-value

                                  +

                                  Hashes are encoded using a memory efficient data structure when the biggest entry in hashes does not exceed the length threshold indicated by this parameter.

                                  +

                                  1–10,000

                                  +

                                  64

                                  +

                                  set-max-intset-entries

                                  +

                                  When a set is composed of just strings that happen to be integers in radix 10 in the range of 64 bit signed integers, sets are encoded using a memory efficient data structure.

                                  +

                                  1–10,000

                                  +

                                  512

                                  +

                                  zset-max-ziplist-entries

                                  +

                                  Sorted sets are encoded using a memory efficient data structure when the number of entries in sorted sets is less than the value of this parameter.

                                  +

                                  1–10,000

                                  +

                                  128

                                  +

                                  zset-max-ziplist-value

                                  +

                                  Sorted sets are encoded using a memory efficient data structure when the biggest entry in sorted sets does not exceed the length threshold indicated by this parameter.

                                  +

                                  1–10,000

                                  +

                                  64

                                  +

                                  latency-monitor-threshold

                                  +

                                  Threshold time in latency monitoring. Unit: millisecond.

                                  +

                                  Set to 0: Latency monitoring is disabled.

                                  +

                                  Set to more than 0: All with at least this many milliseconds of latency will be logged.

                                  +

                                  By running the LATENCY command, you can perform operations related to latency monitoring, such as obtaining statistical data, and configuring and enabling latency monitoring.

                                  +

                                  0–86,400,000 ms

                                  +

                                  0

                                  +

                                  notify-keyspace-events

                                  +

                                  Controls which keyspace events notifications are enabled for. If the value is an empty string, this function is disabled. A combination of different values can be used to enable notifications for multiple event types. Possible values:

                                  +

                                  K: Keyspace events, published with the __keyspace@__ prefix.

                                  +

                                  E: Keyevent events, published with __keyevent@__ prefix

                                  +

                                  g: Generic commands (non-type specific) such as DEL, EXPIRE, and RENAME

                                  +

                                  $: String commands

                                  +

                                  l: List commands

                                  +

                                  s: Set commands

                                  +

                                  h: Hash commands

                                  +

                                  z: Sorted set commands

                                  +

                                  x: Expired events (events generated every time a key expires)

                                  +

                                  e: Evicted events (events generated when a key is evicted for maxmemory)

                                  +

                                  A: an alias for "g$lshzxe"

                                  +

                                  The parameter value must contain either K or E. A cannot be used together with any of the characters in "g$lshzxe". For example, the value Kl means that Redis will notify Pub/Sub clients about keyspace events and list commands. The value AKE means Redis will notify Pub/Sub clients about all events.

                                  +

                                  Proxy Cluster instances do not have this parameter.

                                  +

                                  See the parameter description.

                                  +

                                  Ex

                                  +

                                  slowlog-log-slower-than

                                  +

                                  Redis records queries that exceed a specified execution time.

                                  +

                                  slowlog-log-slower-than is the maximum time allowed, in microseconds, for command execution. If this threshold is exceeded, Redis will record the query.

                                  +

                                  0–1,000,000

                                  +

                                  10,000

                                  +

                                  slowlog-max-len

                                  +

                                  The maximum allowed number of slow queries that can be logged. Slow query log consumes memory, but you can reclaim this memory by running the SLOWLOG RESET command.

                                  +

                                  0–1000

                                  +

                                  128

                                  +
                                  +
                                  +
                                  1. The default values and value ranges of the maxclients, reserved-memory-percent, client-output-buffer-slave-soft-limit, and client-output-buffer-slave-hard-limit parameters are related to the instance specifications. Therefore, these parameters cannot be modified.
                                  2. For more information about the parameters described in Table 1, visit https://redis.io/topics/memory-optimization.
                                  3. The latency-monitor-threshold parameter is usually used for fault location. After locating faults based on the latency information collected, change the value of latency-monitor-threshold to 0 to avoid unnecessary latency.
                                  4. More about the notify-keyspace-events parameter:
                                    • The parameter setting must contain at least a K or E.
                                    • A is an alias for "g$lshzxe" and cannot be used together with any of the characters in "g$lshzxe".
                                    • For example, the value Kl means that Redis will notify Pub/Sub clients about keyspace events and list commands. The value AKE means Redis will notify Pub/Sub clients about all events.
                                    +
                                  +
                                  +

                                8. Click OK.
                                +
                                +
                                +
                                +
                                +
                                Parent topic: Parameter Templates
                                +
                                +
                                + diff --git a/docs/dcs/umn/dcs-ug-210622004.html b/docs/dcs/umn/dcs-ug-210622004.html new file mode 100644 index 000000000..a87c426e8 --- /dev/null +++ b/docs/dcs/umn/dcs-ug-210622004.html @@ -0,0 +1,276 @@ + + +

                                Modifying a Custom Parameter Template

                                +

                                You can modify the name, description, and parameters of a custom parameter template based on service requirements.

                                +

                                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 Parameter Templates.
                                4. Choose the Custom Templates tab.
                                5. You can modify a custom parameter template in either of the following ways:

                                  • Click Edit in the Operation column.
                                    1. Change the name or modify the description of a template.
                                    2. In the Parameters area, select Modifiable parameters. In the row that contains the parameter to be modified, enter a value in the Assigned Value column. Table 1 describes the parameters. In most cases, default values are retained.
                                    3. Click OK.
                                    +
                                  • Click the name of a custom template. On the displayed page, modify parameters.
                                    1. Select Modifiable parameters. Enter a keyword in the search box to search for a parameter by parameter name.
                                    2. Click Modify.
                                    3. In the row that contains the parameter to be modified, enter a value in the Assigned Value column. Table 1 describes the parameters. In most cases, default values are retained.
                                    4. Click Save.
                                    +
                                  + +
                                  + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                  Table 1 DCS Redis instance configuration parameters

                                  Parameter

                                  +

                                  Description

                                  +

                                  Value Range

                                  +

                                  Default Value

                                  +

                                  timeout

                                  +

                                  The maximum amount of time (in seconds) a connection between a client and the DCS instance can be allowed to remain idle before the connection is terminated. A setting of 0 means that this function is disabled.

                                  +

                                  Proxy Cluster instances do not have this parameter.

                                  +

                                  0–7200 seconds

                                  +

                                  0

                                  +

                                  appendfsync

                                  +

                                  Controls how often fsync() transfers cached data to the disk. Note that some OSs will perform a complete data transfer but some others only make a "best-effort" attempt. Single-node instances do not have this parameter.

                                  +

                                  There are three settings:

                                  +

                                  no: fsync() is never called. The OS will flush data when it is ready. This mode offers the highest performance.

                                  +

                                  always: fsync() is called after every write to the AOF. This mode is very slow, but also very safe.

                                  +

                                  everysec: fsync() is called once per second. This mode provides a compromise between safety and performance.

                                  +
                                  • no
                                  • always
                                  • everysec
                                  +

                                  no

                                  +

                                  appendonly

                                  +

                                  Indicates whether to log each modification of the instance. By default, data is written to disks asynchronously in Redis. If this function is disabled, recently-generated data might be lost in the event of a power failure. Options:

                                  +

                                  yes: enabled

                                  +

                                  no: disabled

                                  +
                                  • yes
                                  • no
                                  +

                                  yes

                                  +

                                  client-output-buffer-limit-slave-soft-seconds

                                  +

                                  Number of seconds that the output buffer remains above client-output-buffer-slave-soft-limit before the client is disconnected.

                                  +

                                  0–60

                                  +

                                  60

                                  +

                                  client-output-buffer-slave-hard-limit

                                  +

                                  Hard limit (in bytes) on the output buffer of replica clients. Once the output buffer exceeds the hard limit, the client is immediately disconnected.

                                  +

                                  Depends on the instance type and specifications.

                                  +

                                  +

                                  Depends on the instance type and specifications.

                                  +

                                  client-output-buffer-slave-soft-limit

                                  +

                                  Soft limit (in bytes) on the output buffer of replica clients. Once the output buffer exceeds the soft limit and continuously remains above the limit for the time specified by the client-output-buffer-limit-slave-soft-seconds parameter, the client is disconnected.

                                  +

                                  Depends on the instance type and specifications.

                                  +

                                  +

                                  Depends on the instance type and specifications.

                                  +

                                  maxmemory-policy

                                  +

                                  The deletion policy to apply when the maxmemory limit is reached. Options:

                                  +

                                  volatile-lru: Evict keys by trying to remove the less recently used (LRU) keys first, but only among keys that have an expire set. (Recommended)

                                  +

                                  allkeys-lru: Evict keys by trying to remove the LRU keys first.

                                  +

                                  volatile-random: evict keys randomly, but only evict keys with an expire set.

                                  +

                                  allkeys-random: Evict keys randomly.

                                  +

                                  volatile-ttl: Evict keys with an expire set, and try to evict keys with a shorter time to live (TTL) first.

                                  +

                                  noeviction: Do not delete any keys and only return errors when the memory limit was reached.

                                  +

                                  volatile-lfu: Evict keys by trying to remove the less frequently used (LFU) keys first, but only among keys that have an expire set.

                                  +

                                  allkeys-lfu: Evict keys by trying to remove the LFU keys first.

                                  +

                                  Depends on the instance version.

                                  +

                                  Depends on the instance version and type.

                                  +

                                  lua-time-limit

                                  +

                                  Maximum time allowed for executing a Lua script (in milliseconds).

                                  +

                                  100–5000

                                  +

                                  5,000

                                  +

                                  master-read-only

                                  +

                                  Sets the instance to be read-only. All write operations will fail.

                                  +

                                  Proxy Cluster instances do not have this parameter.

                                  +
                                  • yes
                                  • no
                                  +

                                  no

                                  +

                                  maxclients

                                  +

                                  The maximum number of clients allowed to be concurrently connected to a DCS instance.

                                  +

                                  Proxy Cluster instances do not have this parameter.

                                  +

                                  Depends on the instance type and specifications.

                                  +

                                  Depends on the instance type and specifications.

                                  +

                                  proto-max-bulk-len

                                  +

                                  Maximum size of a single element request (in bytes).

                                  +

                                  1,048,576–536,870,912

                                  +

                                  536,870,912

                                  +

                                  repl-backlog-size

                                  +

                                  The replication backlog size (bytes). The backlog is a buffer that accumulates replica data when replicas are disconnected from the master. When a replica reconnects, a partial synchronization is performed to synchronize the data that was missed while replicas were disconnected.

                                  +

                                  16,384–1,073,741,824

                                  +

                                  1,048,576

                                  +

                                  repl-backlog-ttl

                                  +

                                  The amount of time, in seconds, before the backlog buffer is released, starting from the last a replica was disconnected. The value 0 indicates that the backlog is never released.

                                  +

                                  0–604,800

                                  +

                                  3,600

                                  +

                                  repl-timeout

                                  +

                                  Replication timeout (in seconds).

                                  +

                                  30–3,600

                                  +

                                  60

                                  +

                                  hash-max-ziplist-entries

                                  +

                                  Hashes are encoded using a memory efficient data structure when the number of entries in hashes is less than the value of this parameter.

                                  +

                                  1–10,000

                                  +

                                  512

                                  +

                                  hash-max-ziplist-value

                                  +

                                  Hashes are encoded using a memory efficient data structure when the biggest entry in hashes does not exceed the length threshold indicated by this parameter.

                                  +

                                  1–10,000

                                  +

                                  64

                                  +

                                  set-max-intset-entries

                                  +

                                  When a set is composed of just strings that happen to be integers in radix 10 in the range of 64 bit signed integers, sets are encoded using a memory efficient data structure.

                                  +

                                  1–10,000

                                  +

                                  512

                                  +

                                  zset-max-ziplist-entries

                                  +

                                  Sorted sets are encoded using a memory efficient data structure when the number of entries in sorted sets is less than the value of this parameter.

                                  +

                                  1–10,000

                                  +

                                  128

                                  +

                                  zset-max-ziplist-value

                                  +

                                  Sorted sets are encoded using a memory efficient data structure when the biggest entry in sorted sets does not exceed the length threshold indicated by this parameter.

                                  +

                                  1–10,000

                                  +

                                  64

                                  +

                                  latency-monitor-threshold

                                  +

                                  Threshold time in latency monitoring. Unit: millisecond.

                                  +

                                  Set to 0: Latency monitoring is disabled.

                                  +

                                  Set to more than 0: All with at least this many milliseconds of latency will be logged.

                                  +

                                  By running the LATENCY command, you can perform operations related to latency monitoring, such as obtaining statistical data, and configuring and enabling latency monitoring.

                                  +

                                  0–86,400,000 ms

                                  +

                                  0

                                  +

                                  notify-keyspace-events

                                  +

                                  Controls which keyspace events notifications are enabled for. If the value is an empty string, this function is disabled. A combination of different values can be used to enable notifications for multiple event types. Possible values:

                                  +

                                  K: Keyspace events, published with the __keyspace@__ prefix.

                                  +

                                  E: Keyevent events, published with __keyevent@__ prefix

                                  +

                                  g: Generic commands (non-type specific) such as DEL, EXPIRE, and RENAME

                                  +

                                  $: String commands

                                  +

                                  l: List commands

                                  +

                                  s: Set commands

                                  +

                                  h: Hash commands

                                  +

                                  z: Sorted set commands

                                  +

                                  x: Expired events (events generated every time a key expires)

                                  +

                                  e: Evicted events (events generated when a key is evicted for maxmemory)

                                  +

                                  A: an alias for "g$lshzxe"

                                  +

                                  The parameter value must contain either K or E. A cannot be used together with any of the characters in "g$lshzxe". For example, the value Kl means that Redis will notify Pub/Sub clients about keyspace events and list commands. The value AKE means Redis will notify Pub/Sub clients about all events.

                                  +

                                  Proxy Cluster instances do not have this parameter.

                                  +

                                  See the parameter description.

                                  +

                                  Ex

                                  +

                                  slowlog-log-slower-than

                                  +

                                  Redis records queries that exceed a specified execution time.

                                  +

                                  slowlog-log-slower-than is the maximum time allowed, in microseconds, for command execution. If this threshold is exceeded, Redis will record the query.

                                  +

                                  0–1,000,000

                                  +

                                  10,000

                                  +

                                  slowlog-max-len

                                  +

                                  The maximum allowed number of slow queries that can be logged. Slow query log consumes memory, but you can reclaim this memory by running the SLOWLOG RESET command.

                                  +

                                  0–1000

                                  +

                                  128

                                  +
                                  +
                                  +
                                  1. The default values and value ranges of the maxclients, reserved-memory-percent, client-output-buffer-slave-soft-limit, and client-output-buffer-slave-hard-limit parameters are related to the instance specifications. Therefore, these parameters cannot be modified.
                                  2. For more information about the parameters described in Table 1, visit https://redis.io/topics/memory-optimization.
                                  3. The latency-monitor-threshold parameter is usually used for fault location. After locating faults based on the latency information collected, change the value of latency-monitor-threshold to 0 to avoid unnecessary latency.
                                  4. More about the notify-keyspace-events parameter:
                                    • The parameter setting must contain at least a K or E.
                                    • A is an alias for "g$lshzxe" and cannot be used together with any of the characters in "g$lshzxe".
                                    • For example, the value Kl means that Redis will notify Pub/Sub clients about keyspace events and list commands. The value AKE means Redis will notify Pub/Sub clients about all events.
                                    +
                                  +
                                  +

                                +
                                +
                                +
                                +
                                +
                                Parent topic: Parameter Templates
                                +
                                +
                                + diff --git a/docs/dcs/umn/dcs-ug-210622005.html b/docs/dcs/umn/dcs-ug-210622005.html new file mode 100644 index 000000000..c1e3ab879 --- /dev/null +++ b/docs/dcs/umn/dcs-ug-210622005.html @@ -0,0 +1,13 @@ + + +

                                Deleting a Custom Parameter Template

                                +

                                This section describes how to delete a custom parameter template.

                                +

                                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 Parameter Templates.
                                4. Choose the Custom Templates tab.
                                5. Click Delete in the Operation column.
                                6. Click Yes.
                                +
                                +
                                +
                                +
                                +
                                Parent topic: Parameter Templates
                                +
                                +
                                + diff --git a/docs/dcs/umn/dcs-ug-210626004.html b/docs/dcs/umn/dcs-ug-210626004.html index 41573c01d..f59f57412 100644 --- a/docs/dcs/umn/dcs-ug-210626004.html +++ b/docs/dcs/umn/dcs-ug-210626004.html @@ -5,13 +5,14 @@
                                • Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing DCS resources.
                                • Grant only the permissions required for users to perform a specific task.
                                • Entrust an account or cloud service to perform efficient O&M on your DCS resources.

                                If your account does not need individual IAM users, you may skip over this chapter.

                                This section describes the procedure for granting the DCS ReadOnlyAccess permission (see Figure 1) as an example.

                                -

                                Prerequisites

                                You are familiar with the permissions (see Permissions Management) supported by DCS and choose policies or roles according to your requirements. For the permissions of other services, see Permissions Policies.

                                +

                                Prerequisites

                                You are familiar with the permissions (see Permissions) supported by DCS and choose policies or roles according to your requirements. For the permissions of other services, see Permissions.

                                +

                                Process Flow

                                Figure 1 Process of granting DCS permissions

                                -
                                1. Create a user group and grant permissions.

                                  Create a user group on the IAM console, and attach the DCS ReadOnlyAccess policy to the group.

                                  -
                                2. Create an IAM user.

                                  Create a user on the IAM console and add the user to the group created in 1.

                                  -
                                3. Log in and verify permissions.

                                  Log in to the DCS console by using the newly created user, and verify that the user only has read permissions for DCS.

                                  +
                                  1. Create a user group and assign permissions to it.

                                    Create a user group on the IAM console, and attach the DCS ReadOnlyAccess policy to the group.

                                    +
                                  2. Create an IAM user.

                                    Create a user on the IAM console and add the user to the group created in 1.

                                    +
                                  3. Log in and verify permissions.

                                    Log in to the DCS console by using the newly created user, and verify that the user only has read permissions for DCS.

                                diff --git a/docs/dcs/umn/dcs-ug-210626005.html b/docs/dcs/umn/dcs-ug-210626005.html index 9a44bd5e9..ab1f40d59 100644 --- a/docs/dcs/umn/dcs-ug-210626005.html +++ b/docs/dcs/umn/dcs-ug-210626005.html @@ -1,10 +1,10 @@

                                DCS Custom Policies

                                -

                                Custom policies can be created to supplement the system-defined policies of DCS. For the actions that can be added for custom policies, see Permissions Policies and Supported Actions.

                                +

                                Custom policies can be created to supplement the system-defined policies of DCS. For the actions that can be added to custom policies, see section "Permissions Policies and Supported Actions" in the Distributed Cache Service API Reference.

                                You can create custom policies in either of the following ways:

                                • Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
                                • JSON: Edit JSON policies from scratch or based on an existing policy.
                                -

                                For details, see "Creating a Custom Policy". The following section contains examples of common DCS custom policies.

                                +

                                For details, see section "Creating a Custom Policy" in the Identity and Access Management API Reference. The following section contains examples of common DCS custom policies.

                                Due to data caching, a policy involving OBS actions will take effect five minutes after it is attached to a user, user group, or project.

                                Example Custom Policies

                                • Example 1: Allowing users to delete and restart DCS instances and clear data of an instance
                                  {
diff --git a/docs/dcs/umn/dcs-ug-211011001.html b/docs/dcs/umn/dcs-ug-211011001.html
deleted file mode 100644
index 406e40420..000000000
--- a/docs/dcs/umn/dcs-ug-211011001.html
+++ /dev/null
@@ -1,67 +0,0 @@
-
-
-
                                  Lettuce
                                  
-
                                  Access a Redis Cluster instance through Lettuce on an ECS in the same VPC. For more information on how to use other Redis clients, visit https://redis.io/clients.
                                  
-
                                   
                                  If a password was set during DCS Redis instance creation, configure the password for connecting to Redis using Lettuce. Do not hard code the plaintext password.
                                  
-
                                  To connect to a single-node, master/standby, or Proxy Cluster instance, use the RedisClient object of Lettuce. To connect to a Redis Cluster instance, use the RedisClusterClient object.
                                  
-
                                  
-
                                  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 Java compilation environment has been installed on the ECS.
                                  
-
                                  
-
                                  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. Use Maven to add the following dependency to the pom.xml file:
                                    <dependency>
-  <groupId>io.lettuce</groupId>
-  <artifactId>lettuce-core</artifactId>
-  <version>6.1.6.RELEASE</version>
-</dependency>
                                    
-
                                  4. Use Lettuce (a Java client) to connect to the DCS instance.
                                    • Example of using Lettuce to connect to a single-node, master/standby, or Proxy Cluster DCS Redis instance with a single connection
                                      // password indicates the connection password. If there is no password, delete "password@". If there is a password and it contains special characters, conversion is required.
-RedisClient redisClient = RedisClient.create("redis://password@host:port");
-StatefulRedisConnection<String, String> connection = redisClient.connect();
-RedisCommands<String, String> syncCommands = connection.sync();
-syncCommands.set("key", "value");
-System.out.println("Connected to Redis:" + syncCommands.get("key"));
-// Close the connection.
-connection.close();
-// Close the client.
-redisClient.shutdown();
                                      
-
                                    • Example of using Lettuce to connect to a single-node, master/standby, or Proxy Cluster DCS Redis instance with connection pooling
                                      // password indicates the connection password. If there is no password, delete "password@". If there is a password and it contains special characters, conversion is required.
-RedisClient clusterClient = RedisClient.create("redis://password@host:port");
-GenericObjectPoolConfig<StatefulRedisConnection<String, String>> genericObjectPoolConfig = new GenericObjectPoolConfig();
-// Connection pool parameters
-genericObjectPoolConfig.setMaxIdle(3);
-genericObjectPoolConfig.setMinIdle(2);
-genericObjectPoolConfig.setMaxTotal(3);
-genericObjectPoolConfig.setMaxWaitMillis(-1);
-GenericObjectPool<StatefulRedisConnection<String, String>> pool = ConnectionPoolSupport
-        .createGenericObjectPool(() -> clusterClient.connect(), genericObjectPoolConfig);
-// Obtain a connection to perform operations.
-try (StatefulRedisConnection<String, String> con = pool.borrowObject()) {
-    RedisCommands<String, String> sync = con.sync();
-	sync.set("key", "value");
-    System.out.println("Connected by pool:" + sync.get("key"));
-} catch (Exception e) {
-    e.printStackTrace();
-}finally {
-    // Close the resources.
-    pool.close();
-    clusterClient.shutdown();
-}
                                      
-
                                    • Example of using Lettuce to connect to a Redis Cluster
                                      // password indicates the connection password. If there is no password, delete "password@". If there is a password and it contains special characters, conversion is required.
-RedisClusterClient redisClient = RedisClusterClient.create("redis://password@host:port");
-StatefulRedisClusterConnection<String, String> connection = redisClient.connect();
-RedisAdvancedClusterCommands<String, String> syncCommands = connection.sync();
-syncCommands.set("key", "value");
-System.out.println("Connected to RedisCluster:"+syncCommands.get("key"));
-// Close the connection.
-connection.close();
-// Close the client.
-redisClient.shutdown();
                                      
-
                                    
-
                                  
-
                                  
-
                                  
-
                                  
-
                                  
-
                                  Parent topic: Java
                                  
-
                                  
-
                                  
-
diff --git a/docs/dcs/umn/dcs-ug-211105001.html b/docs/dcs/umn/dcs-ug-211105001.html
index ade8cad1d..9db5d56ec 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.
                                  • An ECS has been created. For details about how to create an ECS, see Elastic Cloud Server User Guide.
                                  
+
                                  Prerequisites
                                  • A DCS Redis instance has been created and is in the Running state.
                                  • An ECS has been created. For details about how to create an ECS, see Elastic Cloud Server User Guide.
                                  
 
                                  
 
                                  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.
                                    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 1. Change the IP address/domain name and port 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 1. 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.

                                • 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 new file mode 100644 index 000000000..ac74bbff2 --- /dev/null +++ b/docs/dcs/umn/dcs-ug-211105002.html @@ -0,0 +1,133 @@ + + +

                                  Lettuce

                                  +

                                  Access a DCS Redis instance through Lettuce 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.
                                  • 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.
                                  +
                                  +

                                  Procedure

                                  1. View the IP address 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. Use Maven to add the following dependency to the pom.xml file:

                                    <dependency>
+  <groupId>io.lettuce</groupId>
+  <artifactId>lettuce-core</artifactId>
+  <version>6.1.6.RELEASE</version>
+</dependency>
                                    +

                                  4. Use Lettuce (a Java client) to connect to the DCS instance.

                                    • Example of using Lettuce to connect to a single-node, master/standby, or Proxy Cluster DCS Redis instance with a single connection
                                      // password indicates the connection password. If there is no password, delete "password@". If there is a password and it contains special characters, conversion is required.
+RedisClient redisClient = RedisClient.create("redis://password@host:port");
+StatefulRedisConnection<String, String> connection = redisClient.connect();
+RedisCommands<String, String> syncCommands = connection.sync();
+syncCommands.set("key", "value");
+System.out.println("Connected to Redis:" + syncCommands.get("key"));
+// Close the connection.
+connection.close();
+// Close the client.
+redisClient.shutdown();
                                      +
                                    • Example of using Lettuce to connect to a single-node, master/standby, or Proxy Cluster DCS Redis instance with connection pooling
                                      1. Add the following dependency in addition to the preceding Maven dependency:
                                        <dependency>  
+   <groupId>org.apache.commons</groupId>  
+   <artifactId>commons-pool2</artifactId>
+    <version>2.11.1</version>  
+ </dependency>
                                        +
                                      2. The code is as follows:
                                        // password indicates the connection password. If there is no password, delete "password@". If there is a password and it contains special characters, conversion is required.
+RedisClient clusterClient = RedisClient.create("redis://password@host:port");
+GenericObjectPoolConfig<StatefulRedisConnection<String, String>> genericObjectPoolConfig = new GenericObjectPoolConfig();
+// Connection pool parameters
+genericObjectPoolConfig.setMaxIdle(3);
+genericObjectPoolConfig.setMinIdle(2);
+genericObjectPoolConfig.setMaxTotal(3);
+genericObjectPoolConfig.setMaxWaitMillis(-1);
+GenericObjectPool<StatefulRedisConnection<String, String>> pool = ConnectionPoolSupport
+        .createGenericObjectPool(() -> clusterClient.connect(), genericObjectPoolConfig);
+// Obtain a connection to perform operations.
+try (StatefulRedisConnection<String, String> con = pool.borrowObject()) {
+    RedisCommands<String, String> sync = con.sync();
+	sync.set("key", "value");
+    System.out.println("Connected by pool:" + sync.get("key"));
+} catch (Exception e) {
+    e.printStackTrace();
+}finally {
+    // Close the resources.
+    pool.close();
+    clusterClient.shutdown();
+}
                                        +
                                      +
                                    • Example of using Lettuce to connect to a Redis Cluster DCS Redis instance with a single connection (automated topology refresh must be enabled)
                                      public class SingleConnectionToCluster {  
+    public static void main(String[] args) {
+         // Enable automated topology refresh.
+        ClusterTopologyRefreshOptions topologyRefreshOptions = ClusterTopologyRefreshOptions.builder()  
+         // Periodic refresh: every time milliseconds.
+            .enablePeriodicRefresh(Duration.ofMillis(time))  
+         // Triggers of adaptive refresh: MOVED redirection, ASK redirection, reconnection, unknown node (since 5.1), and slot not in any of the current shards (since 5.2).
+            .enableAllAdaptiveRefreshTriggers()  
+            .build();  
+        // password indicates the connection password. If there is no password, delete "password@". If there is a password and it contains special characters, conversion is required.
+        RedisClusterClient redisClient = RedisClusterClient.create("redis://password@host:port");  
+        redisClient.setOptions(ClusterClientOptions.builder()  
+            .topologyRefreshOptions(topologyRefreshOptions)  
+            .build());  
+        StatefulRedisClusterConnection<String, String> connection = redisClient.connect(); 
+         // Preferentially read data from the replicas.
+         connection.setReadFrom(ReadFrom.REPLICA_PREFERRED); 
+        RedisAdvancedClusterCommands<String, String> syncCommands = connection.sync();  
+        syncCommands.set("key", "value");  
+        System.out.println("Connected to RedisCluster:" + syncCommands.get("key"));  
+        // Close the connection.
+        connection.close();  
+        // Close the client.
+        redisClient.shutdown();  
+    }  
+}
                                      +
                                    • Example code for connecting to Redis Cluster with connection pooling
                                      1. Add the following dependency in addition to the preceding Maven dependency:
                                        <dependency>  
+   <groupId>org.apache.commons</groupId>  
+   <artifactId>commons-pool2</artifactId>
+    <version>2.11.1</version>  
+ </dependency>
                                        +
                                      2. The code is as follows (automated topology refresh must be enabled):
                                        public class PoolConnectionToCluster {  
+    public static void main(String[] args) {
+         // Enable automated topology refresh.
+        ClusterTopologyRefreshOptions topologyRefreshOptions = ClusterTopologyRefreshOptions.builder()  
+         // Periodic refresh every time milliseconds.
+            .enablePeriodicRefresh(Duration.ofMillis(time))  
+         // Triggers of adaptive refresh: MOVED redirection, ASK redirection, reconnection, unknown node (since 5.1), and slot not in any of the current shards (since 5.2).
+            .enableAllAdaptiveRefreshTriggers()  
+            .build();  
+        // password indicates the connection password. If there is no password, delete "password@". If there is a password and it contains special characters, conversion is required.
+        RedisClusterClient redisClient = RedisClusterClient.create("redis://password@host:port");  
+        redisClient.setOptions(ClusterClientOptions.builder()  
+            .topologyRefreshOptions(topologyRefreshOptions)  
+            .build());  
+        GenericObjectPoolConfig<StatefulRedisClusterConnection<String, String>> genericObjectPoolConfig  
+            = new GenericObjectPoolConfig();  
+        // Connection pool parameters
+        genericObjectPoolConfig.setMaxIdle(3);  
+        genericObjectPoolConfig.setMinIdle(2);  
+        genericObjectPoolConfig.setMaxTotal(3);  
+        genericObjectPoolConfig.setTimeBetweenEvictionRuns(Duration.ofMillis(2000));  
+        genericObjectPoolConfig.setMaxWait(Duration.ofMillis(5000));  
+        GenericObjectPool<StatefulRedisClusterConnection<String, String>> pool = ConnectionPoolSupport  
+            .createGenericObjectPool(() -> redisClient.connect(), genericObjectPoolConfig);  
+        // Obtain a connection to perform operations.
+        try (StatefulRedisClusterConnection<String, String> con = pool.borrowObject()) {  
+            // Preferentially read data from the replicas.
+             con.setReadFrom(ReadFrom.REPLICA_PREFERRED);
+            RedisAdvancedClusterCommands<String, String> syncCommands = con.sync();  
+            syncCommands.set("key", "value");  
+            System.out.println("Connected to RedisCluster:" + syncCommands.get("key"));  
+        } catch (Exception e) {  
+            e.printStackTrace();  
+        } finally {  
+    // Close the resources.
+            pool.close();  
+            redisClient.shutdown();  
+        }  
+    }  
+}
                                        +
                                      +
                                    +

                                    host is the IP address of the DCS instance, port is the port number of the DCS instance, and password is the password of the DCS instance. Specify these parameters as required before running the code. Connection pooling is recommended. Adjust parameters such as timeout, MaxTotal (maximum number of connections), MinIdle (minimum number of idle connections), MaxIdle (maximum number of idle connections), and MaxWait (maximum waiting time) based on service requirements.

                                    +

                                  +
                                  +
                                  +
                                  +
                                  +
                                  Parent topic: Java
                                  +
                                  +
                                  + diff --git a/docs/dcs/umn/dcs-ug-211105003.html b/docs/dcs/umn/dcs-ug-211105003.html index 52c651e20..ec9f55ae7 100644 --- a/docs/dcs/umn/dcs-ug-211105003.html +++ b/docs/dcs/umn/dcs-ug-211105003.html @@ -6,7 +6,7 @@
                                  • Jedis
                                    • -
                                  • Lettuce
                                    +
                                  • Lettuce
                                  • Redisson
                                    • diff --git a/docs/dcs/umn/dcs-ug-211105004.html b/docs/dcs/umn/dcs-ug-211105004.html index e33438e90..a3d9ee546 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.

                                    • 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.
                                    -

                                    Prerequisites

                                    • A DCS Redis instance has been created and is in the Running state.
                                    • 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.
                                    +

                                    Prerequisites

                                    • A DCS Redis instance has been created and is in the Running state.
                                    • 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.

                                    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. Use Maven to add the following dependency to the pom.xml file:

                                      <dependency>
diff --git a/docs/dcs/umn/dcs-ug-211202002.html b/docs/dcs/umn/dcs-ug-211202002.html
index 17a4b474a..e7eede698 100644
--- a/docs/dcs/umn/dcs-ug-211202002.html
+++ b/docs/dcs/umn/dcs-ug-211202002.html
@@ -2,7 +2,7 @@
 
 
                                      Predis
                                      
 
                                      Access a DCS Redis instance through Predis 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.
                                      • 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 PHP compilation environment has been installed on the ECS.
                                      
+
                                      Prerequisites
                                      • A DCS Redis instance has been created and is in the Running state.
                                      • 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 PHP compilation environment has been installed on the ECS.
                                      
 
                                      
 
                                      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
                                        
@@ -38,7 +38,7 @@
        echo $value;
 ?>
                                  -

                                  {redis_instance_address} indicates the actual IP address or 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 the IP address/domain name and port 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".

                                • Run the php redis.php command to access the DCS instance.
                                diff --git a/docs/dcs/umn/dcs-ug-211203001.html b/docs/dcs/umn/dcs-ug-211203001.html index eedac5b5c..24d2a57db 100644 --- a/docs/dcs/umn/dcs-ug-211203001.html +++ b/docs/dcs/umn/dcs-ug-211203001.html @@ -1,7 +1,7 @@

                                Lettuce Integration with Spring Boot

                                -

                                Prerequisites

                                • A DCS Redis instance has been created and is in the Running state.
                                • 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.
                                +

                                Prerequisites

                                • A DCS Redis instance has been created and is in the Running state.
                                • 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.

                                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. Use Maven to add the following dependency to the pom.xml file:

                                  • Since Spring Boot 2.0, Lettuce is used as the default client for connections.
                                  • Spring Boot 2.6.6 and Lettuce 6.1.8 are used.
                                  @@ -281,7 +281,7 @@ public RedisTemplate<String, Object> redisTemplate(LettuceConnectionFactor }
                              -

                              host is the IP address/domain name of the DCS instance, port is the port number of the DCS instance, and pwd is the password of the DCS instance. Specify these parameters as required before running the code. Connection pooling is recommended. Adjust parameters such as TimeOut, MaxTotal (maximum number of connections), MinIdle (minimum number of idle connections), MaxIdle (maximum number of idle connections), and MaxWait (maximum waiting time) based on service requirements.

                              +

                              host is the IP address/domain name of the DCS instance, port is the port number of the DCS instance, and pwd is the password of the DCS instance. Specify these parameters as required before running the code. Connection pooling is recommended. Adjust parameters such as TimeOut, MaxTotal (maximum number of connections), MinIdle (minimum number of idle connections), MaxIdle (maximum number of idle connections), and MaxWait (maximum waiting time) based on service requirements.

                              diff --git a/docs/dcs/umn/en-us_image_0000001148443452.png b/docs/dcs/umn/en-us_image_0000001148443452.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/dcs/umn/en-us_image_0000001148443452.png differ diff --git a/docs/dcs/umn/en-us_image_0266235362.png b/docs/dcs/umn/en-us_image_0000001318437462.png similarity index 100% rename from docs/dcs/umn/en-us_image_0266235362.png rename to docs/dcs/umn/en-us_image_0000001318437462.png diff --git a/docs/dcs/umn/en-us_image_0000001369446161.png b/docs/dcs/umn/en-us_image_0000001369446161.png new file mode 100644 index 000000000..0eed9ccf0 Binary files /dev/null and b/docs/dcs/umn/en-us_image_0000001369446161.png differ diff --git a/docs/dcs/umn/en-us_image_0000001369885981.png b/docs/dcs/umn/en-us_image_0000001369885981.png new file mode 100644 index 000000000..0eed9ccf0 Binary files /dev/null and b/docs/dcs/umn/en-us_image_0000001369885981.png differ diff --git a/docs/dcs/umn/en-us_image_0000001407952686.png b/docs/dcs/umn/en-us_image_0000001407952686.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/dcs/umn/en-us_image_0000001407952686.png differ diff --git a/docs/dcs/umn/en-us_image_0000001408112658.png b/docs/dcs/umn/en-us_image_0000001408112658.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/dcs/umn/en-us_image_0000001408112658.png differ diff --git a/docs/dcs/umn/en-us_image_0000001457367809.png b/docs/dcs/umn/en-us_image_0000001457367809.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/dcs/umn/en-us_image_0000001457367809.png differ diff --git a/docs/dcs/umn/en-us_image_0000001457792613.png b/docs/dcs/umn/en-us_image_0000001457792613.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/dcs/umn/en-us_image_0000001457792613.png differ diff --git a/docs/dcs/umn/en-us_image_0000001478356482.png b/docs/dcs/umn/en-us_image_0000001478356482.png new file mode 100644 index 000000000..4cd8cc7b6 Binary files /dev/null and b/docs/dcs/umn/en-us_image_0000001478356482.png differ diff --git a/docs/dcs/umn/en-us_image_0000001505063901.png b/docs/dcs/umn/en-us_image_0000001505063901.png new file mode 100644 index 000000000..0eed9ccf0 Binary files /dev/null and b/docs/dcs/umn/en-us_image_0000001505063901.png differ diff --git a/docs/dcs/umn/en-us_image_0000001536314713.png b/docs/dcs/umn/en-us_image_0000001536314713.png new file mode 100644 index 000000000..1102f8f19 Binary files /dev/null and b/docs/dcs/umn/en-us_image_0000001536314713.png differ diff --git a/docs/dcs/umn/en-us_image_0000001539798309.png b/docs/dcs/umn/en-us_image_0000001539798309.png new file mode 100644 index 000000000..bbb613bbe Binary files /dev/null and b/docs/dcs/umn/en-us_image_0000001539798309.png differ diff --git a/docs/dcs/umn/en-us_image_0000001540208017.png b/docs/dcs/umn/en-us_image_0000001540208017.png new file mode 100644 index 000000000..9a8b78f3d Binary files /dev/null and b/docs/dcs/umn/en-us_image_0000001540208017.png differ diff --git a/docs/dcs/umn/en-us_image_0000001540447885.png b/docs/dcs/umn/en-us_image_0000001540447885.png new file mode 100644 index 000000000..6a22ba65a Binary files /dev/null and b/docs/dcs/umn/en-us_image_0000001540447885.png differ diff --git a/docs/dcs/umn/en-us_image_0000001572243777.png b/docs/dcs/umn/en-us_image_0000001572243777.png new file mode 100644 index 000000000..0eed9ccf0 Binary files /dev/null and b/docs/dcs/umn/en-us_image_0000001572243777.png differ diff --git a/docs/dcs/umn/en-us_image_0266235369.png b/docs/dcs/umn/en-us_image_0266235369.png new file mode 100644 index 000000000..240e1d269 Binary files /dev/null and b/docs/dcs/umn/en-us_image_0266235369.png differ diff --git a/docs/dcs/umn/en-us_image_0266235377.png b/docs/dcs/umn/en-us_image_0266235377.png new file mode 100644 index 000000000..fc283885c Binary files /dev/null and b/docs/dcs/umn/en-us_image_0266235377.png differ diff --git a/docs/dcs/umn/en-us_image_0266235408.png b/docs/dcs/umn/en-us_image_0266235408.png new file mode 100644 index 000000000..240e1d269 Binary files /dev/null and b/docs/dcs/umn/en-us_image_0266235408.png differ diff --git a/docs/dcs/umn/en-us_image_0266235415.png b/docs/dcs/umn/en-us_image_0266235415.png new file mode 100644 index 000000000..fc283885c Binary files /dev/null and b/docs/dcs/umn/en-us_image_0266235415.png differ diff --git a/docs/dcs/umn/en-us_image_0266235461.jpg b/docs/dcs/umn/en-us_image_0266235461.jpg deleted file mode 100644 index 76e70fb74..000000000 Binary files a/docs/dcs/umn/en-us_image_0266235461.jpg and /dev/null differ diff --git a/docs/dcs/umn/en-us_image_0266235565.jpg b/docs/dcs/umn/en-us_image_0266235565.jpg deleted file mode 100644 index 30be5760a..000000000 Binary files a/docs/dcs/umn/en-us_image_0266235565.jpg and /dev/null differ diff --git a/docs/dcs/umn/en-us_image_0266316214.jpg b/docs/dcs/umn/en-us_image_0266316214.jpg deleted file mode 100644 index be126924e..000000000 Binary files a/docs/dcs/umn/en-us_image_0266316214.jpg and /dev/null differ diff --git a/docs/dcs/umn/en-us_topic_0054235826.html b/docs/dcs/umn/en-us_topic_0054235826.html index 1487e5c1d..2300dc31e 100644 --- a/docs/dcs/umn/en-us_topic_0054235826.html +++ b/docs/dcs/umn/en-us_topic_0054235826.html @@ -3,7 +3,7 @@

                              What Is DCS?

                              Distributed Cache Service (DCS) is an online, distributed, in-memory cache service compatible with Redis. It is reliable, scalable, usable out of the box, and easy to manage, meeting your requirements for high read/write performance and fast data access.

                              • Usability out of the box

                                DCS provides single-node, master/standby, and cluster instances with specifications ranging from 128 MB to 1024 GB. DCS instances can be created with just a few clicks on the console, without requiring you to prepare servers.

                                -

                                DCS Redis 3.0 instances are deployed on VMs. DCS Redis 4.0 and 5.0 instances are containerized and can be created within seconds.

                                +

                                DCS Redis 3.0 instances are deployed on VMs. DCS Redis 4.0/5.0/6.0 instances are containerized and can be created within seconds.

                              • Security and reliability

                                Instance data storage and access are securely protected through security management services, including Identity and Access Management (IAM), Virtual Private Cloud (VPC), Cloud Eye, and Cloud Trace Service (CTS).

                                Master/Standby and cluster instances can be deployed within an availability zone (AZ) or across AZs.

                              • Auto scaling

                                DCS instances can be scaled up or down online, helping you control costs based on service requirements.

                                @@ -15,7 +15,7 @@
                                - -
                                Table 1 DCS Redis instance configuration

                                Instance type

                                DCS for Redis provides the following three types of instances to suit different service scenarios:

                                +

                                DCS for Redis provides the following types of instances to suit different service scenarios:

                                Single-node: Suitable for caching temporary data in low reliability scenarios. Single-node instances support highly concurrent read/write operations, but do not support data persistence. Data will be deleted after instances are restarted.

                                Master/Standby: Each master/standby instance runs on two nodes (one master and one standby). The standby node replicates data synchronously from the master node. If the master node fails, the standby node automatically becomes the master node.

                                Cluster: Each cluster DCS instance consists of multiple shards and each shard includes a master node and zero or multiple replicas. Shards are not visible to users. If the master node fails, a standby node in the same shard takes over.

                                @@ -28,7 +28,7 @@

                                Redis version

                                DCS instances are compatible with open-source Redis 3.0, 4.0, and 5.0.

                                +

                                DCS instances are compatible with open-source Redis 3.0, 4.0, 5.0, and 6.0.

                                Underlying architecture

                                diff --git a/docs/dcs/umn/en-us_topic_0054235835.html b/docs/dcs/umn/en-us_topic_0054235835.html index 887f14848..a9c716648 100644 --- a/docs/dcs/umn/en-us_topic_0054235835.html +++ b/docs/dcs/umn/en-us_topic_0054235835.html @@ -8,6 +8,8 @@
                              • Redis 4.0 and 5.0 Instance Specifications
                                • +
                              • Redis 6.0 Instance Specifications
                                +
                                • diff --git a/docs/dcs/umn/en-us_topic_0054235837.html b/docs/dcs/umn/en-us_topic_0054235837.html index 66e5640d4..e4ae2ab8a 100644 --- a/docs/dcs/umn/en-us_topic_0054235837.html +++ b/docs/dcs/umn/en-us_topic_0054235837.html @@ -2,7 +2,7 @@

                                How to Access DCS

                                There are two ways to access DCS:

                                -
                                • Using the management console

                                  The DCS provides a web-based management console. To launch the DCS console, create an account on the management console and log in, and then choose Application > Distributed Cache Service on the homepage. On the DCS console, you can create, restart, and delete DCS instances, and change their passwords.

                                  +
                                  • Using the management console

                                    The DCS provides a web-based management console. To launch the DCS console, create an account on the management console and log in, and then choose Database > Distributed Cache Service on the homepage. On the DCS console, you can create, restart, and delete DCS instances, and change their passwords.

                                  • Using APIs

                                    If you want to integrate DCS into a third-party system for secondary development, use APIs to access DCS. For more information about available APIs, see the Distributed Cache Service API Reference.

                                diff --git a/docs/dcs/umn/en-us_topic_0079835992.html b/docs/dcs/umn/en-us_topic_0079835992.html index 0ef45c25e..d1ff35e72 100644 --- a/docs/dcs/umn/en-us_topic_0079835992.html +++ b/docs/dcs/umn/en-us_topic_0079835992.html @@ -9,8 +9,9 @@
                                • Automated backup

                                  You can create a scheduled backup policy on the DCS console. Then, data in the chosen DCS instances will be automatically backed up at the scheduled time.

                                  You can choose the days of the week on which scheduled backup will run. Backup data will be retained for a maximum of seven days. Backup data older than seven days will be automatically deleted.

                                  The primary purpose of scheduled backups is to create complete data replicas of DCS instances so that the instance can be quickly restored if necessary.

                                  -
                                • Manual backup

                                  Backup requests can also be issued manually. Then, data in the chosen DCS instances will be permanently backed up to OBS. Backup data can be deleted manually.

                                  +
                                • Manual backup

                                  Backup requests can be issued manually. Data in the chosen DCS instances will be backed up to OBS.

                                  Before performing high-risk operations, such as system maintenance or upgrade, back up DCS instance data.

                                  +

                                  When a DCS instance is in use, its backup data will not be automatically deleted. You can manually delete backup data as required. When you delete the instance, its backup data is deleted along with the instance. If you need the backup data, download and save it in advance.

                                Additional Information About Data Backup

                                • Instance type

                                  Redis: Only master/standby, Proxy Cluster, and Redis Cluster instances can be backed up and restored, while single-node instances cannot. However, you can export data of a single-node instance to an RDB file using redis-cli. For details, see Can I Export Backup Data of DCS Redis Instances to RDB Files Using the Console?

                                  @@ -21,7 +22,7 @@

                                  In the event of full-data synchronization or heavy instance load, it takes a few minutes to complete data synchronization. If instance backup starts before data synchronization is complete, the backup data will be slightly behind the data in the master cache node.

                                  During instance backup, the standby cache node stops persisting the latest changes to disk files. If new data is written to the master cache node during backup, the backup file will not contain the new data.

                                • Backup time

                                  It is advisable to back up instance data during off-peak periods.

                                  -
                                • Storage and pricing of backup files

                                  Backup files are stored to OBS.

                                  +
                                • Storage of backup files

                                  Backup files are stored to OBS.

                                • Handling exceptions in scheduled backup

                                  If a scheduled backup task is triggered while the DCS instance is restarting or being scaled up, the scheduled backup task will be run in the next cycle.

                                  If backing up a DCS instance fails or the backup is postponed because another task is in progress, DCS will try to back up the instance in the next cycle. A maximum of three retries are allowed within a single day.

                                • Retention period of backup data

                                  Scheduled backup files are retained for up to seven days. You can configure the retention period. At the end of the retention period, most backup files of the DCS instance will be automatically deleted, but at least one backup file will be retained.

                                  diff --git a/docs/dcs/umn/en-us_topic_0090662012.html b/docs/dcs/umn/en-us_topic_0090662012.html index 8efdd05ad..6649e7607 100644 --- a/docs/dcs/umn/en-us_topic_0090662012.html +++ b/docs/dcs/umn/en-us_topic_0090662012.html @@ -1,9 +1,9 @@

                                  Security Group Configurations

                                  -

                                  DCS Redis 3.0/4.0/5.0 instances are deployed in different modes. Therefore, the access control method varies.

                                  -
                                  • To control access to DCS Redis 3.0 instances, you can use security groups. Whitelists are not supported. Security group operations are described in this section.
                                  • To control access to DCS Redis 4.0/5.0 instances, you can use whitelists. Security groups are not supported. Whitelist operations are described in Managing IP Address Whitelist.
                                  -

                                  This section describes how to configure a security group for accessing a DCS instance within a VPC.

                                  +

                                  DCS helps you control access to your DCS instances in the following ways, depending on the deployment mode:

                                  +
                                  • To control access to DCS Redis 3.0 instances, you can use security groups. Whitelists are not supported. Security group operations are described in this section.
                                  • To control access to DCS Redis 4.0/5.0/6.0 instances, you can use whitelists. Security groups are not supported. Whitelist operations are described in Managing IP Address Whitelist.
                                  +

                                  The following describes how to configure security groups for intra-VPC access to DCS Redis 3.0 instances.

                                  Intra-VPC Access to DCS Redis 3.0 Instances

                                  An ECS can communicate with a DCS instance if they belong to the same VPC and security group rules are configured correctly.

                                  In addition, you must configure correct rules for the security groups of both the ECS and DCS instance so that you can access the instance through your client.

                                  • If the ECS and DCS instance are configured with the same security group, network access in the group is not restricted by default.
                                  • If the ECS and DCS instance are configured with different security groups, add security group rules to ensure that the ECS and DCS instance can access each other.
                                    • Suppose that the ECS on which the client runs belongs to security group sg-ECS, and the DCS instance that the client will access belongs to security group sg-DCS.
                                    • Suppose that the port number of the DCS service is 6379.
                                    • The remote end is a security group or an IP address.