From ab5f2db011f36fc44b36f59d548cbf7b59834c8d Mon Sep 17 00:00:00 2001 From: chenjunjie Date: Wed, 26 Feb 2025 10:24:22 +0000 Subject: [PATCH] DCS UMN 20240705 version MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Reviewed-by: Mützel, Andrea Co-authored-by: chenjunjie Co-committed-by: chenjunjie --- docs/dcs/umn/ALL_META.TXT.json | 869 ++++---- docs/dcs/umn/CLASS.TXT.json | 1081 ++++----- docs/dcs/umn/CacheCluster.html | 172 +- docs/dcs/umn/CacheMasterSlave.html | 36 +- docs/dcs/umn/CacheProxy.html | 2 + docs/dcs/umn/CacheSingleNode.html | 7 +- docs/dcs/umn/GlobalDRPolicy.html | 18 +- docs/dcs/umn/PurchasePreparation.html | 8 +- docs/dcs/umn/RedisDifference.html | 18 +- docs/dcs/umn/TagManagement.html | 5 +- docs/dcs/umn/dcs-faq-022025.html | 6 +- docs/dcs/umn/dcs-faq-0220330.html | 3 +- docs/dcs/umn/dcs-faq-0326021.html | 2 +- docs/dcs/umn/dcs-faq-0326024.html | 4 +- docs/dcs/umn/dcs-faq-0427057.html | 6 +- docs/dcs/umn/dcs-faq-0427081.html | 14 +- docs/dcs/umn/dcs-faq-0521003.html | 2 +- docs/dcs/umn/dcs-faq-0603001.html | 6 +- docs/dcs/umn/dcs-faq-0730001.html | 2 +- docs/dcs/umn/dcs-faq-0730009.html | 10 +- docs/dcs/umn/dcs-faq-0730010.html | 2 +- docs/dcs/umn/dcs-faq-0730014.html | 4 +- docs/dcs/umn/dcs-faq-0730021.html | 4 +- docs/dcs/umn/dcs-faq-0730026.html | 7 + docs/dcs/umn/dcs-faq-0730029.html | 2 +- docs/dcs/umn/dcs-faq-0730034.html | 2 +- docs/dcs/umn/dcs-faq-0730047.html | 91 +- docs/dcs/umn/dcs-faq-0730058.html | 2 +- docs/dcs/umn/dcs-faq-210721001.html | 2 +- docs/dcs/umn/dcs-faq-210721002.html | 13 - docs/dcs/umn/dcs-faq-211230001.html | 8 +- docs/dcs/umn/dcs-faq-221222.html | 4 +- docs/dcs/umn/dcs-migrate-0220411.html | 19 +- docs/dcs/umn/dcs-migrate-1117003.html | 47 +- docs/dcs/umn/dcs-migrate-demo02.html | 104 +- docs/dcs/umn/dcs-migrate-demo03.html | 64 + docs/dcs/umn/dcs-migration-0312001.html | 4 +- docs/dcs/umn/dcs-migration-0312002.html | 8 +- docs/dcs/umn/dcs-migration-0312003.html | 86 +- docs/dcs/umn/dcs-migration-0312004.html | 49 +- docs/dcs/umn/dcs-migration-0312005.html | 17 +- docs/dcs/umn/dcs-migration-0312006.html | 69 +- docs/dcs/umn/dcs-migration-0312007.html | 6 +- docs/dcs/umn/dcs-migration-0312008.html | 4 +- docs/dcs/umn/dcs-migration-0312010.html | 36 +- docs/dcs/umn/dcs-migration-0312011.html | 54 +- docs/dcs/umn/dcs-migration-0312017.html | 2 +- docs/dcs/umn/dcs-migration-0312018.html | 2 +- docs/dcs/umn/dcs-migration-0713001.html | 4 +- docs/dcs/umn/dcs-migration-090626001_0.html | 30 +- docs/dcs/umn/dcs-migration-090626002.html | 41 +- docs/dcs/umn/dcs-migration-1117001.html | 44 +- docs/dcs/umn/dcs-migration-190703002.html | 20 +- docs/dcs/umn/dcs-migration-190703003.html | 65 +- docs/dcs/umn/dcs-migration-211125001.html | 2 +- docs/dcs/umn/dcs-migration-230313.html | 4 +- docs/dcs/umn/dcs-pd-0220606.html | 28 + docs/dcs/umn/dcs-pd-0326003.html | 2 +- docs/dcs/umn/dcs-pd-0916002.html | 1053 +++++++-- docs/dcs/umn/dcs-pd-0916004.html | 550 ++--- docs/dcs/umn/dcs-pd-191224001.html | 16 +- docs/dcs/umn/dcs-pd-200312001.html | 2 + docs/dcs/umn/dcs-pd-200312003.html | 10 +- docs/dcs/umn/dcs-pd-200713005.html | 2 +- docs/dcs/umn/dcs-pd-200813002.html | 1939 ++++++++++++++--- docs/dcs/umn/dcs-pd-200813003.html | 366 +++- docs/dcs/umn/dcs-pd-200813004.html | 4 +- docs/dcs/umn/dcs-pd-200916001.html | 1848 +++++++++++++--- docs/dcs/umn/dcs-pd-210209002.html | 766 +++---- docs/dcs/umn/dcs-ug-023129.html | 10 +- docs/dcs/umn/dcs-ug-0312008.html | 4 +- docs/dcs/umn/dcs-ug-0312009.html | 9 +- docs/dcs/umn/dcs-ug-0312010.html | 38 +- docs/dcs/umn/dcs-ug-0312011.html | 28 +- docs/dcs/umn/dcs-ug-0312012.html | 59 +- docs/dcs/umn/dcs-ug-0312013.html | 14 +- docs/dcs/umn/dcs-ug-0312016.html | 19 +- docs/dcs/umn/dcs-ug-0312017.html | 4 +- docs/dcs/umn/dcs-ug-0312018.html | 2 +- docs/dcs/umn/dcs-ug-0312019.html | 2 +- docs/dcs/umn/dcs-ug-0312022.html | 12 +- docs/dcs/umn/dcs-ug-0312024.html | 108 +- docs/dcs/umn/dcs-ug-0312025.html | 2 +- docs/dcs/umn/dcs-ug-0312026.html | 4 +- docs/dcs/umn/dcs-ug-0312028.html | 4 +- docs/dcs/umn/dcs-ug-0312029.html | 19 - docs/dcs/umn/dcs-ug-0312031.html | 4 +- docs/dcs/umn/dcs-ug-0312032.html | 2 +- docs/dcs/umn/dcs-ug-0312033.html | 2 +- docs/dcs/umn/dcs-ug-0312034.html | 4 +- docs/dcs/umn/dcs-ug-0312035.html | 2 + docs/dcs/umn/dcs-ug-0312036.html | 97 +- docs/dcs/umn/dcs-ug-0312037.html | 14 +- docs/dcs/umn/dcs-ug-0312038.html | 16 +- docs/dcs/umn/dcs-ug-0312039.html | 4 + docs/dcs/umn/dcs-ug-0312040.html | 2 +- docs/dcs/umn/dcs-ug-0312041.html | 23 + docs/dcs/umn/dcs-ug-0312042.html | 20 + docs/dcs/umn/dcs-ug-0312045.html | 2 +- docs/dcs/umn/dcs-ug-0312047.html | 2 +- docs/dcs/umn/dcs-ug-0326007.html | 2 +- docs/dcs/umn/dcs-ug-0326008.html | 24 +- docs/dcs/umn/dcs-ug-0326009.html | 26 +- docs/dcs/umn/dcs-ug-0326011.html | 154 +- docs/dcs/umn/dcs-ug-0326013.html | 4 +- docs/dcs/umn/dcs-ug-0326014.html | 4 +- docs/dcs/umn/dcs-ug-0326018.html | 51 +- docs/dcs/umn/dcs-ug-0326019.html | 1904 +++++++--------- docs/dcs/umn/dcs-ug-0326026.html | 43 +- docs/dcs/umn/dcs-ug-0512002.html | 10 +- docs/dcs/umn/dcs-ug-0713005.html | 168 +- docs/dcs/umn/dcs-ug-0916002.html | 2 +- docs/dcs/umn/dcs-ug-1009001.html | 2 +- docs/dcs/umn/dcs-ug-1009002.html | 4 +- docs/dcs/umn/dcs-ug-190808001.html | 4 +- docs/dcs/umn/dcs-ug-190812001.html | 6 +- docs/dcs/umn/dcs-ug-190905001.html | 196 +- docs/dcs/umn/dcs-ug-190926001.html | 2 +- docs/dcs/umn/dcs-ug-210107001.html | 13 +- docs/dcs/umn/dcs-ug-210226001.html | 4 +- docs/dcs/umn/dcs-ug-210330002.html | 100 +- docs/dcs/umn/dcs-ug-210622002.html | 108 +- docs/dcs/umn/dcs-ug-210622003.html | 108 +- docs/dcs/umn/dcs-ug-210622004.html | 108 +- docs/dcs/umn/dcs-ug-210622005.html | 2 +- docs/dcs/umn/dcs-ug-210818001.html | 20 + docs/dcs/umn/dcs-ug-210820001.html | 43 + docs/dcs/umn/dcs-ug-211105001.html | 12 +- docs/dcs/umn/dcs-ug-211105002.html | 386 ++-- docs/dcs/umn/dcs-ug-211105003.html | 8 +- docs/dcs/umn/dcs-ug-211105004.html | 442 ++-- docs/dcs/umn/dcs-ug-211202001.html | 6 +- docs/dcs/umn/dcs-ug-211202002.html | 19 +- docs/dcs/umn/dcs-ug-22121.html | 20 + docs/dcs/umn/dcs-ug-221220.html | 64 + docs/dcs/umn/dcs_01_0001.html | 1354 ++++++++++++ docs/dcs/umn/en-us_image_0000001148443460.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001148443514.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001148603242.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001148603246.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001148603248.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001148603250.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001153500240.png | Bin 499 -> 0 bytes docs/dcs/umn/en-us_image_0000001194403147.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001194403149.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001194403151.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001194403153.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001194403155.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001194403157.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001194522775.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001194522893.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001194523039.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001194523043.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001194523045.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001194523047.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001194523049.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001194523107.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001195353813.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001196710703.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001206970621.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001241411631.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001273950310.png | Bin 0 -> 57794 bytes docs/dcs/umn/en-us_image_0000001383102132.png | Bin 46233 -> 0 bytes docs/dcs/umn/en-us_image_0000001407952686.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001408112658.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001433519397.png | Bin 0 -> 38677 bytes docs/dcs/umn/en-us_image_0000001457367809.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001457792613.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0000001681129365.png | Bin 1004 -> 0 bytes ...2.png => en-us_image_0000001785451408.png} | Bin docs/dcs/umn/en-us_image_0000001941980352.png | Bin 0 -> 19370 bytes docs/dcs/umn/en-us_image_0000001955094688.png | Bin 0 -> 21623 bytes docs/dcs/umn/en-us_image_0000001955154978.png | Bin 0 -> 6899 bytes ...2.png => en-us_image_0000001962038446.png} | Bin docs/dcs/umn/en-us_image_0000001963155450.png | Bin 0 -> 214 bytes ...1.png => en-us_image_0000001964418130.png} | Bin ...7.png => en-us_image_0000001964888588.png} | Bin docs/dcs/umn/en-us_image_0000001968993633.png | Bin 0 -> 4837 bytes docs/dcs/umn/en-us_image_0000001974534420.png | Bin 0 -> 504 bytes docs/dcs/umn/en-us_image_0000001990974029.png | Bin 0 -> 6777 bytes ...4.png => en-us_image_0000001999635737.png} | Bin ...2.png => en-us_image_0000002000818973.png} | Bin ...0.png => en-us_image_0000002001365365.png} | Bin docs/dcs/umn/en-us_image_0000002010627429.png | Bin 0 -> 23941 bytes ...6.png => en-us_image_0000002010628601.png} | Bin docs/dcs/umn/en-us_image_0000002128172684.png | Bin 0 -> 18723 bytes docs/dcs/umn/en-us_image_0000002128172688.png | Bin 0 -> 30847 bytes docs/dcs/umn/en-us_image_0000002163572305.png | Bin 0 -> 35992 bytes docs/dcs/umn/en-us_image_0000002163572313.png | Bin 0 -> 40849 bytes ...8443458.png => en-us_image_0143929918.png} | Bin docs/dcs/umn/en-us_image_0177654980.png | Bin 55218 -> 0 bytes docs/dcs/umn/en-us_image_0266235394.png | Bin 27559 -> 0 bytes docs/dcs/umn/en-us_image_0266235405.png | Bin 1004 -> 0 bytes docs/dcs/umn/en-us_image_0266235430.png | Bin 461 -> 0 bytes docs/dcs/umn/en-us_image_0266235441.png | Bin 29535 -> 0 bytes docs/dcs/umn/en-us_image_0266235508.png | Bin 271 -> 0 bytes docs/dcs/umn/en-us_image_0293282054.png | Bin 46568 -> 0 bytes docs/dcs/umn/en-us_image_0296786164.png | Bin 16901 -> 0 bytes docs/dcs/umn/en-us_topic_0054235826.html | 9 +- docs/dcs/umn/en-us_topic_0054235835.html | 2 +- docs/dcs/umn/en-us_topic_0079835992.html | 14 +- docs/dcs/umn/en-us_topic_0090662012.html | 2 +- 202 files changed, 10686 insertions(+), 5075 deletions(-) delete mode 100644 docs/dcs/umn/dcs-faq-210721002.html create mode 100644 docs/dcs/umn/dcs-migrate-demo03.html create mode 100644 docs/dcs/umn/dcs-pd-0220606.html delete mode 100644 docs/dcs/umn/dcs-ug-0312029.html create mode 100644 docs/dcs/umn/dcs-ug-0312041.html create mode 100644 docs/dcs/umn/dcs-ug-0312042.html create mode 100644 docs/dcs/umn/dcs-ug-210818001.html create mode 100644 docs/dcs/umn/dcs-ug-210820001.html create mode 100644 docs/dcs/umn/dcs-ug-22121.html create mode 100644 docs/dcs/umn/dcs-ug-221220.html create mode 100644 docs/dcs/umn/dcs_01_0001.html delete mode 100644 docs/dcs/umn/en-us_image_0000001148443460.png delete mode 100644 docs/dcs/umn/en-us_image_0000001148443514.png delete mode 100644 docs/dcs/umn/en-us_image_0000001148603242.png delete mode 100644 docs/dcs/umn/en-us_image_0000001148603246.png delete mode 100644 docs/dcs/umn/en-us_image_0000001148603248.png delete mode 100644 docs/dcs/umn/en-us_image_0000001148603250.png delete mode 100644 docs/dcs/umn/en-us_image_0000001153500240.png delete mode 100644 docs/dcs/umn/en-us_image_0000001194403147.png delete mode 100644 docs/dcs/umn/en-us_image_0000001194403149.png delete mode 100644 docs/dcs/umn/en-us_image_0000001194403151.png delete mode 100644 docs/dcs/umn/en-us_image_0000001194403153.png delete mode 100644 docs/dcs/umn/en-us_image_0000001194403155.png delete mode 100644 docs/dcs/umn/en-us_image_0000001194403157.png delete mode 100644 docs/dcs/umn/en-us_image_0000001194522775.png delete mode 100644 docs/dcs/umn/en-us_image_0000001194522893.png delete mode 100644 docs/dcs/umn/en-us_image_0000001194523039.png delete mode 100644 docs/dcs/umn/en-us_image_0000001194523043.png delete mode 100644 docs/dcs/umn/en-us_image_0000001194523045.png delete mode 100644 docs/dcs/umn/en-us_image_0000001194523047.png delete mode 100644 docs/dcs/umn/en-us_image_0000001194523049.png delete mode 100644 docs/dcs/umn/en-us_image_0000001194523107.png delete mode 100644 docs/dcs/umn/en-us_image_0000001195353813.png delete mode 100644 docs/dcs/umn/en-us_image_0000001196710703.png delete mode 100644 docs/dcs/umn/en-us_image_0000001206970621.png delete mode 100644 docs/dcs/umn/en-us_image_0000001241411631.png create mode 100644 docs/dcs/umn/en-us_image_0000001273950310.png delete mode 100644 docs/dcs/umn/en-us_image_0000001383102132.png delete mode 100644 docs/dcs/umn/en-us_image_0000001407952686.png delete mode 100644 docs/dcs/umn/en-us_image_0000001408112658.png create mode 100644 docs/dcs/umn/en-us_image_0000001433519397.png delete mode 100644 docs/dcs/umn/en-us_image_0000001457367809.png delete mode 100644 docs/dcs/umn/en-us_image_0000001457792613.png delete mode 100644 docs/dcs/umn/en-us_image_0000001681129365.png rename docs/dcs/umn/{en-us_image_0000001318437462.png => en-us_image_0000001785451408.png} (100%) create mode 100644 docs/dcs/umn/en-us_image_0000001941980352.png create mode 100644 docs/dcs/umn/en-us_image_0000001955094688.png create mode 100644 docs/dcs/umn/en-us_image_0000001955154978.png rename docs/dcs/umn/{en-us_image_0000001148443452.png => en-us_image_0000001962038446.png} (100%) create mode 100644 docs/dcs/umn/en-us_image_0000001963155450.png rename docs/dcs/umn/{en-us_image_0000001420151641.png => en-us_image_0000001964418130.png} (100%) rename docs/dcs/umn/{en-us_image_0000001420267897.png => en-us_image_0000001964888588.png} (100%) create mode 100644 docs/dcs/umn/en-us_image_0000001968993633.png create mode 100644 docs/dcs/umn/en-us_image_0000001974534420.png create mode 100644 docs/dcs/umn/en-us_image_0000001990974029.png rename docs/dcs/umn/{en-us_image_0000001148443454.png => en-us_image_0000001999635737.png} (100%) rename docs/dcs/umn/{en-us_image_0177653842.png => en-us_image_0000002000818973.png} (100%) rename docs/dcs/umn/{en-us_image_0177600650.png => en-us_image_0000002001365365.png} (100%) create mode 100644 docs/dcs/umn/en-us_image_0000002010627429.png rename docs/dcs/umn/{en-us_image_0000001148443456.png => en-us_image_0000002010628601.png} (100%) create mode 100644 docs/dcs/umn/en-us_image_0000002128172684.png create mode 100644 docs/dcs/umn/en-us_image_0000002128172688.png create mode 100644 docs/dcs/umn/en-us_image_0000002163572305.png create mode 100644 docs/dcs/umn/en-us_image_0000002163572313.png rename docs/dcs/umn/{en-us_image_0000001148443458.png => en-us_image_0143929918.png} (100%) delete mode 100644 docs/dcs/umn/en-us_image_0177654980.png delete mode 100644 docs/dcs/umn/en-us_image_0266235394.png delete mode 100644 docs/dcs/umn/en-us_image_0266235405.png delete mode 100644 docs/dcs/umn/en-us_image_0266235430.png delete mode 100644 docs/dcs/umn/en-us_image_0266235441.png delete mode 100644 docs/dcs/umn/en-us_image_0266235508.png delete mode 100644 docs/dcs/umn/en-us_image_0293282054.png delete mode 100644 docs/dcs/umn/en-us_image_0296786164.png diff --git a/docs/dcs/umn/ALL_META.TXT.json b/docs/dcs/umn/ALL_META.TXT.json index 93394609b..c5953c9e1 100644 --- a/docs/dcs/umn/ALL_META.TXT.json +++ b/docs/dcs/umn/ALL_META.TXT.json @@ -170,11 +170,32 @@ "title":"Redis Cluster", "githuburl":"" }, + { + "uri":"dcs-pd-0220606.html", + "node_id":"dcs-pd-0220606.xml", + "product_code":"dcs", + "code":"9", + "des":"This section describes read/write splitting DCS Redis 4.0/5.0 instances. Read/write splitting is implemented on the server side by default. Proxies distinguish between re", + "doc_type":"usermanual", + "kw":"Read/Write Splitting Redis,DCS Instance Types,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dcs", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"Yes", + "IsBot":"Yes" + } + ], + "title":"Read/Write Splitting Redis", + "githuburl":"" + }, { "uri":"dcs-pd-191224001.html", "node_id":"dcs-pd-191224001.xml", "product_code":"dcs", - "code":"9", + "code":"10", "des":"Table 1 describes the differences between different Redis instance types in terms of features and commands.", "doc_type":"usermanual", "kw":"Comparing DCS Redis Instance Types,DCS Instance Types,User Guide", @@ -195,7 +216,7 @@ "uri":"en-us_topic_0054235835.html", "node_id":"en-us_topic_0054235835.xml", "product_code":"dcs", - "code":"10", + "code":"11", "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", @@ -216,7 +237,7 @@ "uri":"dcs-pd-0916001.html", "node_id":"dcs-pd-0916001.xml", "product_code":"dcs", - "code":"11", + "code":"12", "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,", @@ -237,7 +258,7 @@ "uri":"dcs-pd-0916002.html", "node_id":"dcs-pd-0916002.xml", "product_code":"dcs", - "code":"12", + "code":"13", "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", @@ -258,10 +279,10 @@ "uri":"dcs-pd-0916004.html", "node_id":"dcs-pd-0916004.xml", "product_code":"dcs", - "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", + "code":"14", + "des":"This section describes DCS Redis 6.0/7.0 instance specifications, including the total memory, available memory, maximum number of connections allowed, maximum/assured ban", "doc_type":"usermanual", - "kw":"DCS Redis 6.0 instance specifications,Redis 6.0 Instance Specifications,DCS Instance Specifications,", + "kw":"DCS Redis 6.0/7.0 instance specifications,Redis 6.0 and 7.0 Instance Specifications,DCS Instance Spe", "search_title":"", "metedata":[ { @@ -272,14 +293,14 @@ "IsBot":"Yes" } ], - "title":"Redis 6.0 Instance Specifications", + "title":"Redis 6.0 and 7.0 Instance Specifications", "githuburl":"" }, { "uri":"dcs-pd-200312003.html", "node_id":"dcs-pd-200312003.xml", "product_code":"dcs", - "code":"14", + "code":"15", "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", @@ -300,10 +321,10 @@ "uri":"dcs-pd-200713005.html", "node_id":"dcs-pd-200713005.xml", "product_code":"dcs", - "code":"15", + "code":"16", "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", + "kw":"Commands Supported and Disabled by DCS for Redis 3.0,Command Compatibility,User Guide", "search_title":"", "metedata":[ { @@ -314,17 +335,17 @@ "IsBot":"Yes" } ], - "title":"Redis 3.0 Commands", + "title":"Commands Supported and Disabled by DCS for Redis 3.0", "githuburl":"" }, { "uri":"dcs-pd-200916001.html", "node_id":"dcs-pd-200916001.xml", "product_code":"dcs", - "code":"16", + "code":"17", "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", + "kw":"Commands Supported and Disabled by DCS for Redis 4.0,Command Compatibility,User Guide", "search_title":"", "metedata":[ { @@ -335,17 +356,17 @@ "IsBot":"Yes" } ], - "title":"Redis 4.0 Commands", + "title":"Commands Supported and Disabled by DCS for Redis 4.0", "githuburl":"" }, { "uri":"dcs-pd-200813002.html", "node_id":"dcs-pd-200813002.xml", "product_code":"dcs", - "code":"17", + "code":"18", "des":"DCS for Redis 5.0 is developed based on Redis 5.0.14 and is compatible with open-source protocols and commands.This section describes DCS for Redis 5.0's compatibility wi", "doc_type":"usermanual", - "kw":"Redis 5.0 Commands,Command Compatibility,User Guide", + "kw":"Commands Supported and Disabled by DCS for Redis 5.0,Command Compatibility,User Guide", "search_title":"", "metedata":[ { @@ -356,17 +377,17 @@ "IsBot":"Yes" } ], - "title":"Redis 5.0 Commands", + "title":"Commands Supported and Disabled by DCS for Redis 5.0", "githuburl":"" }, { "uri":"dcs-pd-210209002.html", "node_id":"dcs-pd-210209002.xml", "product_code":"dcs", - "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", + "code":"19", + "des":"DCS for Redis 6.0 is fully compatible with open-source Redis 6.This section describes DCS for Redis 6.0's command compatibility, including supported and disabled commands", "doc_type":"usermanual", - "kw":"Redis 6.0 Commands,Command Compatibility,User Guide", + "kw":"Commands Supported and Disabled by DCS for Redis 6.0,Command Compatibility,User Guide", "search_title":"", "metedata":[ { @@ -377,14 +398,34 @@ "IsBot":"Yes" } ], - "title":"Redis 6.0 Commands", + "title":"Commands Supported and Disabled by DCS for Redis 6.0", + "githuburl":"" + }, + { + "uri":"dcs_01_0001.html", + "node_id":"dcs_01_0001.xml", + "product_code":"dcs", + "code":"20", + "des":"This section describes DCS for Redis 7.0's compatibility with KeyDB commands, including supported and disabled commands.DCS Redis instances support most Redis commands. A", + "doc_type":"usermanual", + "kw":"Commands Supported and Disabled by DCS for Redis 7.0,Command Compatibility,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dcs", + "documenttype":"usermanual", + "IsMulti":"Yes", + "opensource":"true" + } + ], + "title":"Commands Supported and Disabled by DCS for Redis 7.0", "githuburl":"" }, { "uri":"dcs-pd-190826001.html", "node_id":"dcs-pd-190826001.xml", "product_code":"dcs", - "code":"19", + "code":"21", "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", @@ -405,7 +446,7 @@ "uri":"dcs-pd-200813003.html", "node_id":"dcs-pd-200813003.xml", "product_code":"dcs", - "code":"20", + "code":"22", "des":"Some Redis commands are supported by Redis Cluster DCS instances for multi-key operations in the same slot. For details, see Table 1.Some commands support multiple keys b", "doc_type":"usermanual", "kw":"Command Restrictions,Command Compatibility,User Guide", @@ -426,7 +467,7 @@ "uri":"dcs-pd-200813004.html", "node_id":"dcs-pd-200813004.xml", "product_code":"dcs", - "code":"21", + "code":"23", "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", @@ -447,7 +488,7 @@ "uri":"GlobalDRPolicy.html", "node_id":"globaldrpolicy.xml", "product_code":"dcs", - "code":"22", + "code":"24", "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":"Disaster Recovery and Multi-Active Solution,Service Overview,User Guide", @@ -468,8 +509,8 @@ "uri":"RedisDifference.html", "node_id":"redisdifference.xml", "product_code":"dcs", - "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", + "code":"25", + "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/7.0. The following table descr", "doc_type":"usermanual", "kw":"Comparing Redis Versions,Service Overview,User Guide", "search_title":"", @@ -489,7 +530,7 @@ "uri":"dcs-pd-0326003.html", "node_id":"dcs-pd-0326003.xml", "product_code":"dcs", - "code":"24", + "code":"26", "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", @@ -510,7 +551,7 @@ "uri":"dcs-pd-200312004.html", "node_id":"dcs-pd-200312004.xml", "product_code":"dcs", - "code":"25", + "code":"27", "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", @@ -531,7 +572,7 @@ "uri":"dcs-pd-210626001.html", "node_id":"dcs-pd-210626001.xml", "product_code":"dcs", - "code":"26", + "code":"28", "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,Service Overview,User Guide", @@ -552,7 +593,7 @@ "uri":"dcs-pd-0326006.html", "node_id":"dcs-pd-0326006.xml", "product_code":"dcs", - "code":"27", + "code":"29", "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", @@ -573,7 +614,7 @@ "uri":"en-us_topic_0054235836.html", "node_id":"en-us_topic_0054235836.xml", "product_code":"dcs", - "code":"28", + "code":"30", "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", @@ -594,7 +635,7 @@ "uri":"en-us_topic_0054235837.html", "node_id":"en-us_topic_0054235837.xml", "product_code":"dcs", - "code":"29", + "code":"31", "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", @@ -615,7 +656,7 @@ "uri":"en-us_topic_0054247786.html", "node_id":"en-us_topic_0054247786.xml", "product_code":"dcs", - "code":"30", + "code":"32", "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", @@ -636,7 +677,7 @@ "uri":"dcs-ug-210626003.html", "node_id":"dcs-ug-210626003.xml", "product_code":"dcs", - "code":"31", + "code":"33", "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", @@ -657,7 +698,7 @@ "uri":"dcs-ug-210626004.html", "node_id":"dcs-ug-210626004.xml", "product_code":"dcs", - "code":"32", + "code":"34", "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", @@ -678,7 +719,7 @@ "uri":"dcs-ug-210626005.html", "node_id":"dcs-ug-210626005.xml", "product_code":"dcs", - "code":"33", + "code":"35", "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", @@ -699,7 +740,7 @@ "uri":"dcs-ug-0326007.html", "node_id":"dcs-ug-0326007.xml", "product_code":"dcs", - "code":"34", + "code":"36", "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", @@ -720,7 +761,7 @@ "uri":"dcs-ug-0312003.html", "node_id":"dcs-ug-0312003.xml", "product_code":"dcs", - "code":"35", + "code":"37", "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", @@ -741,7 +782,7 @@ "uri":"PurchasePreparation.html", "node_id":"purchasepreparation.xml", "product_code":"dcs", - "code":"36", + "code":"38", "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", @@ -762,7 +803,7 @@ "uri":"dcs-ug-0312004.html", "node_id":"dcs-ug-0312004.xml", "product_code":"dcs", - "code":"37", + "code":"39", "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 Required Resources,Creating an Instance,User Guide", @@ -783,7 +824,7 @@ "uri":"dcs-ug-0326008.html", "node_id":"dcs-ug-0326008.xml", "product_code":"dcs", - "code":"38", + "code":"40", "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", @@ -804,7 +845,7 @@ "uri":"dcs-ug-0916002.html", "node_id":"dcs-ug-0916002.xml", "product_code":"dcs", - "code":"39", + "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":"usermanual", "kw":"Accessing an Instance", @@ -825,8 +866,8 @@ "uri":"dcs-ug-0326009.html", "node_id":"dcs-ug-0326009.xml", "product_code":"dcs", - "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 ", + "code":"42", + "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.The follow", "doc_type":"usermanual", "kw":"Accessing a DCS Redis Instance Through redis-cli,Accessing an Instance,User Guide", "search_title":"", @@ -846,7 +887,7 @@ "uri":"dcs-ug-0512002.html", "node_id":"dcs-ug-0512002.xml", "product_code":"dcs", - "code":"41", + "code":"43", "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":"Access in Different Languages", @@ -867,7 +908,7 @@ "uri":"dcs-ug-211105003.html", "node_id":"dcs-ug-211105003.xml", "product_code":"dcs", - "code":"42", + "code":"44", "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", @@ -888,10 +929,10 @@ "uri":"dcs-ug-0713005.html", "node_id":"dcs-ug-0713005.xml", "product_code":"dcs", - "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.Spring Da", + "code":"45", + "des":"This section describes how to access a Redis instance on Jedis. For more information about how to use other Redis clients, visit the Redis official website.Spring Data Re", "doc_type":"usermanual", - "kw":"Access a DCS Redis instance through Jedis,Jedis,Java,User Guide", + "kw":"Connecting to Redis on Jedis (Java),Java,User Guide", "search_title":"", "metedata":[ { @@ -902,17 +943,17 @@ "IsBot":"Yes" } ], - "title":"Jedis", + "title":"Connecting to Redis on Jedis (Java)", "githuburl":"" }, { "uri":"dcs-ug-211105002.html", "node_id":"dcs-ug-211105002.xml", "product_code":"dcs", - "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.Spring ", + "code":"46", + "des":"This section describes how to access a Redis instance on Lettuce. For more information about how to use other Redis clients, visit the Redis official website.Spring Data ", "doc_type":"usermanual", - "kw":"Access a DCS Redis instance through Lettuce,Lettuce,Java,User Guide", + "kw":"Connecting to Redis on Lettuce (Java),Java,User Guide", "search_title":"", "metedata":[ { @@ -923,17 +964,17 @@ "IsBot":"Yes" } ], - "title":"Lettuce", + "title":"Connecting to Redis on Lettuce (Java)", "githuburl":"" }, { "uri":"dcs-ug-211105004.html", "node_id":"dcs-ug-211105004.xml", "product_code":"dcs", - "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.For Sp", + "code":"47", + "des":"This section describes how to access a Redis instance on Redisson. For more information about how to use other Redis clients, visit the Redis official website.For Spring ", "doc_type":"usermanual", - "kw":"Access a DCS Redis instance through Redisson,Redisson,Java,User Guide", + "kw":"Connecting to Redis on Redisson (Java),Java,User Guide", "search_title":"", "metedata":[ { @@ -944,17 +985,17 @@ "IsBot":"Yes" } ], - "title":"Redisson", + "title":"Connecting to Redis on Redisson (Java)", "githuburl":"" }, { "uri":"dcs-ug-0312011.html", "node_id":"dcs-ug-0312011.xml", "product_code":"dcs", - "code":"46", - "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", + "code":"48", + "des":"This section describes how to access a Redis instance on redis-py. For more information about how to use other Redis clients, visit the Redis official website.The followi", "doc_type":"usermanual", - "kw":"redis-py,Clients in Python,Access in Different Languages,User Guide", + "kw":"Connecting to Redis on redis-py (Python),Access in Different Languages,User Guide", "search_title":"", "metedata":[ { @@ -965,17 +1006,17 @@ "IsBot":"Yes" } ], - "title":"Clients in Python", + "title":"Connecting to Redis on redis-py (Python)", "githuburl":"" }, { "uri":"dcs-ug-211105001.html", "node_id":"dcs-ug-211105001.xml", "product_code":"dcs", - "code":"47", - "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 ", + "code":"49", + "des":"This section describes how to access a Redis instance on go-redis. For more information about how to use other Redis clients, visit the Redis official website.The followi", "doc_type":"usermanual", - "kw":"Access a DCS Redis instance through go-redis,go-redis,Access in Different Languages,User Guide", + "kw":"Connecting to Redis on go-redis (Go),Access in Different Languages,User Guide", "search_title":"", "metedata":[ { @@ -986,17 +1027,17 @@ "IsBot":"Yes" } ], - "title":"go-redis", + "title":"Connecting to Redis on go-redis (Go)", "githuburl":"" }, { "uri":"dcs-ug-0312010.html", "node_id":"dcs-ug-0312010.xml", "product_code":"dcs", - "code":"48", - "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", + "code":"50", + "des":"This section describes how to access a Redis instance on hiredis (C++). For more information about how to use other Redis clients, visit the Redis official website.The fo", "doc_type":"usermanual", - "kw":"Access a DCS Redis instance through hiredis,hiredis in C++,Access in Different Languages,User Guide", + "kw":"Connecting to Redis on hiredis (C++),Access in Different Languages,User Guide", "search_title":"", "metedata":[ { @@ -1007,17 +1048,17 @@ "IsBot":"Yes" } ], - "title":"hiredis in C++", + "title":"Connecting to Redis on hiredis (C++)", "githuburl":"" }, { "uri":"dcs-ug-0312013.html", "node_id":"dcs-ug-0312013.xml", "product_code":"dcs", - "code":"49", - "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", + "code":"51", + "des":"This section describes how to access a Redis instance on StackExchange.Redis. For more information about how to use other Redis clients, visit the Redis official website.", "doc_type":"usermanual", - "kw":"C# Client StackExchange.Redis,C#,Access in Different Languages,User Guide", + "kw":"Connecting to Redis on StackExchange.Redis (C#),Access in Different Languages,User Guide", "search_title":"", "metedata":[ { @@ -1028,14 +1069,14 @@ "IsBot":"Yes" } ], - "title":"C#", + "title":"Connecting to Redis on StackExchange.Redis (C#)", "githuburl":"" }, { "uri":"dcs-ug-211202001.html", "node_id":"dcs-ug-211202001.xml", "product_code":"dcs", - "code":"50", + "code":"52", "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", @@ -1056,10 +1097,10 @@ "uri":"dcs-ug-0312009.html", "node_id":"dcs-ug-0312009.xml", "product_code":"dcs", - "code":"51", - "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", + "code":"53", + "des":"This section describes how to connect to Redis on phpredis. For more information about how to use other Redis clients, visit the Redis official website.The following oper", "doc_type":"usermanual", - "kw":"Access a DCS Redis instance through phpredis,phpredis,PHP,User Guide", + "kw":"Connecting to Redis on phpredis (PHP),PHP,User Guide", "search_title":"", "metedata":[ { @@ -1070,17 +1111,17 @@ "IsBot":"Yes" } ], - "title":"phpredis", + "title":"Connecting to Redis on phpredis (PHP)", "githuburl":"" }, { "uri":"dcs-ug-211202002.html", "node_id":"dcs-ug-211202002.xml", "product_code":"dcs", - "code":"52", - "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", + "code":"54", + "des":"This section describes how to connect to Redis on predis. For more information about how to use other Redis clients, visit the Redis official website.The following operat", "doc_type":"usermanual", - "kw":"Access a DCS Redis instance through Predis,Predis,PHP,User Guide", + "kw":"Connecting to Redis on predis (PHP),PHP,User Guide", "search_title":"", "metedata":[ { @@ -1091,17 +1132,17 @@ "IsBot":"Yes" } ], - "title":"Predis", + "title":"Connecting to Redis on predis (PHP)", "githuburl":"" }, { "uri":"dcs-ug-0312012.html", "node_id":"dcs-ug-0312012.xml", "product_code":"dcs", - "code":"53", - "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", + "code":"55", + "des":"This section describes how to access a Redis instance on ioredis. For more information about how to use other Redis clients, visit the Redis official website.The followin", "doc_type":"usermanual", - "kw":"Node.js,Node.js,Access in Different Languages,User Guide", + "kw":"Connecting to Redis on ioredis (Node.js),Access in Different Languages,User Guide", "search_title":"", "metedata":[ { @@ -1112,17 +1153,17 @@ "IsBot":"Yes" } ], - "title":"Node.js", + "title":"Connecting to Redis on ioredis (Node.js)", "githuburl":"" }, { "uri":"dcs-ug-0312008.html", "node_id":"dcs-ug-0312008.xml", "product_code":"dcs", - "code":"54", + "code":"56", "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/5.0/6.0 Instance on the Console,Accessing an In", + "kw":"Access a DCS Redis,Web CLI,Accessing a DCS Redis Instance on the Console,Accessing an Instance,User ", "search_title":"", "metedata":[ { @@ -1133,17 +1174,17 @@ "IsBot":"Yes" } ], - "title":"Accessing a DCS Redis 4.0/5.0/6.0 Instance on the Console", + "title":"Accessing a DCS Redis Instance on the Console", "githuburl":"" }, { "uri":"dcs-ug-0312016.html", "node_id":"dcs-ug-0312016.xml", "product_code":"dcs", - "code":"55", + "code":"57", "des":"On the DCS console, you can view DCS instance details.Search by keyword.If you do not select an attribute and enter a keyword in the search box, the system searches for i", "doc_type":"usermanual", - "kw":"view DCS,Viewing Details of a DCS Instance,Getting Started,User Guide", + "kw":"view DCS,Viewing and Modifying DCS Instance Information,Getting Started,User Guide", "search_title":"", "metedata":[ { @@ -1154,14 +1195,14 @@ "IsBot":"Yes" } ], - "title":"Viewing Details of a DCS Instance", + "title":"Viewing and Modifying DCS Instance Information", "githuburl":"" }, { "uri":"dcs-ug-0312015.html", "node_id":"dcs-ug-0312015.xml", "product_code":"dcs", - "code":"56", + "code":"58", "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", @@ -1182,7 +1223,7 @@ "uri":"dcs-ug-0326011.html", "node_id":"dcs-ug-0326011.xml", "product_code":"dcs", - "code":"57", + "code":"59", "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 the modification failed in", "doc_type":"usermanual", "kw":"Modifying DCS Instance Specifications,Operating DCS Instances,User Guide", @@ -1203,7 +1244,7 @@ "uri":"dcs-ug-0911001.html", "node_id":"dcs-ug-0911001.xml", "product_code":"dcs", - "code":"58", + "code":"60", "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", @@ -1224,8 +1265,8 @@ "uri":"dcs-ug-0326013.html", "node_id":"dcs-ug-0326013.xml", "product_code":"dcs", - "code":"59", - "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 ", + "code":"61", + "des":"On the DCS console, you can restart one or multiple DCS instances at a time.Restarting a single-node DCS instance or other types of DCS instances with AOF persistence dis", "doc_type":"usermanual", "kw":"restart one or multiple DCS instances,Restarting DCS Instances,Operating DCS Instances,User Guide", "search_title":"", @@ -1245,7 +1286,7 @@ "uri":"dcs-ug-0326014.html", "node_id":"dcs-ug-0326014.xml", "product_code":"dcs", - "code":"60", + "code":"62", "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", @@ -1266,7 +1307,7 @@ "uri":"dcs-ug-0312017.html", "node_id":"dcs-ug-0312017.xml", "product_code":"dcs", - "code":"61", + "code":"63", "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", @@ -1287,7 +1328,7 @@ "uri":"dcs-ug-0312018.html", "node_id":"dcs-ug-0312018.xml", "product_code":"dcs", - "code":"62", + "code":"64", "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", @@ -1308,7 +1349,7 @@ "uri":"dcs-ug-0312019.html", "node_id":"dcs-ug-0312019.xml", "product_code":"dcs", - "code":"63", + "code":"65", "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", @@ -1329,7 +1370,7 @@ "uri":"dcs-ug-1009002.html", "node_id":"dcs-ug-1009002.xml", "product_code":"dcs", - "code":"64", + "code":"66", "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, FLUSHALL, HGE", "doc_type":"usermanual", "kw":"Command Renaming,Operating DCS Instances,User Guide", @@ -1350,7 +1391,7 @@ "uri":"dcs-ug-0312022.html", "node_id":"dcs-ug-0312022.xml", "product_code":"dcs", - "code":"65", + "code":"67", "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", @@ -1371,7 +1412,7 @@ "uri":"dcs-ug-0312023.html", "node_id":"dcs-ug-0312023.xml", "product_code":"dcs", - "code":"66", + "code":"68", "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", @@ -1392,7 +1433,7 @@ "uri":"dcs-ug-0312024.html", "node_id":"dcs-ug-0312024.xml", "product_code":"dcs", - "code":"67", + "code":"69", "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", @@ -1413,7 +1454,7 @@ "uri":"dcs-ug-0312025.html", "node_id":"dcs-ug-0312025.xml", "product_code":"dcs", - "code":"68", + "code":"70", "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", @@ -1434,7 +1475,7 @@ "uri":"dcs-ug-0312026.html", "node_id":"dcs-ug-0312026.xml", "product_code":"dcs", - "code":"69", + "code":"71", "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", @@ -1455,7 +1496,7 @@ "uri":"dcs-ug-0312028.html", "node_id":"dcs-ug-0312028.xml", "product_code":"dcs", - "code":"70", + "code":"72", "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", @@ -1472,32 +1513,11 @@ "title":"Viewing Background Tasks", "githuburl":"" }, - { - "uri":"dcs-ug-0312029.html", - "node_id":"dcs-ug-0312029.xml", - "product_code":"dcs", - "code":"71", - "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", - "search_title":"", - "metedata":[ - { - "prodname":"dcs", - "opensource":"true", - "documenttype":"usermanual", - "IsMulti":"Yes", - "IsBot":"Yes" - } - ], - "title":"Viewing Data Storage Statistics of a DCS Redis 3.0 Proxy Cluster Instance", - "githuburl":"" - }, { "uri":"TagManagement.html", "node_id":"tagmanagement.xml", "product_code":"dcs", - "code":"72", + "code":"73", "des":"Tags facilitate DCS instance identification and management.You can add tags to an instance when creating it or add, modify, or delete tags on the details page of a create", "doc_type":"usermanual", "kw":"Managing Tags,Managing DCS Instances,User Guide", @@ -1518,8 +1538,8 @@ "uri":"dcs-ug-210107001.html", "node_id":"dcs-ug-210107001.xml", "product_code":"dcs", - "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", + "code":"74", + "des":"This section describes how to query the shards and replicas of a DCS Redis 4.0 or later instance and how to manually promote a replica to master.Currently, this function ", "doc_type":"usermanual", "kw":"Managing Shards and Replicas,Managing DCS Instances,User Guide", "search_title":"", @@ -1539,7 +1559,7 @@ "uri":"dcs-ug-190808001.html", "node_id":"dcs-ug-190808001.xml", "product_code":"dcs", - "code":"74", + "code":"75", "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":"Analyzing Big Keys and Hot Keys,Managing DCS Instances,User Guide", @@ -1560,10 +1580,10 @@ "uri":"dcs-ug-210330002.html", "node_id":"dcs-ug-210330002.xml", "product_code":"dcs", - "code":"75", + "code":"76", "des":"There are two ways to delete a key in Redis.Use the DEL command to directly delete a key.Use commands such as EXPIRE to set a timeout on a key. After the timeout elapses,", "doc_type":"usermanual", - "kw":"Scanning Expired Keys,Managing DCS Instances,User Guide", + "kw":"Scanning and Deleting Expired Keys in a DCS Redis Instance,Managing DCS Instances,User Guide", "search_title":"", "metedata":[ { @@ -1574,14 +1594,14 @@ "IsBot":"Yes" } ], - "title":"Scanning Expired Keys", + "title":"Scanning and Deleting Expired Keys in a DCS Redis Instance", "githuburl":"" }, { "uri":"dcs-ug-190812001.html", "node_id":"dcs-ug-190812001.xml", "product_code":"dcs", - "code":"76", + "code":"77", "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", @@ -1602,7 +1622,7 @@ "uri":"dcs-ug-190926001.html", "node_id":"dcs-ug-190926001.xml", "product_code":"dcs", - "code":"77", + "code":"78", "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 Queries,Managing DCS Instances,User Guide", @@ -1623,7 +1643,7 @@ "uri":"dcs-ug-1009001.html", "node_id":"dcs-ug-1009001.xml", "product_code":"dcs", - "code":"78", + "code":"79", "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", @@ -1641,13 +1661,13 @@ "githuburl":"" }, { - "uri":"dcs-ug-023129.html", - "node_id":"dcs-ug-023129.xml", + "uri":"dcs-ug-210818001.html", + "node_id":"dcs-ug-210818001.xml", "product_code":"dcs", - "code":"79", - "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 ", + "code":"80", + "des":"If a fault or performance issue occurs, you can ask DCS to diagnose your instance to learn about the cause and impact of the issue and how to handle it.Tested Object: You", "doc_type":"usermanual", - "kw":"Configuring SSL,Managing DCS Instances,User Guide", + "kw":"Diagnosing an Instance,Managing DCS Instances,User Guide", "search_title":"", "metedata":[ { @@ -1658,14 +1678,75 @@ "IsBot":"Yes" } ], - "title":"Configuring SSL", + "title":"Diagnosing an Instance", + "githuburl":"" + }, + { + "uri":"dcs-ug-023129.html", + "node_id":"dcs-ug-023129.xml", + "product_code":"dcs", + "code":"81", + "des":"Single-node, master/standby, and Redis ClusterDCS Redis 6.0/7.0instances support SSL encryption to ensure data transmission security. This function is not available for o", + "doc_type":"usermanual", + "kw":"Transmitting DCS Redis Data with Encryption Using SSL,Managing DCS Instances,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dcs", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"Yes", + "IsBot":"Yes" + } + ], + "title":"Transmitting DCS Redis Data with Encryption Using SSL", + "githuburl":"" + }, + { + "uri":"dcs-ug-22121.html", + "node_id":"dcs-ug-22121.xml", + "product_code":"dcs", + "code":"82", + "des":"You can view the client connection information of an instance and disconnect clients.This function is supported by DCS Redis 4.0 instances and later.The session managemen", + "doc_type":"usermanual", + "kw":"Managing Sessions,Managing DCS Instances,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dcs", + "documenttype":"usermanual", + "IsMulti":"Yes", + "opensource":"true" + } + ], + "title":"Managing Sessions", + "githuburl":"" + }, + { + "uri":"dcs-ug-221220.html", + "node_id":"dcs-ug-221220.xml", + "product_code":"dcs", + "code":"83", + "des":"You can create read-only and read/write users to control access permissions.This function is supported only by DCS Redis 4.0 and 5.0 instances.Default user: defaultA maxi", + "doc_type":"usermanual", + "kw":"Managing Users,Managing DCS Instances,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dcs", + "documenttype":"usermanual", + "IsMulti":"Yes", + "opensource":"true" + } + ], + "title":"Managing Users", "githuburl":"" }, { "uri":"dcs-ug-0312030.html", "node_id":"dcs-ug-0312030.xml", "product_code":"dcs", - "code":"80", + "code":"84", "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", @@ -1686,7 +1767,7 @@ "uri":"en-us_topic_0079835992.html", "node_id":"en-us_topic_0079835992.xml", "product_code":"dcs", - "code":"81", + "code":"85", "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", @@ -1707,7 +1788,7 @@ "uri":"dcs-ug-0312031.html", "node_id":"dcs-ug-0312031.xml", "product_code":"dcs", - "code":"82", + "code":"86", "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 an Automatic Backup Policy,Backing Up and Restoring", @@ -1728,7 +1809,7 @@ "uri":"dcs-ug-0312032.html", "node_id":"dcs-ug-0312032.xml", "product_code":"dcs", - "code":"83", + "code":"87", "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", @@ -1749,7 +1830,7 @@ "uri":"dcs-ug-0312033.html", "node_id":"dcs-ug-0312033.xml", "product_code":"dcs", - "code":"84", + "code":"88", "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", @@ -1770,7 +1851,7 @@ "uri":"dcs-ug-0312034.html", "node_id":"dcs-ug-0312034.xml", "product_code":"dcs", - "code":"85", + "code":"89", "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", @@ -1791,7 +1872,7 @@ "uri":"dcs-ug-0312035.html", "node_id":"dcs-ug-0312035.xml", "product_code":"dcs", - "code":"86", + "code":"90", "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", @@ -1812,7 +1893,7 @@ "uri":"dcs-ug-0312036.html", "node_id":"dcs-ug-0312036.xml", "product_code":"dcs", - "code":"87", + "code":"91", "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", @@ -1833,7 +1914,7 @@ "uri":"dcs-ug-210922001.html", "node_id":"dcs-ug-210922001.xml", "product_code":"dcs", - "code":"88", + "code":"92", "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", @@ -1854,7 +1935,7 @@ "uri":"dcs-ug-0312037.html", "node_id":"dcs-ug-0312037.xml", "product_code":"dcs", - "code":"89", + "code":"93", "des":"Use the DCS console to migrate backup data to DCS for Redis.Simply download the source Redis backup data and then upload the data to an OBS bucket in the same region as t", "doc_type":"usermanual", "kw":"Importing Backup Files from an OBS Bucket,Importing Backup Files,User Guide", @@ -1875,7 +1956,7 @@ "uri":"dcs-ug-210226001.html", "node_id":"dcs-ug-210226001.xml", "product_code":"dcs", - "code":"90", + "code":"94", "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", @@ -1896,7 +1977,7 @@ "uri":"dcs-ug-0312038.html", "node_id":"dcs-ug-0312038.xml", "product_code":"dcs", - "code":"91", + "code":"95", "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", @@ -1913,11 +1994,32 @@ "title":"Migrating Data Online", "githuburl":"" }, + { + "uri":"dcs-ug-210820001.html", + "node_id":"dcs-ug-210820001.xml", + "product_code":"dcs", + "code":"96", + "des":"Currently, you cannot change the instance type when using the specification modification function. To modify instance specifications while changing the instance type, you", + "doc_type":"usermanual", + "kw":"Switching DCS Instance IP Addresses,Migrating Data with DCS,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dcs", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"Yes", + "IsBot":"Yes" + } + ], + "title":"Switching DCS Instance IP Addresses", + "githuburl":"" + }, { "uri":"dcs-ug-0312039.html", "node_id":"dcs-ug-0312039.xml", "product_code":"dcs", - "code":"92", + "code":"97", "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", @@ -1938,7 +2040,7 @@ "uri":"cache-instance-password.html", "node_id":"cache-instance-password.xml", "product_code":"dcs", - "code":"93", + "code":"98", "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", @@ -1959,7 +2061,7 @@ "uri":"dcs-ug-0312040.html", "node_id":"dcs-ug-0312040.xml", "product_code":"dcs", - "code":"94", + "code":"99", "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", @@ -1976,11 +2078,53 @@ "title":"Changing Instance Passwords", "githuburl":"" }, + { + "uri":"dcs-ug-0312041.html", + "node_id":"dcs-ug-0312041.xml", + "product_code":"dcs", + "code":"100", + "des":"On the DCS console, you can configure a new password if you forget your instance password.For a DCS Redis instance, you can change it from password mode to password-free ", + "doc_type":"usermanual", + "kw":"configure a new password,Resetting Instance Passwords,Managing Passwords,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"dcs", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"Yes", + "IsBot":"Yes" + } + ], + "title":"Resetting Instance Passwords", + "githuburl":"" + }, + { + "uri":"dcs-ug-0312042.html", + "node_id":"dcs-ug-0312042.xml", + "product_code":"dcs", + "code":"101", + "des":"DCS Redis instances can be accessed with or without passwords. After an instance is created, you can change its password setting in the following scenarios:To access a DC", + "doc_type":"usermanual", + "kw":"enable password-free access,Changing Password Settings for DCS Redis Instances,Managing Passwords,Us", + "search_title":"", + "metedata":[ + { + "prodname":"dcs", + "opensource":"true", + "documenttype":"usermanual", + "IsMulti":"Yes", + "IsBot":"Yes" + } + ], + "title":"Changing Password Settings for DCS Redis Instances", + "githuburl":"" + }, { "uri":"dcs-ug-210622001.html", "node_id":"dcs-ug-210622001.xml", "product_code":"dcs", - "code":"95", + "code":"102", "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", @@ -2001,7 +2145,7 @@ "uri":"dcs-ug-210622002.html", "node_id":"dcs-ug-210622002.xml", "product_code":"dcs", - "code":"96", + "code":"103", "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", @@ -2022,7 +2166,7 @@ "uri":"dcs-ug-210622003.html", "node_id":"dcs-ug-210622003.xml", "product_code":"dcs", - "code":"97", + "code":"104", "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", @@ -2043,7 +2187,7 @@ "uri":"dcs-ug-210622004.html", "node_id":"dcs-ug-210622004.xml", "product_code":"dcs", - "code":"98", + "code":"105", "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", @@ -2064,7 +2208,7 @@ "uri":"dcs-ug-210622005.html", "node_id":"dcs-ug-210622005.xml", "product_code":"dcs", - "code":"99", + "code":"106", "des":"This section describes how to delete a custom parameter template.", "doc_type":"usermanual", "kw":"Deleting a Custom Parameter Template,Parameter Templates,User Guide", @@ -2085,7 +2229,7 @@ "uri":"dcs-ug-0326016.html", "node_id":"dcs-ug-0326016.xml", "product_code":"dcs", - "code":"100", + "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":"Monitoring", @@ -2106,7 +2250,7 @@ "uri":"dcs-ug-0326019.html", "node_id":"dcs-ug-0326019.xml", "product_code":"dcs", - "code":"101", + "code":"108", "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", @@ -2127,7 +2271,7 @@ "uri":"dcs-ug-0312045.html", "node_id":"dcs-ug-0312045.xml", "product_code":"dcs", - "code":"102", + "code":"109", "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", @@ -2148,7 +2292,7 @@ "uri":"dcs-ug-190905001.html", "node_id":"dcs-ug-190905001.xml", "product_code":"dcs", - "code":"103", + "code":"110", "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", @@ -2169,7 +2313,7 @@ "uri":"dcs-ug-0326017.html", "node_id":"dcs-ug-0326017.xml", "product_code":"dcs", - "code":"104", + "code":"111", "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", @@ -2190,7 +2334,7 @@ "uri":"dcs-ug-0326018.html", "node_id":"dcs-ug-0326018.xml", "product_code":"dcs", - "code":"105", + "code":"112", "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", @@ -2211,7 +2355,7 @@ "uri":"dcs-ug-0312047.html", "node_id":"dcs-ug-0312047.xml", "product_code":"dcs", - "code":"106", + "code":"113", "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", @@ -2232,7 +2376,7 @@ "uri":"dcs-migration-230313.html", "node_id":"dcs-migration-230313.xml", "product_code":"dcs", - "code":"107", + "code":"114", "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 Migration Guide", @@ -2253,7 +2397,7 @@ "uri":"dcs-migration-0713001.html", "node_id":"dcs-migration-0713001.xml", "product_code":"dcs", - "code":"108", + "code":"115", "des":"Due to variations of Redis application environments and scenarios, migration solutions must be detailed to address actual requirements. The time required for data migrati", "doc_type":"usermanual", "kw":"Overview,Data Migration Guide,User Guide", @@ -2271,7 +2415,7 @@ "uri":"dcs-migration-0312001.html", "node_id":"dcs-migration-0312001.xml", "product_code":"dcs", - "code":"109", + "code":"116", "des":"Collect the following information about the cached data to be migrated (based on Information to be collected for the migration):Number of instancesNumber of databases (DB", "doc_type":"usermanual", "kw":"Migration Process,Data Migration Guide,User Guide", @@ -2289,10 +2433,10 @@ "uri":"dcs-migration-090626002.html", "node_id":"dcs-migration-090626002.xml", "product_code":"dcs", - "code":"110", + "code":"117", "des":"Self-hosted Redis refers to self-hosted Redis on this service, in another cloud, or in on-premises data centers.", "doc_type":"usermanual", - "kw":"Migration Tools and Schemes,Data Migration Guide,User Guide", + "kw":"Migration Solution Notes,Data Migration Guide,User Guide", "search_title":"", "metedata":[ { @@ -2300,14 +2444,14 @@ "prodname":"dcs" } ], - "title":"Migration Tools and Schemes", + "title":"Migration Solution Notes", "githuburl":"" }, { "uri":"dcs-migration-0312002.html", "node_id":"dcs-migration-0312002.xml", "product_code":"dcs", - "code":"111", + "code":"118", "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 from Self-Hosted Redis to DCS", @@ -2325,10 +2469,10 @@ "uri":"dcs-migration-190703003.html", "node_id":"dcs-migration-190703003.xml", "product_code":"dcs", - "code":"112", - "des":"If the source and target instances are interconnected and the SYNC and PSYNC commands are supported by the source instance, data can be migrated online in full or increme", + "code":"119", + "des":"If the source self-host and target instances are interconnected and the SYNC and PSYNC commands are supported by the source instance, data can be migrated online in full ", "doc_type":"usermanual", - "kw":"Online Migration of Self-Hosted Redis,Migrating Data from Self-Hosted Redis to DCS,User Guide", + "kw":"Migrating Self-Built Redis Online,Migrating Data from Self-Hosted Redis to DCS,User Guide", "search_title":"", "metedata":[ { @@ -2336,17 +2480,17 @@ "prodname":"dcs" } ], - "title":"Online Migration of Self-Hosted Redis", + "title":"Migrating Self-Built Redis Online", "githuburl":"" }, { "uri":"dcs-migration-190703002.html", "node_id":"dcs-migration-190703002.xml", "product_code":"dcs", - "code":"113", - "des":"Use the DCS console to migrate Redis data from Redis of another cloud or self-hosted Redis to DCS for Redis.Simply download the source Redis data and then upload the data", + "code":"120", + "des":"This section describes how to migrate self-hosted Redis to DCS by importing backup files.Simply download the source Redis data and then upload the data to an OBS bucket i", "doc_type":"usermanual", - "kw":"Backup Migration of Self-Hosted Redis,Migrating Data from Self-Hosted Redis to DCS,User Guide", + "kw":"Self-Hosted Redis Migration with Backup Files,Migrating Data from Self-Hosted Redis to DCS,User Guid", "search_title":"", "metedata":[ { @@ -2354,15 +2498,15 @@ "prodname":"dcs" } ], - "title":"Backup Migration of Self-Hosted Redis", + "title":"Self-Hosted Redis Migration with Backup Files", "githuburl":"" }, { "uri":"dcs-migration-0312010.html", "node_id":"dcs-migration-0312010.xml", "product_code":"dcs", - "code":"114", - "des":"redis-cli is the command line tool of Redis, which can be used after you install the Redis server.Run the following command to download Redis:wget http://download.redis.i", + "code":"121", + "des":"redis-cli is the command line tool of Redis, which can be used after you install the Redis server. This section describes how to use redis-cli to migrate a data from a se", "doc_type":"usermanual", "kw":"Self-Hosted Redis Migration with redis-cli (AOF),Migrating Data from Self-Hosted Redis to DCS,User G", "search_title":"", @@ -2379,8 +2523,8 @@ "uri":"dcs-migration-0312011.html", "node_id":"dcs-migration-0312011.xml", "product_code":"dcs", - "code":"115", - "des":"redis-cli is the command line tool of Redis, which can be used after you install the Redis server.redis-cli supports data export as an RDB file. If your Redis service doe", + "code":"122", + "des":"redis-cli is the command line tool of Redis, which can be used after you install the Redis server. redis-cli supports data export as an RDB file. If your Redis service do", "doc_type":"usermanual", "kw":"Self-Hosted Redis Migration with redis-cli (RDB),Migrating Data from Self-Hosted Redis to DCS,User G", "search_title":"", @@ -2397,10 +2541,10 @@ "uri":"dcs-migrate-demo02.html", "node_id":"dcs-migrate-demo02.xml", "product_code":"dcs", - "code":"116", + "code":"123", "des":"redis-shake is an open-source tool for migrating data online or offline (by importing backup files) between Redis Clusters. Data can be migrated to DCS Redis Cluster inst", "doc_type":"usermanual", - "kw":"Self-Hosted Redis Cluster Migration with redis-shake,Migrating Data from Self-Hosted Redis to DCS,Us", + "kw":"Self-Hosted Redis Cluster Migration with redis-shake (Online),Migrating Data from Self-Hosted Redis ", "search_title":"", "metedata":[ { @@ -2408,14 +2552,32 @@ "prodname":"dcs" } ], - "title":"Self-Hosted Redis Cluster Migration with redis-shake", + "title":"Self-Hosted Redis Cluster Migration with redis-shake (Online)", + "githuburl":"" + }, + { + "uri":"dcs-migrate-demo03.html", + "node_id":"dcs-migrate-demo03.xml", + "product_code":"dcs", + "code":"124", + "des":"redis-shake is an open-source tool for migrating data online or offline (by importing backup files) between Redis Clusters. Data can be migrated to DCS Redis Cluster inst", + "doc_type":"usermanual", + "kw":"Self-Hosted Redis Cluster Migration with redis-shake (RDB),Migrating Data from Self-Hosted Redis to ", + "search_title":"", + "metedata":[ + { + "prodname":"dcs", + "documenttype":"usermanual" + } + ], + "title":"Self-Hosted Redis Cluster Migration with redis-shake (RDB)", "githuburl":"" }, { "uri":"dcs-migration-0312008.html", "node_id":"dcs-migration-0312008.xml", "product_code":"dcs", - "code":"117", + "code":"125", "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 Between DCS Instances", @@ -2433,46 +2595,46 @@ "uri":"dcs-migration-0312003.html", "node_id":"dcs-migration-0312003.xml", "product_code":"dcs", - "code":"118", + "code":"126", "des":"If the source and target instances are interconnected and the SYNC and PSYNC commands are supported by the source instance, data can be migrated online in full or increme", "doc_type":"usermanual", - "kw":"Online Migration Between DCS Redis Instances,Migrating Data Between DCS Instances,User Guide", + "kw":"Online Migration Between Instances,Migrating Data Between DCS Instances,User Guide", "search_title":"", "metedata":[ { - "documenttype":"usermanual", - "prodname":"dcs" + "prodname":"dcs", + "documenttype":"usermanual" } ], - "title":"Online Migration Between DCS Redis Instances", + "title":"Online Migration Between Instances", "githuburl":"" }, { "uri":"dcs-migration-0312004.html", "node_id":"dcs-migration-0312004.xml", "product_code":"dcs", - "code":"119", - "des":"Use the DCS console to migrate Redis data from Redis of another cloud or self-hosted Redis to DCS for Redis.Simply download the source Redis data and then upload the data", + "code":"127", + "des":"You can migrate data between DCS instances by importing backup files.If the source Redis and target Redis are in the same region under the same DCS account, and the sourc", "doc_type":"usermanual", - "kw":"Backup Migration Between Regions or Redis Versions,Migrating Data Between DCS Instances,User Guide", + "kw":"Backup Import Between DCS Redis Instances,Migrating Data Between DCS Instances,User Guide", "search_title":"", "metedata":[ { - "documenttype":"usermanual", - "prodname":"dcs" + "prodname":"dcs", + "documenttype":"usermanual" } ], - "title":"Backup Migration Between Regions or Redis Versions", + "title":"Backup Import Between DCS Redis Instances", "githuburl":"" }, { "uri":"dcs-migration-0312005.html", "node_id":"dcs-migration-0312005.xml", "product_code":"dcs", - "code":"120", + "code":"128", "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 Redis Data from Another Cloud to DCS", + "kw":"Migration from Another Cloud", "search_title":"", "metedata":[ { @@ -2480,17 +2642,17 @@ "prodname":"dcs" } ], - "title":"Migrating Redis Data from Another Cloud to DCS", + "title":"Migration from Another Cloud", "githuburl":"" }, { "uri":"dcs-migration-0312006.html", "node_id":"dcs-migration-0312006.xml", "product_code":"dcs", - "code":"121", + "code":"129", "des":"If the source and target instances are interconnected and the SYNC and PSYNC commands are supported by the source instance, data can be migrated online in full or increme", "doc_type":"usermanual", - "kw":"Online Migration from Another Cloud,Migrating Redis Data from Another Cloud to DCS,User Guide", + "kw":"Migrating Redis from Another Cloud Online,Migration from Another Cloud,User Guide", "search_title":"", "metedata":[ { @@ -2498,17 +2660,17 @@ "prodname":"dcs" } ], - "title":"Online Migration from Another Cloud", + "title":"Migrating Redis from Another Cloud Online", "githuburl":"" }, { "uri":"dcs-migration-1117001.html", "node_id":"dcs-migration-1117001.xml", "product_code":"dcs", - "code":"122", - "des":"Use the DCS console to migrate Redis data from Redis of another cloud or self-hosted Redis to DCS for Redis.Simply download the source Redis data and then upload the data", + "code":"130", + "des":"This section describes how to migrate Redis from another cloud to DCS by importing backup files.Simply download the source Redis data and then upload the data to an OBS b", "doc_type":"usermanual", - "kw":"Backup Migration from Another Cloud,Migrating Redis Data from Another Cloud to DCS,User Guide", + "kw":"Backup Import from Another Cloud,Migration from Another Cloud,User Guide", "search_title":"", "metedata":[ { @@ -2516,17 +2678,17 @@ "prodname":"dcs" } ], - "title":"Backup Migration from Another Cloud", + "title":"Backup Import from Another Cloud", "githuburl":"" }, { "uri":"dcs-migration-090626001_0.html", "node_id":"dcs-migration-090626001_0.xml", "product_code":"dcs", - "code":"123", + "code":"131", "des":"Redis instances provided by some cloud service vendors do not allow SLAVEOF, BGSAVE, and PSYNC commands to be issued from Redis clients. As a result, redis-cli, redis-sha", "doc_type":"usermanual", - "kw":"Online Migration with Rump,Migrating Redis Data from Another Cloud to DCS,User Guide", + "kw":"Online Migration from Another Cloud Using Rump,Migration from Another Cloud,User Guide", "search_title":"", "metedata":[ { @@ -2534,17 +2696,17 @@ "prodname":"dcs" } ], - "title":"Online Migration with Rump", + "title":"Online Migration from Another Cloud Using Rump", "githuburl":"" }, { "uri":"dcs-migrate-1117003.html", "node_id":"dcs-migrate-1117003.xml", "product_code":"dcs", - "code":"124", + "code":"132", "des":"redis-shake is an open-source tool for migrating data online or offline (by importing backup files) between Redis Clusters. If the source Redis Cluster is deployed in ano", "doc_type":"usermanual", - "kw":"Offline Migration of Redis Cluster from Another Cloud with redis-shake,Migrating Redis Data from Ano", + "kw":"Backup Import from Another Cloud Using redis-shake,Migration from Another Cloud,User Guide", "search_title":"", "metedata":[ { @@ -2552,17 +2714,17 @@ "prodname":"dcs" } ], - "title":"Offline Migration of Redis Cluster from Another Cloud with redis-shake", + "title":"Backup Import from Another Cloud Using redis-shake", "githuburl":"" }, { "uri":"dcs-migrate-0220411.html", "node_id":"dcs-migrate-0220411.xml", "product_code":"dcs", - "code":"125", + "code":"133", "des":"redis-shake is an open-source Redis migration tool. Its rump mode allows you to obtain the full data of a source Redis using the SCAN command and write the data to a targ", "doc_type":"usermanual", - "kw":"Online Full Migration of Redis from Another Cloud with redis-shake,Migrating Redis Data from Another", + "kw":"Migrating from Another Cloud Online Using redis-shake,Migration from Another Cloud,User Guide", "search_title":"", "metedata":[ { @@ -2570,14 +2732,14 @@ "prodname":"dcs" } ], - "title":"Online Full Migration of Redis from Another Cloud with redis-shake", + "title":"Migrating from Another Cloud Online Using redis-shake", "githuburl":"" }, { "uri":"dcs-migration-0312007.html", "node_id":"dcs-migration-0312007.xml", "product_code":"dcs", - "code":"126", + "code":"134", "des":"You can use the online migration function of the DCS console to migrate DCS Redis instances to your self-hosted Redis. You can also export the DCS instance data to an RDB", "doc_type":"usermanual", "kw":"Migrating Data from DCS to Self-Hosted Redis,Data Migration Guide,User Guide", @@ -2595,7 +2757,7 @@ "uri":"dcs-faq-0326019.html", "node_id":"dcs-faq-0326019.xml", "product_code":"dcs", - "code":"127", + "code":"135", "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", @@ -2616,7 +2778,7 @@ "uri":"dcs-faq-0326020.html", "node_id":"dcs-faq-0326020.xml", "product_code":"dcs", - "code":"128", + "code":"136", "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", @@ -2637,7 +2799,7 @@ "uri":"en-us_topic_0090662012.html", "node_id":"en-us_topic_0090662012.xml", "product_code":"dcs", - "code":"129", + "code":"137", "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", @@ -2658,8 +2820,8 @@ "uri":"dcs-faq-0730001.html", "node_id":"dcs-faq-0730001.xml", "product_code":"dcs", - "code":"130", - "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", + "code":"138", + "des":"No. DCS instances cannot be accessed at their EIPs over public networks. To ensure security, the ECS that serves as a client and the DCS instance that the client will acc", "doc_type":"usermanual", "kw":"Does DCS Support Access over Public Networks?,Client and Network Connection,User Guide", "search_title":"", @@ -2679,7 +2841,7 @@ "uri":"en-us_topic_0100698850.html", "node_id":"en-us_topic_0100698850.xml", "product_code":"dcs", - "code":"131", + "code":"139", "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", @@ -2700,7 +2862,7 @@ "uri":"dcs-faq-0427005.html", "node_id":"dcs-faq-0427005.xml", "product_code":"dcs", - "code":"132", + "code":"140", "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":"usermanual", "kw":"Why Is \"(error) NOAUTH Authentication required\" Displayed When I Access a DCS Redis Instance?,Client", @@ -2721,7 +2883,7 @@ "uri":"dcs-faq-0730004.html", "node_id":"dcs-faq-0730004.xml", "product_code":"dcs", - "code":"133", + "code":"141", "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", @@ -2742,7 +2904,7 @@ "uri":"dcs-faq-0730005.html", "node_id":"dcs-faq-0730005.xml", "product_code":"dcs", - "code":"134", + "code":"142", "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", @@ -2763,7 +2925,7 @@ "uri":"dcs-faq-0730006.html", "node_id":"dcs-faq-0730006.xml", "product_code":"dcs", - "code":"135", + "code":"143", "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", @@ -2784,7 +2946,7 @@ "uri":"dcs-faq-0730007.html", "node_id":"dcs-faq-0730007.xml", "product_code":"dcs", - "code":"136", + "code":"144", "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", @@ -2805,7 +2967,7 @@ "uri":"dcs-faq-0730008.html", "node_id":"dcs-faq-0730008.xml", "product_code":"dcs", - "code":"137", + "code":"145", "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", @@ -2826,7 +2988,7 @@ "uri":"dcs-faq-0730009.html", "node_id":"dcs-faq-0730009.xml", "product_code":"dcs", - "code":"138", + "code":"146", "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", @@ -2847,7 +3009,7 @@ "uri":"dcs-faq-0427015.html", "node_id":"dcs-faq-0427015.xml", "product_code":"dcs", - "code":"139", + "code":"147", "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":"usermanual", "kw":"Is a Password Required for Accessing an Instance? How Do I Set a Password?,Client and Network Connec", @@ -2868,7 +3030,7 @@ "uri":"dcs-faq-0730011.html", "node_id":"dcs-faq-0730011.xml", "product_code":"dcs", - "code":"140", + "code":"148", "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", @@ -2889,7 +3051,7 @@ "uri":"dcs-faq-0730010.html", "node_id":"dcs-faq-0730010.xml", "product_code":"dcs", - "code":"141", + "code":"149", "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", @@ -2910,7 +3072,7 @@ "uri":"dcs-faq-210721003.html", "node_id":"dcs-faq-210721003.xml", "product_code":"dcs", - "code":"142", + "code":"150", "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":"usermanual", "kw":"What Can I Do If Error \"Cannot assign requested address\" Is Returned When I Access Redis Using conne", @@ -2931,7 +3093,7 @@ "uri":"dcs-faq-211230001.html", "node_id":"dcs-faq-211230001.xml", "product_code":"dcs", - "code":"143", + "code":"151", "des":"The comparison between Lettuce and Jedis is as follows:LettuceLettuce does not perform connection keepalive detection. If an abnormal connection exists in the connection ", "doc_type":"usermanual", "kw":"Connection Pool Selection and Recommended Jedis Parameter Settings,Client and Network Connection,Use", @@ -2952,8 +3114,8 @@ "uri":"dcs-faq-022025.html", "node_id":"dcs-faq-022025.xml", "product_code":"dcs", - "code":"144", - "des":"Single-node, and Proxy Cluster:Each instance has only one IP address and one domain name address. The addresses remain unchanged before and after master/standby switchove", + "code":"152", + "des":"Single-node, read/write splitting, and Proxy Cluster:Each instance has only one IP address and one domain name address. The addresses remain unchanged before and after ma", "doc_type":"usermanual", "kw":"Should I Use a Domain Name or an IP Address to Connect to a DCS Redis Instance?,Client and Network C", "search_title":"", @@ -2973,8 +3135,8 @@ "uri":"dcs-faq-221222.html", "node_id":"dcs-faq-221222.xml", "product_code":"dcs", - "code":"145", - "des":"A master/standby DCS Redis 4.0/5.0/6.0 instance has a Connection Address and a Read-only Address. The connection address is used to connect to the master node of the inst", + "code":"153", + "des":"A master/standby DCS Redis 4.0 or later instance has a Connection Address and a Read-only Address. The connection address is used to connect to the master node of the ins", "doc_type":"usermanual", "kw":"Is the Read-only Address of a Master/Standby Instance Connected to the Master or Standby Node?,Clien", "search_title":"", @@ -2994,7 +3156,7 @@ "uri":"dcs-faq-0326021.html", "node_id":"dcs-faq-0326021.xml", "product_code":"dcs", - "code":"146", + "code":"154", "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", @@ -3015,7 +3177,7 @@ "uri":"dcs-faq-0730012.html", "node_id":"dcs-faq-0730012.xml", "product_code":"dcs", - "code":"147", + "code":"155", "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", @@ -3036,7 +3198,7 @@ "uri":"dcs-faq-0730013.html", "node_id":"dcs-faq-0730013.xml", "product_code":"dcs", - "code":"148", + "code":"156", "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", @@ -3057,10 +3219,10 @@ "uri":"dcs-faq-0730014.html", "node_id":"dcs-faq-0730014.xml", "product_code":"dcs", - "code":"149", - "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", + "code":"157", + "des":"Currently, DCS Redis 4.0 and later instances use VPC endpoints and do not support security groups. You can configure whitelists instead. For details, see Managing IP Addr", "doc_type":"usermanual", - "kw":"Why Aren't Security Groups Configured for DCS Redis 4.0/5.0/6.0 Instances?,Redis Usage,User Guide", + "kw":"Why Aren't Security Groups Configured for DCS Redis 4.0 and Later Instances?,Redis Usage,User Guide", "search_title":"", "metedata":[ { @@ -3071,14 +3233,14 @@ "IsBot":"Yes" } ], - "title":"Why Aren't Security Groups Configured for DCS Redis 4.0/5.0/6.0 Instances?", + "title":"Why Aren't Security Groups Configured for DCS Redis 4.0 and Later Instances?", "githuburl":"" }, { "uri":"dcs-faq-0730015.html", "node_id":"dcs-faq-0730015.xml", "product_code":"dcs", - "code":"150", + "code":"158", "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", @@ -3099,7 +3261,7 @@ "uri":"dcs-faq-0730017.html", "node_id":"dcs-faq-0730017.xml", "product_code":"dcs", - "code":"151", + "code":"159", "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", @@ -3120,7 +3282,7 @@ "uri":"dcs-faq-0730018.html", "node_id":"dcs-faq-0730018.xml", "product_code":"dcs", - "code":"152", + "code":"160", "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 Smaller Than Instance Cache Size?,Redis Usage,User Guide", @@ -3141,7 +3303,7 @@ "uri":"dcs-faq-0730019.html", "node_id":"dcs-faq-0730019.xml", "product_code":"dcs", - "code":"153", + "code":"161", "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 ", @@ -3162,7 +3324,7 @@ "uri":"dcs-faq-0730020.html", "node_id":"dcs-faq-0730020.xml", "product_code":"dcs", - "code":"154", + "code":"162", "des":"Yes. DCS for Redis 4.0 and later support Redis Clusters. DCS for Redis 3.0 supports Proxy Clusters.", "doc_type":"usermanual", "kw":"Does DCS for Redis Support Redis Clusters?,Redis Usage,User Guide", @@ -3183,8 +3345,8 @@ "uri":"dcs-faq-0730021.html", "node_id":"dcs-faq-0730021.xml", "product_code":"dcs", - "code":"155", - "des":"Cluster instances and master/standby DCS Redis 4.0 and later instances support Sentinels. Sentinels monitor the running status of both the master and standby nodes of a m", + "code":"163", + "des":"Master/Standby, read/write splitting, and cluster DCS Redis 4.0 and later instances support Sentinels (Each shard of a cluster is a master/standby instance.). Sentinels m", "doc_type":"usermanual", "kw":"Does DCS for Redis Support Sentinel?,Redis Usage,User Guide", "search_title":"", @@ -3204,7 +3366,7 @@ "uri":"dcs-faq-0730022.html", "node_id":"dcs-faq-0730022.xml", "product_code":"dcs", - "code":"156", + "code":"164", "des":"Data is evicted from cache based on a user-defined space limit in order to make space for new data. For details, see the Redis official website. You can view or change th", "doc_type":"usermanual", "kw":"What Is the Default Data Eviction Policy?,Redis Usage,User Guide", @@ -3225,7 +3387,7 @@ "uri":"dcs-faq-0730023.html", "node_id":"dcs-faq-0730023.xml", "product_code":"dcs", - "code":"157", + "code":"165", "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", @@ -3246,7 +3408,7 @@ "uri":"dcs-faq-0730025.html", "node_id":"dcs-faq-0730025.xml", "product_code":"dcs", - "code":"158", + "code":"166", "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", @@ -3267,7 +3429,7 @@ "uri":"dcs-faq-0730026.html", "node_id":"dcs-faq-0730026.xml", "product_code":"dcs", - "code":"159", + "code":"167", "des":"You cannot customize or change the port for accessing a DCS Redis 3.0 instance. You can customize (during instance creation) and change the port (on the instance details ", "doc_type":"usermanual", "kw":"Can I Customize or Change the Port for Accessing a DCS Instance?,Redis Usage,User Guide", @@ -3288,7 +3450,7 @@ "uri":"dcs-faq-0730027.html", "node_id":"dcs-faq-0730027.xml", "product_code":"dcs", - "code":"160", + "code":"168", "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", @@ -3309,8 +3471,8 @@ "uri":"dcs-faq-0730029.html", "node_id":"dcs-faq-0730029.xml", "product_code":"dcs", - "code":"161", - "des":"Master/Standby and cluster DCS Redis instances can be deployed across availability zones (AZs).If instance nodes in an AZ are faulty, nodes in other AZs will not be affec", + "code":"169", + "des":"Master/Standby, read/write splitting, and cluster DCS Redis instances can be deployed across availability zones (AZs).If instance nodes in an AZ are faulty, nodes in othe", "doc_type":"usermanual", "kw":"Does DCS Support Cross-AZ Deployment?,Redis Usage,User Guide", "search_title":"", @@ -3330,7 +3492,7 @@ "uri":"dcs-faq-0730030.html", "node_id":"dcs-faq-0730030.xml", "product_code":"dcs", - "code":"162", + "code":"170", "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", @@ -3351,7 +3513,7 @@ "uri":"dcs-faq-0730032.html", "node_id":"dcs-faq-0730032.xml", "product_code":"dcs", - "code":"163", + "code":"171", "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", @@ -3372,7 +3534,7 @@ "uri":"dcs-faq-0730034.html", "node_id":"dcs-faq-0730034.xml", "product_code":"dcs", - "code":"164", + "code":"172", "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", @@ -3393,7 +3555,7 @@ "uri":"dcs-faq-210223001.html", "node_id":"dcs-faq-210223001.xml", "product_code":"dcs", - "code":"165", + "code":"173", "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", @@ -3414,7 +3576,7 @@ "uri":"dcs-faq-210409001.html", "node_id":"dcs-faq-210409001.xml", "product_code":"dcs", - "code":"166", + "code":"174", "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":"usermanual", "kw":"Why Does a Key Disappear in Redis?,Redis Usage,User Guide", @@ -3435,7 +3597,7 @@ "uri":"dcs-faq-211228001.html", "node_id":"dcs-faq-211228001.xml", "product_code":"dcs", - "code":"167", + "code":"175", "des":"Multi-key operations, such as those using the MSET command or Lua scripts, are atomic. All specified keys are executed at the same time. However, in a cluster, each key i", "doc_type":"usermanual", "kw":"Explaining and Using Hash Tags,Redis Usage,User Guide", @@ -3456,8 +3618,8 @@ "uri":"dcs-faq-0220330.html", "node_id":"dcs-faq-0220330.xml", "product_code":"dcs", - "code":"168", - "des":"After a single-node DCS instance is restarted, data in the instance is deleted.Master/Standby and cluster instances (except single-replica clusters) support AOF persisten", + "code":"176", + "des":"After a single-node DCS instance is restarted, data in the instance is deleted.Master/Standby, read/write splitting, and cluster instances (except single-replica clusters", "doc_type":"usermanual", "kw":"Will Cached Data Be Retained After an Instance Is Restarted?,Redis Usage,User Guide", "search_title":"", @@ -3477,7 +3639,7 @@ "uri":"dcs-faq-190921003.html", "node_id":"dcs-faq-190921003.xml", "product_code":"dcs", - "code":"169", + "code":"177", "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", @@ -3498,7 +3660,7 @@ "uri":"dcs-faq-0730036.html", "node_id":"dcs-faq-0730036.xml", "product_code":"dcs", - "code":"170", + "code":"178", "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", @@ -3519,7 +3681,7 @@ "uri":"dcs-faq-0730039.html", "node_id":"dcs-faq-0730039.xml", "product_code":"dcs", - "code":"171", + "code":"179", "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", @@ -3540,7 +3702,7 @@ "uri":"dcs-faq-0730040.html", "node_id":"dcs-faq-0730040.xml", "product_code":"dcs", - "code":"172", + "code":"180", "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", @@ -3561,7 +3723,7 @@ "uri":"dcs-faq-0730041.html", "node_id":"dcs-faq-0730041.xml", "product_code":"dcs", - "code":"173", + "code":"181", "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", @@ -3582,8 +3744,8 @@ "uri":"dcs-faq-0427057.html", "node_id":"dcs-faq-0427057.xml", "product_code":"dcs", - "code":"174", - "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", + "code":"182", + "des":"Redis timeouts happen on the client or server.Timeouts on the client are managed in the client code. Services can determine an appropriate timeout. For example, parameter", "doc_type":"usermanual", "kw":"Is There a Time Limit on Executing Redis Commands? What Will Happen If a Command Times Out?,Redis Co", "search_title":"", @@ -3603,7 +3765,7 @@ "uri":"dcs-faq-0427058.html", "node_id":"dcs-faq-0427058.xml", "product_code":"dcs", - "code":"175", + "code":"183", "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":"usermanual", "kw":"Can I Configure Redis Keys to Be Case-Insensitive?,Redis Commands,User Guide", @@ -3624,7 +3786,7 @@ "uri":"dcs-faq-0624001.html", "node_id":"dcs-faq-0624001.xml", "product_code":"dcs", - "code":"176", + "code":"184", "des":"No. Redis does not record commands and does not support viewing the most frequently used commands.", "doc_type":"usermanual", "kw":"Can I View the Most Frequently Used Redis Commands?,Redis Commands,User Guide", @@ -3645,7 +3807,7 @@ "uri":"dcs-faq-0326022.html", "node_id":"dcs-faq-0326022.xml", "product_code":"dcs", - "code":"177", + "code":"185", "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", @@ -3666,7 +3828,7 @@ "uri":"dcs-faq-0730043.html", "node_id":"dcs-faq-0730043.xml", "product_code":"dcs", - "code":"178", + "code":"186", "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 4.0 to 5.0?,Instance Scaling and Upgrad", @@ -3687,7 +3849,7 @@ "uri":"dcs-faq-0730044.html", "node_id":"dcs-faq-0730044.xml", "product_code":"dcs", - "code":"179", + "code":"187", "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", @@ -3708,7 +3870,7 @@ "uri":"dcs-faq-0730045.html", "node_id":"dcs-faq-0730045.xml", "product_code":"dcs", - "code":"180", + "code":"188", "des":"No. Specification modifications can take place while the instance is running and do not affect any other resources.", "doc_type":"usermanual", "kw":"Are Instances Stopped or Restarted During Specification Modification?,Instance Scaling and Upgrade,U", @@ -3729,8 +3891,8 @@ "uri":"dcs-faq-0730047.html", "node_id":"dcs-faq-0730047.xml", "product_code":"dcs", - "code":"181", - "des":"You are advised to change the instance specifications during off-peak hours because specification modification has the following impacts:Supported instance type changes:F", + "code":"189", + "des":"You are advised to change the instance specifications during off-peak hours because specification modification has the following impacts:The following table lists scaling", "doc_type":"usermanual", "kw":"Are Services Interrupted During Specification Modification?,Instance Scaling and Upgrade,User Guide", "search_title":"", @@ -3750,7 +3912,7 @@ "uri":"dcs-faq-0730048.html", "node_id":"dcs-faq-0730048.xml", "product_code":"dcs", - "code":"182", + "code":"190", "des":"Check whether other tasks are running.Specifications of a DCS instance cannot be modified if another task of the instance is still running. For example, you cannot delete", "doc_type":"usermanual", "kw":"Why Can't I Modify Specifications for a DCS Redis Instance?,Instance Scaling and Upgrade,User Guide", @@ -3771,7 +3933,7 @@ "uri":"dcs-faq-0326023.html", "node_id":"dcs-faq-0326023.xml", "product_code":"dcs", - "code":"183", + "code":"191", "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", @@ -3792,7 +3954,7 @@ "uri":"dcs-faq-0427070.html", "node_id":"dcs-faq-0427070.xml", "product_code":"dcs", - "code":"184", + "code":"192", "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":"usermanual", "kw":"How Do I View Current Concurrent Connections and Maximum Connections of a DCS Redis Instance?,Monito", @@ -3813,7 +3975,7 @@ "uri":"dcs-faq-0730049.html", "node_id":"dcs-faq-0730049.xml", "product_code":"dcs", - "code":"185", + "code":"193", "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", @@ -3834,7 +3996,7 @@ "uri":"dcs-faq-0730050.html", "node_id":"dcs-faq-0730050.xml", "product_code":"dcs", - "code":"186", + "code":"194", "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", @@ -3855,7 +4017,7 @@ "uri":"dcs-faq-0730052.html", "node_id":"dcs-faq-0730052.xml", "product_code":"dcs", - "code":"187", + "code":"195", "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", @@ -3876,7 +4038,7 @@ "uri":"dcs-faq-0513001.html", "node_id":"dcs-faq-0513001.xml", "product_code":"dcs", - "code":"188", + "code":"196", "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":"usermanual", "kw":"Why Does Bandwidth Usage Exceed 100%?,Monitoring and Alarm,User Guide", @@ -3897,8 +4059,8 @@ "uri":"dcs-faq-0603001.html", "node_id":"dcs-faq-0603001.xml", "product_code":"dcs", - "code":"189", - "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":"197", + "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.The Rejected ", "doc_type":"usermanual", "kw":"Why Is the Rejected Connections Metric Displayed?,Monitoring and Alarm,User Guide", "search_title":"", @@ -3918,7 +4080,7 @@ "uri":"dcs-faq-0220721.html", "node_id":"dcs-faq-0220721.xml", "product_code":"dcs", - "code":"190", + "code":"198", "des":"Flow control is triggered when the traffic used by a Redis instance in a period exceeds the maximum bandwidth.For details about the maximum bandwidth of an instance flavo", "doc_type":"usermanual", "kw":"Why Is Flow Control Triggered? How Do I Handle It?,Monitoring and Alarm,User Guide", @@ -3939,7 +4101,7 @@ "uri":"dcs-faq-0326024.html", "node_id":"dcs-faq-0326024.xml", "product_code":"dcs", - "code":"191", + "code":"199", "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", @@ -3960,7 +4122,7 @@ "uri":"dcs-faq-0730053.html", "node_id":"dcs-faq-0730053.xml", "product_code":"dcs", - "code":"192", + "code":"200", "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", @@ -3981,7 +4143,7 @@ "uri":"dcs-faq-0730054.html", "node_id":"dcs-faq-0730054.xml", "product_code":"dcs", - "code":"193", + "code":"201", "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,", @@ -4002,10 +4164,10 @@ "uri":"dcs-faq-0427081.html", "node_id":"dcs-faq-0427081.xml", "product_code":"dcs", - "code":"194", - "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:", + "code":"202", + "des":"Single-node: NoMaster/Standby, read/write splitting, and cluster (except single-replica clusters): YesDCS Redis instances supports only AOF persistence by default. You ca", "doc_type":"usermanual", - "kw":"Does DCS Support Data Persistence? What Is the Impact of Persistence?,Data Backup, Export, and Migra", + "kw":"Do DCS Redis Instances Support Data Persistence? What Is the Impact of Persistence?,Data Backup, Exp", "search_title":"", "metedata":[ { @@ -4016,14 +4178,14 @@ "IsBot":"Yes" } ], - "title":"Does DCS Support Data Persistence? What Is the Impact of Persistence?", + "title":"Do DCS Redis Instances Support Data Persistence? What Is the Impact of Persistence?", "githuburl":"" }, { "uri":"dcs-faq-210706001.html", "node_id":"dcs-faq-210706001.xml", "product_code":"dcs", - "code":"195", + "code":"203", "des":"AOF rewrites involve the following concepts:Rewrite window, which is currently 01:00 to 04:59Disk usage threshold, which is 50%Dataset memory, which is the percentage of ", "doc_type":"usermanual", "kw":"When Will AOF Rewrites Be Triggered?,Data Backup, Export, and Migration,User Guide", @@ -4044,7 +4206,7 @@ "uri":"dcs-faq-220317.html", "node_id":"dcs-faq-220317.xml", "product_code":"dcs", - "code":"196", + "code":"204", "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":"usermanual", "kw":"Can I Migrate Data to Multiple Target Instances in One Migration Task?,Data Backup, Export, and Migr", @@ -4065,8 +4227,8 @@ "uri":"dcs-faq-210721001.html", "node_id":"dcs-faq-210721001.xml", "product_code":"dcs", - "code":"197", - "des":"Migration within DCS:By default, the SYNC and PSYNC commands can be used when self-hosted Redis is migrated to DCS.During online migration between DCS Redis instances in ", + "code":"205", + "des":"Migration within DCS:If the online migration task uses the same account and region as the source instance, select a DCS instance (cloud Redis) as the source. The SYNC and", "doc_type":"usermanual", "kw":"How Do I Enable the SYNC and PSYNC Commands?,Data Backup, Export, and Migration,User Guide", "search_title":"", @@ -4082,32 +4244,11 @@ "title":"How Do I Enable the SYNC and PSYNC Commands?", "githuburl":"" }, - { - "uri":"dcs-faq-210721002.html", - "node_id":"dcs-faq-210721002.xml", - "product_code":"dcs", - "code":"198", - "des":"Possible causes:The underlying resources are insufficient.The specifications of the ECS used for the migration are insufficient.The memory of the target Redis created bef", - "doc_type":"usermanual", - "kw":"Why Does Migration Task Creation Fail?,Data Backup, Export, and Migration,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"dcs", - "opensource":"true", - "documenttype":"usermanual", - "IsMulti":"Yes", - "IsBot":"Yes" - } - ], - "title":"Why Does Migration Task Creation Fail?", - "githuburl":"" - }, { "uri":"dcs-faq-11185.html", "node_id":"dcs-faq-11185.xml", "product_code":"dcs", - "code":"199", + "code":"206", "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":"usermanual", "kw":"Will the Same Keys Be Overwritten During Data Migration or Backup Import?,Data Backup, Export, and M", @@ -4128,7 +4269,7 @@ "uri":"dcs-migration-090626001.html", "node_id":"dcs-migration-090626001.xml", "product_code":"dcs", - "code":"200", + "code":"207", "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":"usermanual", "kw":"Online Migration with Rump,Data Backup, Export, and Migration,User Guide", @@ -4149,7 +4290,7 @@ "uri":"dcs-migration-0312016.html", "node_id":"dcs-migration-0312016.xml", "product_code":"dcs", - "code":"201", + "code":"208", "des":"Convert the format of a data file before importing the file.Run the following command to convert the format of a file in the Windows OS to that in the Unix-like OS:dos2un", "doc_type":"usermanual", "kw":"What Should I Consider When Transferring or Operating Data Between Different OSs?,Data Backup, Expor", @@ -4170,8 +4311,8 @@ "uri":"dcs-migration-0312017.html", "node_id":"dcs-migration-0312017.xml", "product_code":"dcs", - "code":"202", - "des":"A total of 256 DBs (DB 0 to DB 255) can be configured for a single-node or master/standby DCS instance.If the target is a cluster instance (a cluster instance has only on", + "code":"209", + "des":"A total of 256 DBs (DB 0 to DB 255) can be configured for a single-node, read/write splitting, or master/standby DCS instance.If the target is a cluster instance (a clust", "doc_type":"usermanual", "kw":"Can I Migrate Data from a Multi-DB Source Redis Instance to a Cluster DCS Redis Instance?,Data Backu", "search_title":"", @@ -4191,7 +4332,7 @@ "uri":"dcs-migration-0312018.html", "node_id":"dcs-migration-0312018.xml", "product_code":"dcs", - "code":"203", + "code":"210", "des":"The online migration function provided on the console does not support migration of specified DBs. If you want to migrate specified Redis DBs, use redis-shake to export o", "doc_type":"usermanual", "kw":"How Can I Migrate Partial Data?,Data Backup, Export, and Migration,User Guide", @@ -4212,7 +4353,7 @@ "uri":"dcs-migration-0312019.html", "node_id":"dcs-migration-0312019.xml", "product_code":"dcs", - "code":"204", + "code":"211", "des":"Proxy Cluster instancesProxy Cluster instances are used in the same way that you use single-node or master/standby instances. However, only one DB is configured for a Pro", "doc_type":"usermanual", "kw":"What Are the Constraints and Precautions for Migrating Redis Data to a Cluster Instance?,Data Backup", @@ -4233,7 +4374,7 @@ "uri":"dcs-migration-0312020.html", "node_id":"dcs-migration-0312020.xml", "product_code":"dcs", - "code":"205", + "code":"212", "des":"NetworkBefore online migration, ensure that the network configured for the migration task is connected to source and target Redis instances.Before online migration, ensur", "doc_type":"usermanual", "kw":"What Should I Consider for Online Migration?,Data Backup, Export, and Migration,User Guide", @@ -4254,7 +4395,7 @@ "uri":"dcs-migration-0312021.html", "node_id":"dcs-migration-0312021.xml", "product_code":"dcs", - "code":"206", + "code":"213", "des":"Yes. You can use the application dual-write mode. In this mode, during data migration, data is still read from the source Redis instance, and operations such as adding, d", "doc_type":"usermanual", "kw":"Can I Perform Online Migration Without Any Service Interruption?,Data Backup, Export, and Migration,", @@ -4275,7 +4416,7 @@ "uri":"dcs-migration-211125001.html", "node_id":"dcs-migration-211125001.xml", "product_code":"dcs", - "code":"207", + "code":"214", "des":"The following error messages may be displayed during online migration:\"Disconnecting timedout slave\" is reported on the source instance, as shown in the following figure:", "doc_type":"usermanual", "kw":"What If \"Disconnecting timedout slave\" and \"overcoming of output buffer limits\" Are Reported on the ", @@ -4296,7 +4437,7 @@ "uri":"dcs-faq-0427076.html", "node_id":"dcs-faq-0427076.xml", "product_code":"dcs", - "code":"208", + "code":"215", "des":"For details on how to use Rump, see the Data Migration Guide.Possible causes:Rump does not support migration to cluster DCS instances.Commands are incorrectly run in Rump", "doc_type":"usermanual", "kw":"Why Is Memory of a DCS Redis Instance Unchanged After Data Migration Using Rump, Even If No Error Me", @@ -4317,7 +4458,7 @@ "uri":"dcs-migration-0715005.html", "node_id":"dcs-migration-0715005.xml", "product_code":"dcs", - "code":"209", + "code":"216", "des":"Yes. Redis is backward compatible.The version of the source Redis (DCS, self-built, or another cloud) can be earlier than or the same as the target DCS instance.", "doc_type":"usermanual", "kw":"Can I Migrate Data from a Lower Redis Version to a Higher One?,Data Backup, Export, and Migration,Us", @@ -4338,7 +4479,7 @@ "uri":"dcs-faq-0805001.html", "node_id":"dcs-faq-0805001.xml", "product_code":"dcs", - "code":"210", + "code":"217", "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":"Big/Hot Key Analysis and Expired Key Scan", @@ -4359,7 +4500,7 @@ "uri":"dcs-faq-0521003.html", "node_id":"dcs-faq-0521003.xml", "product_code":"dcs", - "code":"211", + "code":"218", "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":"What Are Big Keys and Hot Keys?,Big/Hot Key Analysis and Expired Key Scan,User Guide", @@ -4380,7 +4521,7 @@ "uri":"dcs-faq-0521004.html", "node_id":"dcs-faq-0521004.xml", "product_code":"dcs", - "code":"212", + "code":"219", "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":"What Is the Impact of Big Keys or Hot Keys?,Big/Hot Key Analysis and Expired Key Scan,User Guide", @@ -4401,7 +4542,7 @@ "uri":"dcs-faq-0521005.html", "node_id":"dcs-faq-0521005.xml", "product_code":"dcs", - "code":"213", + "code":"220", "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":"usermanual", "kw":"How Do I Avoid Big Keys and Hot Keys?,Big/Hot Key Analysis and Expired Key Scan,User Guide", @@ -4422,7 +4563,7 @@ "uri":"dcs-faq-0521006.html", "node_id":"dcs-faq-0521006.xml", "product_code":"dcs", - "code":"214", + "code":"221", "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":"usermanual", "kw":"How Do I Analyze the Hot Keys of a DCS Redis 3.0 Instance?,Big/Hot Key Analysis and Expired Key Scan", @@ -4443,7 +4584,7 @@ "uri":"dcs-faq-0606002.html", "node_id":"dcs-faq-0606002.xml", "product_code":"dcs", - "code":"215", + "code":"222", "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":"usermanual", "kw":"How Do I Detect Big Keys and Hot Keys in Advance?,Big/Hot Key Analysis and Expired Key Scan,User Gui", @@ -4464,7 +4605,7 @@ "uri":"dcs-faq-210531002.html", "node_id":"dcs-faq-210531002.xml", "product_code":"dcs", - "code":"216", + "code":"223", "des":"What are the rules for scheduled deletion of expired keys on a daily basis? Can I customize the rules?Lazy free deletion: The deletion strategy is controlled in the main ", "doc_type":"usermanual", "kw":"How Does DCS Delete Expired Keys?,Big/Hot Key Analysis and Expired Key Scan,User Guide", @@ -4485,7 +4626,7 @@ "uri":"dcs-faq-210812001.html", "node_id":"dcs-faq-210812001.xml", "product_code":"dcs", - "code":"217", + "code":"224", "des":"Key storage durationKeys that do not have an expiration are stored permanently.Keys that have an expiration are deleted after they expire. For details, see Scanning Expir", "doc_type":"usermanual", "kw":"How Long Are Keys Stored? How Do I Set Key Expiration?,Big/Hot Key Analysis and Expired Key Scan,Use", @@ -4506,7 +4647,7 @@ "uri":"dcs-faq-191204001.html", "node_id":"dcs-faq-191204001.xml", "product_code":"dcs", - "code":"218", + "code":"225", "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", @@ -4527,7 +4668,7 @@ "uri":"dcs-faq-0730058.html", "node_id":"dcs-faq-0730058.xml", "product_code":"dcs", - "code":"219", + "code":"226", "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", @@ -4548,7 +4689,7 @@ "uri":"dcs-faq-0730059.html", "node_id":"dcs-faq-0730059.xml", "product_code":"dcs", - "code":"220", + "code":"227", "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", @@ -4569,7 +4710,7 @@ "uri":"dcs-faq-0730060.html", "node_id":"dcs-faq-0730060.xml", "product_code":"dcs", - "code":"221", + "code":"228", "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", @@ -4590,7 +4731,7 @@ "uri":"dcs-faq-0730061.html", "node_id":"dcs-faq-0730061.xml", "product_code":"dcs", - "code":"222", + "code":"229", "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,", @@ -4611,7 +4752,7 @@ "uri":"en-us_topic_0072429345.html", "node_id":"en-us_topic_0072429345.xml", "product_code":"dcs", - "code":"223", + "code":"230", "des":"For details about the terms involved in this document, see Glossary.", "doc_type":"usermanual", "kw":"Glossary,User Guide", @@ -4632,7 +4773,7 @@ "uri":"dcs-ug-0326026.html", "node_id":"dcs-ug-0326026.xml", "product_code":"dcs", - "code":"224", + "code":"231", "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 be635a086..ca12b72f3 100644 --- a/docs/dcs/umn/CLASS.TXT.json +++ b/docs/dcs/umn/CLASS.TXT.json @@ -71,6 +71,15 @@ "p_code":"4", "code":"8" }, + { + "desc":"This section describes read/write splitting DCS Redis 4.0/5.0 instances. Read/write splitting is implemented on the server side by default. Proxies distinguish between re", + "product_code":"dcs", + "title":"Read/Write Splitting Redis", + "uri":"dcs-pd-0220606.html", + "doc_type":"usermanual", + "p_code":"4", + "code":"9" + }, { "desc":"Table 1 describes the differences between different Redis instance types in terms of features and commands.", "product_code":"dcs", @@ -78,7 +87,7 @@ "uri":"dcs-pd-191224001.html", "doc_type":"usermanual", "p_code":"4", - "code":"9" + "code":"10" }, { "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.", @@ -87,7 +96,7 @@ "uri":"en-us_topic_0054235835.html", "doc_type":"usermanual", "p_code":"1", - "code":"10" + "code":"11" }, { "desc":"This section describes DCS Redis 3.0 instance specifications, including the total memory, available memory, maximum number of connections allowed, maximum/assured bandwid", @@ -95,8 +104,8 @@ "title":"Redis 3.0 Instance Specifications", "uri":"dcs-pd-0916001.html", "doc_type":"usermanual", - "p_code":"10", - "code":"11" + "p_code":"11", + "code":"12" }, { "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", @@ -104,17 +113,17 @@ "title":"Redis 4.0 and 5.0 Instance Specifications", "uri":"dcs-pd-0916002.html", "doc_type":"usermanual", - "p_code":"10", - "code":"12" + "p_code":"11", + "code":"13" }, { - "desc":"This section describes DCS Redis 6.0 instance specifications, including the total memory, available memory, maximum number of connections allowed, maximum/assured bandwid", + "desc":"This section describes DCS Redis 6.0/7.0 instance specifications, including the total memory, available memory, maximum number of connections allowed, maximum/assured ban", "product_code":"dcs", - "title":"Redis 6.0 Instance Specifications", + "title":"Redis 6.0 and 7.0 Instance Specifications", "uri":"dcs-pd-0916004.html", "doc_type":"usermanual", - "p_code":"10", - "code":"13" + "p_code":"11", + "code":"14" }, { "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.", @@ -123,43 +132,52 @@ "uri":"dcs-pd-200312003.html", "doc_type":"usermanual", "p_code":"1", - "code":"14" + "code":"15" }, { "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", "product_code":"dcs", - "title":"Redis 3.0 Commands", + "title":"Commands Supported and Disabled by DCS for Redis 3.0", "uri":"dcs-pd-200713005.html", "doc_type":"usermanual", - "p_code":"14", - "code":"15" + "p_code":"15", + "code":"16" }, { "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", "product_code":"dcs", - "title":"Redis 4.0 Commands", + "title":"Commands Supported and Disabled by DCS for Redis 4.0", "uri":"dcs-pd-200916001.html", "doc_type":"usermanual", - "p_code":"14", - "code":"16" + "p_code":"15", + "code":"17" }, { "desc":"DCS for Redis 5.0 is developed based on Redis 5.0.14 and is compatible with open-source protocols and commands.This section describes DCS for Redis 5.0's compatibility wi", "product_code":"dcs", - "title":"Redis 5.0 Commands", + "title":"Commands Supported and Disabled by DCS for Redis 5.0", "uri":"dcs-pd-200813002.html", "doc_type":"usermanual", - "p_code":"14", - "code":"17" + "p_code":"15", + "code":"18" }, { - "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", + "desc":"DCS for Redis 6.0 is fully compatible with open-source Redis 6.This section describes DCS for Redis 6.0's command compatibility, including supported and disabled commands", "product_code":"dcs", - "title":"Redis 6.0 Commands", + "title":"Commands Supported and Disabled by DCS for Redis 6.0", "uri":"dcs-pd-210209002.html", "doc_type":"usermanual", - "p_code":"14", - "code":"18" + "p_code":"15", + "code":"19" + }, + { + "desc":"This section describes DCS for Redis 7.0's compatibility with KeyDB commands, including supported and disabled commands.DCS Redis instances support most Redis commands. A", + "product_code":"dcs", + "title":"Commands Supported and Disabled by DCS for Redis 7.0", + "uri":"dcs_01_0001.html", + "doc_type":"usermanual", + "p_code":"15", + "code":"20" }, { "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.", @@ -167,8 +185,8 @@ "title":"Web CLI Commands", "uri":"dcs-pd-190826001.html", "doc_type":"usermanual", - "p_code":"14", - "code":"19" + "p_code":"15", + "code":"21" }, { "desc":"Some Redis commands are supported by Redis Cluster DCS instances for multi-key operations in the same slot. For details, see Table 1.Some commands support multiple keys b", @@ -176,8 +194,8 @@ "title":"Command Restrictions", "uri":"dcs-pd-200813003.html", "doc_type":"usermanual", - "p_code":"14", - "code":"20" + "p_code":"15", + "code":"22" }, { "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", @@ -185,8 +203,8 @@ "title":"Other Command Usage Restrictions", "uri":"dcs-pd-200813004.html", "doc_type":"usermanual", - "p_code":"14", - "code":"21" + "p_code":"15", + "code":"23" }, { "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", @@ -195,16 +213,16 @@ "uri":"GlobalDRPolicy.html", "doc_type":"usermanual", "p_code":"1", - "code":"22" + "code":"24" }, { - "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", + "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/7.0. The following table descr", "product_code":"dcs", "title":"Comparing Redis Versions", "uri":"RedisDifference.html", "doc_type":"usermanual", "p_code":"1", - "code":"23" + "code":"25" }, { "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", @@ -213,7 +231,7 @@ "uri":"dcs-pd-0326003.html", "doc_type":"usermanual", "p_code":"1", - "code":"24" + "code":"26" }, { "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", @@ -222,7 +240,7 @@ "uri":"dcs-pd-200312004.html", "doc_type":"usermanual", "p_code":"1", - "code":"25" + "code":"27" }, { "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", @@ -231,7 +249,7 @@ "uri":"dcs-pd-210626001.html", "doc_type":"usermanual", "p_code":"1", - "code":"26" + "code":"28" }, { "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", @@ -240,7 +258,7 @@ "uri":"dcs-pd-0326006.html", "doc_type":"usermanual", "p_code":"1", - "code":"27" + "code":"29" }, { "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 +267,7 @@ "uri":"en-us_topic_0054235836.html", "doc_type":"usermanual", "p_code":"1", - "code":"28" + "code":"30" }, { "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", @@ -257,8 +275,8 @@ "title":"How to Access DCS", "uri":"en-us_topic_0054235837.html", "doc_type":"usermanual", - "p_code":"28", - "code":"29" + "p_code":"30", + "code":"31" }, { "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", @@ -266,8 +284,8 @@ "title":"User Permissions", "uri":"en-us_topic_0054247786.html", "doc_type":"usermanual", - "p_code":"28", - "code":"30" + "p_code":"30", + "code":"32" }, { "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 +294,7 @@ "uri":"dcs-ug-210626003.html", "doc_type":"usermanual", "p_code":"", - "code":"31" + "code":"33" }, { "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", @@ -284,8 +302,8 @@ "title":"Creating a User and Granting DCS Permissions", "uri":"dcs-ug-210626004.html", "doc_type":"usermanual", - "p_code":"31", - "code":"32" + "p_code":"33", + "code":"34" }, { "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", @@ -293,8 +311,8 @@ "title":"DCS Custom Policies", "uri":"dcs-ug-210626005.html", "doc_type":"usermanual", - "p_code":"31", - "code":"33" + "p_code":"33", + "code":"35" }, { "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.", @@ -303,7 +321,7 @@ "uri":"dcs-ug-0326007.html", "doc_type":"usermanual", "p_code":"", - "code":"34" + "code":"36" }, { "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.", @@ -311,8 +329,8 @@ "title":"Creating an Instance", "uri":"dcs-ug-0312003.html", "doc_type":"usermanual", - "p_code":"34", - "code":"35" + "p_code":"36", + "code":"37" }, { "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", @@ -320,8 +338,8 @@ "title":"Identifying Requirements", "uri":"PurchasePreparation.html", "doc_type":"usermanual", - "p_code":"35", - "code":"36" + "p_code":"37", + "code":"38" }, { "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 ", @@ -329,8 +347,8 @@ "title":"Preparing Required Resources", "uri":"dcs-ug-0312004.html", "doc_type":"usermanual", - "p_code":"35", - "code":"37" + "p_code":"37", + "code":"39" }, { "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", @@ -338,8 +356,8 @@ "title":"Creating a DCS Redis Instance", "uri":"dcs-ug-0326008.html", "doc_type":"usermanual", - "p_code":"35", - "code":"38" + "p_code":"37", + "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.", @@ -347,17 +365,17 @@ "title":"Accessing an Instance", "uri":"dcs-ug-0916002.html", "doc_type":"usermanual", - "p_code":"34", - "code":"39" + "p_code":"36", + "code":"41" }, { - "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 ", + "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.The follow", "product_code":"dcs", "title":"Accessing a DCS Redis Instance Through redis-cli", "uri":"dcs-ug-0326009.html", "doc_type":"usermanual", - "p_code":"39", - "code":"40" + "p_code":"41", + "code":"42" }, { "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.", @@ -365,8 +383,8 @@ "title":"Access in Different Languages", "uri":"dcs-ug-0512002.html", "doc_type":"usermanual", - "p_code":"39", - "code":"41" + "p_code":"41", + "code":"43" }, { "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.", @@ -374,71 +392,71 @@ "title":"Java", "uri":"dcs-ug-211105003.html", "doc_type":"usermanual", - "p_code":"41", - "code":"42" - }, - { - "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.Spring Da", - "product_code":"dcs", - "title":"Jedis", - "uri":"dcs-ug-0713005.html", - "doc_type":"usermanual", - "p_code":"42", - "code":"43" - }, - { - "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.Spring ", - "product_code":"dcs", - "title":"Lettuce", - "uri":"dcs-ug-211105002.html", - "doc_type":"usermanual", - "p_code":"42", + "p_code":"43", "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.For Sp", + "desc":"This section describes how to access a Redis instance on Jedis. For more information about how to use other Redis clients, visit the Redis official website.Spring Data Re", "product_code":"dcs", - "title":"Redisson", - "uri":"dcs-ug-211105004.html", + "title":"Connecting to Redis on Jedis (Java)", + "uri":"dcs-ug-0713005.html", "doc_type":"usermanual", - "p_code":"42", + "p_code":"44", "code":"45" }, { - "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", + "desc":"This section describes how to access a Redis instance on Lettuce. For more information about how to use other Redis clients, visit the Redis official website.Spring Data ", "product_code":"dcs", - "title":"Clients in Python", - "uri":"dcs-ug-0312011.html", + "title":"Connecting to Redis on Lettuce (Java)", + "uri":"dcs-ug-211105002.html", "doc_type":"usermanual", - "p_code":"41", + "p_code":"44", "code":"46" }, { - "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 ", + "desc":"This section describes how to access a Redis instance on Redisson. For more information about how to use other Redis clients, visit the Redis official website.For Spring ", "product_code":"dcs", - "title":"go-redis", - "uri":"dcs-ug-211105001.html", + "title":"Connecting to Redis on Redisson (Java)", + "uri":"dcs-ug-211105004.html", "doc_type":"usermanual", - "p_code":"41", + "p_code":"44", "code":"47" }, { - "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", + "desc":"This section describes how to access a Redis instance on redis-py. For more information about how to use other Redis clients, visit the Redis official website.The followi", "product_code":"dcs", - "title":"hiredis in C++", - "uri":"dcs-ug-0312010.html", + "title":"Connecting to Redis on redis-py (Python)", + "uri":"dcs-ug-0312011.html", "doc_type":"usermanual", - "p_code":"41", + "p_code":"43", "code":"48" }, { - "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", + "desc":"This section describes how to access a Redis instance on go-redis. For more information about how to use other Redis clients, visit the Redis official website.The followi", "product_code":"dcs", - "title":"C#", + "title":"Connecting to Redis on go-redis (Go)", + "uri":"dcs-ug-211105001.html", + "doc_type":"usermanual", + "p_code":"43", + "code":"49" + }, + { + "desc":"This section describes how to access a Redis instance on hiredis (C++). For more information about how to use other Redis clients, visit the Redis official website.The fo", + "product_code":"dcs", + "title":"Connecting to Redis on hiredis (C++)", + "uri":"dcs-ug-0312010.html", + "doc_type":"usermanual", + "p_code":"43", + "code":"50" + }, + { + "desc":"This section describes how to access a Redis instance on StackExchange.Redis. For more information about how to use other Redis clients, visit the Redis official website.", + "product_code":"dcs", + "title":"Connecting to Redis on StackExchange.Redis (C#)", "uri":"dcs-ug-0312013.html", "doc_type":"usermanual", - "p_code":"41", - "code":"49" + "p_code":"43", + "code":"51" }, { "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.", @@ -446,53 +464,53 @@ "title":"PHP", "uri":"dcs-ug-211202001.html", "doc_type":"usermanual", - "p_code":"41", - "code":"50" - }, - { - "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", - "product_code":"dcs", - "title":"phpredis", - "uri":"dcs-ug-0312009.html", - "doc_type":"usermanual", - "p_code":"50", - "code":"51" - }, - { - "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", - "product_code":"dcs", - "title":"Predis", - "uri":"dcs-ug-211202002.html", - "doc_type":"usermanual", - "p_code":"50", + "p_code":"43", "code":"52" }, { - "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", + "desc":"This section describes how to connect to Redis on phpredis. For more information about how to use other Redis clients, visit the Redis official website.The following oper", "product_code":"dcs", - "title":"Node.js", + "title":"Connecting to Redis on phpredis (PHP)", + "uri":"dcs-ug-0312009.html", + "doc_type":"usermanual", + "p_code":"52", + "code":"53" + }, + { + "desc":"This section describes how to connect to Redis on predis. For more information about how to use other Redis clients, visit the Redis official website.The following operat", + "product_code":"dcs", + "title":"Connecting to Redis on predis (PHP)", + "uri":"dcs-ug-211202002.html", + "doc_type":"usermanual", + "p_code":"52", + "code":"54" + }, + { + "desc":"This section describes how to access a Redis instance on ioredis. For more information about how to use other Redis clients, visit the Redis official website.The followin", + "product_code":"dcs", + "title":"Connecting to Redis on ioredis (Node.js)", "uri":"dcs-ug-0312012.html", "doc_type":"usermanual", - "p_code":"41", - "code":"53" + "p_code":"43", + "code":"55" }, { "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/5.0/6.0 Instance on the Console", + "title":"Accessing a DCS Redis Instance on the Console", "uri":"dcs-ug-0312008.html", "doc_type":"usermanual", - "p_code":"39", - "code":"54" + "p_code":"41", + "code":"56" }, { "desc":"On the DCS console, you can view DCS instance details.Search by keyword.If you do not select an attribute and enter a keyword in the search box, the system searches for i", "product_code":"dcs", - "title":"Viewing Details of a DCS Instance", + "title":"Viewing and Modifying DCS Instance Information", "uri":"dcs-ug-0312016.html", "doc_type":"usermanual", - "p_code":"34", - "code":"55" + "p_code":"36", + "code":"57" }, { "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.", @@ -501,7 +519,7 @@ "uri":"dcs-ug-0312015.html", "doc_type":"usermanual", "p_code":"", - "code":"56" + "code":"58" }, { "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 the modification failed in", @@ -509,8 +527,8 @@ "title":"Modifying DCS Instance Specifications", "uri":"dcs-ug-0326011.html", "doc_type":"usermanual", - "p_code":"56", - "code":"57" + "p_code":"58", + "code":"59" }, { "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", @@ -518,17 +536,17 @@ "title":"Starting DCS Instances", "uri":"dcs-ug-0911001.html", "doc_type":"usermanual", - "p_code":"56", - "code":"58" + "p_code":"58", + "code":"60" }, { - "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 ", + "desc":"On the DCS console, you can restart one or multiple DCS instances at a time.Restarting a single-node DCS instance or other types of DCS instances with AOF persistence dis", "product_code":"dcs", "title":"Restarting DCS Instances", "uri":"dcs-ug-0326013.html", "doc_type":"usermanual", - "p_code":"56", - "code":"59" + "p_code":"58", + "code":"61" }, { "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", @@ -536,8 +554,8 @@ "title":"Deleting DCS Instances", "uri":"dcs-ug-0326014.html", "doc_type":"usermanual", - "p_code":"56", - "code":"60" + "p_code":"58", + "code":"62" }, { "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", @@ -545,8 +563,8 @@ "title":"Performing a Master/Standby Switchover for a DCS Instance", "uri":"dcs-ug-0312017.html", "doc_type":"usermanual", - "p_code":"56", - "code":"61" + "p_code":"58", + "code":"63" }, { "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", @@ -554,8 +572,8 @@ "title":"Clearing DCS Instance Data", "uri":"dcs-ug-0312018.html", "doc_type":"usermanual", - "p_code":"56", - "code":"62" + "p_code":"58", + "code":"64" }, { "desc":"On the DCS console, you can export DCS instance information in full to an Excel file.", @@ -563,8 +581,8 @@ "title":"Exporting DCS Instance List", "uri":"dcs-ug-0312019.html", "doc_type":"usermanual", - "p_code":"56", - "code":"63" + "p_code":"58", + "code":"65" }, { "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, FLUSHALL, HGE", @@ -572,8 +590,8 @@ "title":"Command Renaming", "uri":"dcs-ug-1009002.html", "doc_type":"usermanual", - "p_code":"56", - "code":"64" + "p_code":"58", + "code":"66" }, { "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.", @@ -582,7 +600,7 @@ "uri":"dcs-ug-0312022.html", "doc_type":"usermanual", "p_code":"", - "code":"65" + "code":"67" }, { "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", @@ -590,8 +608,8 @@ "title":"Configuration Notice", "uri":"dcs-ug-0312023.html", "doc_type":"usermanual", - "p_code":"65", - "code":"66" + "p_code":"67", + "code":"68" }, { "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, ", @@ -599,8 +617,8 @@ "title":"Modifying Configuration Parameters", "uri":"dcs-ug-0312024.html", "doc_type":"usermanual", - "p_code":"65", - "code":"67" + "p_code":"67", + "code":"69" }, { "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", @@ -608,8 +626,8 @@ "title":"Modifying Maintenance Time Window", "uri":"dcs-ug-0312025.html", "doc_type":"usermanual", - "p_code":"65", - "code":"68" + "p_code":"67", + "code":"70" }, { "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", @@ -617,8 +635,8 @@ "title":"Modifying the Security Group", "uri":"dcs-ug-0312026.html", "doc_type":"usermanual", - "p_code":"65", - "code":"69" + "p_code":"67", + "code":"71" }, { "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", @@ -626,17 +644,8 @@ "title":"Viewing Background Tasks", "uri":"dcs-ug-0312028.html", "doc_type":"usermanual", - "p_code":"65", - "code":"70" - }, - { - "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", - "product_code":"dcs", - "title":"Viewing Data Storage Statistics of a DCS Redis 3.0 Proxy Cluster Instance", - "uri":"dcs-ug-0312029.html", - "doc_type":"usermanual", - "p_code":"65", - "code":"71" + "p_code":"67", + "code":"72" }, { "desc":"Tags facilitate DCS instance identification and management.You can add tags to an instance when creating it or add, modify, or delete tags on the details page of a create", @@ -644,17 +653,17 @@ "title":"Managing Tags", "uri":"TagManagement.html", "doc_type":"usermanual", - "p_code":"65", - "code":"72" + "p_code":"67", + "code":"73" }, { - "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", + "desc":"This section describes how to query the shards and replicas of a DCS Redis 4.0 or later instance and how to manually promote a replica to master.Currently, this function ", "product_code":"dcs", "title":"Managing Shards and Replicas", "uri":"dcs-ug-210107001.html", "doc_type":"usermanual", - "p_code":"65", - "code":"73" + "p_code":"67", + "code":"74" }, { "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", @@ -662,17 +671,17 @@ "title":"Analyzing Big Keys and Hot Keys", "uri":"dcs-ug-190808001.html", "doc_type":"usermanual", - "p_code":"65", - "code":"74" + "p_code":"67", + "code":"75" }, { "desc":"There are two ways to delete a key in Redis.Use the DEL command to directly delete a key.Use commands such as EXPIRE to set a timeout on a key. After the timeout elapses,", "product_code":"dcs", - "title":"Scanning Expired Keys", + "title":"Scanning and Deleting Expired Keys in a DCS Redis Instance", "uri":"dcs-ug-210330002.html", "doc_type":"usermanual", - "p_code":"65", - "code":"75" + "p_code":"67", + "code":"76" }, { "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", @@ -680,8 +689,8 @@ "title":"Managing IP Address Whitelist", "uri":"dcs-ug-190812001.html", "doc_type":"usermanual", - "p_code":"65", - "code":"76" + "p_code":"67", + "code":"77" }, { "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", @@ -689,8 +698,8 @@ "title":"Viewing Redis Slow Queries", "uri":"dcs-ug-190926001.html", "doc_type":"usermanual", - "p_code":"65", - "code":"77" + "p_code":"67", + "code":"78" }, { "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", @@ -698,17 +707,44 @@ "title":"Viewing Redis Run Logs", "uri":"dcs-ug-1009001.html", "doc_type":"usermanual", - "p_code":"65", - "code":"78" + "p_code":"67", + "code":"79" }, { - "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 ", + "desc":"If a fault or performance issue occurs, you can ask DCS to diagnose your instance to learn about the cause and impact of the issue and how to handle it.Tested Object: You", "product_code":"dcs", - "title":"Configuring SSL", + "title":"Diagnosing an Instance", + "uri":"dcs-ug-210818001.html", + "doc_type":"usermanual", + "p_code":"67", + "code":"80" + }, + { + "desc":"Single-node, master/standby, and Redis ClusterDCS Redis 6.0/7.0instances support SSL encryption to ensure data transmission security. This function is not available for o", + "product_code":"dcs", + "title":"Transmitting DCS Redis Data with Encryption Using SSL", "uri":"dcs-ug-023129.html", "doc_type":"usermanual", - "p_code":"65", - "code":"79" + "p_code":"67", + "code":"81" + }, + { + "desc":"You can view the client connection information of an instance and disconnect clients.This function is supported by DCS Redis 4.0 instances and later.The session managemen", + "product_code":"dcs", + "title":"Managing Sessions", + "uri":"dcs-ug-22121.html", + "doc_type":"usermanual", + "p_code":"67", + "code":"82" + }, + { + "desc":"You can create read-only and read/write users to control access permissions.This function is supported only by DCS Redis 4.0 and 5.0 instances.Default user: defaultA maxi", + "product_code":"dcs", + "title":"Managing Users", + "uri":"dcs-ug-221220.html", + "doc_type":"usermanual", + "p_code":"67", + "code":"83" }, { "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.", @@ -717,7 +753,7 @@ "uri":"dcs-ug-0312030.html", "doc_type":"usermanual", "p_code":"", - "code":"80" + "code":"84" }, { "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", @@ -725,8 +761,8 @@ "title":"Overview", "uri":"en-us_topic_0079835992.html", "doc_type":"usermanual", - "p_code":"80", - "code":"81" + "p_code":"84", + "code":"85" }, { "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", @@ -734,8 +770,8 @@ "title":"Configuring an Automatic Backup Policy", "uri":"dcs-ug-0312031.html", "doc_type":"usermanual", - "p_code":"80", - "code":"82" + "p_code":"84", + "code":"86" }, { "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", @@ -743,8 +779,8 @@ "title":"Manually Backing Up a DCS Instance", "uri":"dcs-ug-0312032.html", "doc_type":"usermanual", - "p_code":"80", - "code":"83" + "p_code":"84", + "code":"87" }, { "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", @@ -752,8 +788,8 @@ "title":"Restoring a DCS Instance", "uri":"dcs-ug-0312033.html", "doc_type":"usermanual", - "p_code":"80", - "code":"84" + "p_code":"84", + "code":"88" }, { "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 ", @@ -761,8 +797,8 @@ "title":"Downloading a Backup File", "uri":"dcs-ug-0312034.html", "doc_type":"usermanual", - "p_code":"80", - "code":"85" + "p_code":"84", + "code":"89" }, { "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.", @@ -771,7 +807,7 @@ "uri":"dcs-ug-0312035.html", "doc_type":"usermanual", "p_code":"", - "code":"86" + "code":"90" }, { "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", @@ -779,8 +815,8 @@ "title":"Introduction to Migration with DCS", "uri":"dcs-ug-0312036.html", "doc_type":"usermanual", - "p_code":"86", - "code":"87" + "p_code":"90", + "code":"91" }, { "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 +824,8 @@ "title":"Importing Backup Files", "uri":"dcs-ug-210922001.html", "doc_type":"usermanual", - "p_code":"86", - "code":"88" + "p_code":"90", + "code":"92" }, { "desc":"Use the DCS console to migrate backup data to DCS for Redis.Simply download the source Redis backup data and then upload the data to an OBS bucket in the same region as t", @@ -797,8 +833,8 @@ "title":"Importing Backup Files from an OBS Bucket", "uri":"dcs-ug-0312037.html", "doc_type":"usermanual", - "p_code":"88", - "code":"89" + "p_code":"92", + "code":"93" }, { "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", @@ -806,8 +842,8 @@ "title":"Importing Backup Files from Redis", "uri":"dcs-ug-210226001.html", "doc_type":"usermanual", - "p_code":"88", - "code":"90" + "p_code":"92", + "code":"94" }, { "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", @@ -815,8 +851,17 @@ "title":"Migrating Data Online", "uri":"dcs-ug-0312038.html", "doc_type":"usermanual", - "p_code":"86", - "code":"91" + "p_code":"90", + "code":"95" + }, + { + "desc":"Currently, you cannot change the instance type when using the specification modification function. To modify instance specifications while changing the instance type, you", + "product_code":"dcs", + "title":"Switching DCS Instance IP Addresses", + "uri":"dcs-ug-210820001.html", + "doc_type":"usermanual", + "p_code":"90", + "code":"96" }, { "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.", @@ -825,7 +870,7 @@ "uri":"dcs-ug-0312039.html", "doc_type":"usermanual", "p_code":"", - "code":"92" + "code":"97" }, { "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", @@ -833,8 +878,8 @@ "title":"DCS Instance Passwords", "uri":"cache-instance-password.html", "doc_type":"usermanual", - "p_code":"92", - "code":"93" + "p_code":"97", + "code":"98" }, { "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", @@ -842,8 +887,26 @@ "title":"Changing Instance Passwords", "uri":"dcs-ug-0312040.html", "doc_type":"usermanual", - "p_code":"92", - "code":"94" + "p_code":"97", + "code":"99" + }, + { + "desc":"On the DCS console, you can configure a new password if you forget your instance password.For a DCS Redis instance, you can change it from password mode to password-free ", + "product_code":"dcs", + "title":"Resetting Instance Passwords", + "uri":"dcs-ug-0312041.html", + "doc_type":"usermanual", + "p_code":"97", + "code":"100" + }, + { + "desc":"DCS Redis instances can be accessed with or without passwords. After an instance is created, you can change its password setting in the following scenarios:To access a DC", + "product_code":"dcs", + "title":"Changing Password Settings for DCS Redis Instances", + "uri":"dcs-ug-0312042.html", + "doc_type":"usermanual", + "p_code":"97", + "code":"101" }, { "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 +915,7 @@ "uri":"dcs-ug-210622001.html", "doc_type":"usermanual", "p_code":"", - "code":"95" + "code":"102" }, { "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", @@ -860,8 +923,8 @@ "title":"Viewing Parameter Templates", "uri":"dcs-ug-210622002.html", "doc_type":"usermanual", - "p_code":"95", - "code":"96" + "p_code":"102", + "code":"103" }, { "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", @@ -869,8 +932,8 @@ "title":"Creating a Custom Parameter Template", "uri":"dcs-ug-210622003.html", "doc_type":"usermanual", - "p_code":"95", - "code":"97" + "p_code":"102", + "code":"104" }, { "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", @@ -878,8 +941,8 @@ "title":"Modifying a Custom Parameter Template", "uri":"dcs-ug-210622004.html", "doc_type":"usermanual", - "p_code":"95", - "code":"98" + "p_code":"102", + "code":"105" }, { "desc":"This section describes how to delete a custom parameter template.", @@ -887,8 +950,8 @@ "title":"Deleting a Custom Parameter Template", "uri":"dcs-ug-210622005.html", "doc_type":"usermanual", - "p_code":"95", - "code":"99" + "p_code":"102", + "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.", @@ -897,7 +960,7 @@ "uri":"dcs-ug-0326016.html", "doc_type":"usermanual", "p_code":"", - "code":"100" + "code":"107" }, { "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", @@ -905,8 +968,8 @@ "title":"DCS Metrics", "uri":"dcs-ug-0326019.html", "doc_type":"usermanual", - "p_code":"100", - "code":"101" + "p_code":"107", + "code":"108" }, { "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", @@ -914,8 +977,8 @@ "title":"Viewing DCS Monitoring Metrics", "uri":"dcs-ug-0312045.html", "doc_type":"usermanual", - "p_code":"100", - "code":"102" + "p_code":"107", + "code":"109" }, { "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", @@ -923,8 +986,8 @@ "title":"Configuring Alarm Rules for Critical Metrics", "uri":"dcs-ug-190905001.html", "doc_type":"usermanual", - "p_code":"100", - "code":"103" + "p_code":"107", + "code":"110" }, { "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.", @@ -933,7 +996,7 @@ "uri":"dcs-ug-0326017.html", "doc_type":"usermanual", "p_code":"", - "code":"104" + "code":"111" }, { "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", @@ -941,8 +1004,8 @@ "title":"Operations That Can Be Recorded by CTS", "uri":"dcs-ug-0326018.html", "doc_type":"usermanual", - "p_code":"104", - "code":"105" + "p_code":"111", + "code":"112" }, { "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", @@ -950,8 +1013,8 @@ "title":"Viewing Traces on the CTS Console", "uri":"dcs-ug-0312047.html", "doc_type":"usermanual", - "p_code":"104", - "code":"106" + "p_code":"111", + "code":"113" }, { "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.", @@ -960,7 +1023,7 @@ "uri":"dcs-migration-230313.html", "doc_type":"usermanual", "p_code":"", - "code":"107" + "code":"114" }, { "desc":"Due to variations of Redis application environments and scenarios, migration solutions must be detailed to address actual requirements. The time required for data migrati", @@ -968,8 +1031,8 @@ "title":"Overview", "uri":"dcs-migration-0713001.html", "doc_type":"usermanual", - "p_code":"107", - "code":"108" + "p_code":"114", + "code":"115" }, { "desc":"Collect the following information about the cached data to be migrated (based on Information to be collected for the migration):Number of instancesNumber of databases (DB", @@ -977,17 +1040,17 @@ "title":"Migration Process", "uri":"dcs-migration-0312001.html", "doc_type":"usermanual", - "p_code":"107", - "code":"109" + "p_code":"114", + "code":"116" }, { "desc":"Self-hosted Redis refers to self-hosted Redis on this service, in another cloud, or in on-premises data centers.", "product_code":"dcs", - "title":"Migration Tools and Schemes", + "title":"Migration Solution Notes", "uri":"dcs-migration-090626002.html", "doc_type":"usermanual", - "p_code":"107", - "code":"110" + "p_code":"114", + "code":"117" }, { "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,53 +1058,62 @@ "title":"Migrating Data from Self-Hosted Redis to DCS", "uri":"dcs-migration-0312002.html", "doc_type":"usermanual", - "p_code":"107", - "code":"111" + "p_code":"114", + "code":"118" }, { - "desc":"If the source and target instances are interconnected and the SYNC and PSYNC commands are supported by the source instance, data can be migrated online in full or increme", + "desc":"If the source self-host and target instances are interconnected and the SYNC and PSYNC commands are supported by the source instance, data can be migrated online in full ", "product_code":"dcs", - "title":"Online Migration of Self-Hosted Redis", + "title":"Migrating Self-Built Redis Online", "uri":"dcs-migration-190703003.html", "doc_type":"usermanual", - "p_code":"111", - "code":"112" + "p_code":"118", + "code":"119" }, { - "desc":"Use the DCS console to migrate Redis data from Redis of another cloud or self-hosted Redis to DCS for Redis.Simply download the source Redis data and then upload the data", + "desc":"This section describes how to migrate self-hosted Redis to DCS by importing backup files.Simply download the source Redis data and then upload the data to an OBS bucket i", "product_code":"dcs", - "title":"Backup Migration of Self-Hosted Redis", + "title":"Self-Hosted Redis Migration with Backup Files", "uri":"dcs-migration-190703002.html", "doc_type":"usermanual", - "p_code":"111", - "code":"113" + "p_code":"118", + "code":"120" }, { - "desc":"redis-cli is the command line tool of Redis, which can be used after you install the Redis server.Run the following command to download Redis:wget http://download.redis.i", + "desc":"redis-cli is the command line tool of Redis, which can be used after you install the Redis server. This section describes how to use redis-cli to migrate a data from a se", "product_code":"dcs", "title":"Self-Hosted Redis Migration with redis-cli (AOF)", "uri":"dcs-migration-0312010.html", "doc_type":"usermanual", - "p_code":"111", - "code":"114" + "p_code":"118", + "code":"121" }, { - "desc":"redis-cli is the command line tool of Redis, which can be used after you install the Redis server.redis-cli supports data export as an RDB file. If your Redis service doe", + "desc":"redis-cli is the command line tool of Redis, which can be used after you install the Redis server. redis-cli supports data export as an RDB file. If your Redis service do", "product_code":"dcs", "title":"Self-Hosted Redis Migration with redis-cli (RDB)", "uri":"dcs-migration-0312011.html", "doc_type":"usermanual", - "p_code":"111", - "code":"115" + "p_code":"118", + "code":"122" }, { "desc":"redis-shake is an open-source tool for migrating data online or offline (by importing backup files) between Redis Clusters. Data can be migrated to DCS Redis Cluster inst", "product_code":"dcs", - "title":"Self-Hosted Redis Cluster Migration with redis-shake", + "title":"Self-Hosted Redis Cluster Migration with redis-shake (Online)", "uri":"dcs-migrate-demo02.html", "doc_type":"usermanual", - "p_code":"111", - "code":"116" + "p_code":"118", + "code":"123" + }, + { + "desc":"redis-shake is an open-source tool for migrating data online or offline (by importing backup files) between Redis Clusters. Data can be migrated to DCS Redis Cluster inst", + "product_code":"dcs", + "title":"Self-Hosted Redis Cluster Migration with redis-shake (RDB)", + "uri":"dcs-migrate-demo03.html", + "doc_type":"usermanual", + "p_code":"118", + "code":"124" }, { "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.", @@ -1049,80 +1121,80 @@ "title":"Migrating Data Between DCS Instances", "uri":"dcs-migration-0312008.html", "doc_type":"usermanual", - "p_code":"107", - "code":"117" + "p_code":"114", + "code":"125" }, { "desc":"If the source and target instances are interconnected and the SYNC and PSYNC commands are supported by the source instance, data can be migrated online in full or increme", "product_code":"dcs", - "title":"Online Migration Between DCS Redis Instances", + "title":"Online Migration Between Instances", "uri":"dcs-migration-0312003.html", "doc_type":"usermanual", - "p_code":"117", - "code":"118" + "p_code":"125", + "code":"126" }, { - "desc":"Use the DCS console to migrate Redis data from Redis of another cloud or self-hosted Redis to DCS for Redis.Simply download the source Redis data and then upload the data", + "desc":"You can migrate data between DCS instances by importing backup files.If the source Redis and target Redis are in the same region under the same DCS account, and the sourc", "product_code":"dcs", - "title":"Backup Migration Between Regions or Redis Versions", + "title":"Backup Import Between DCS Redis Instances", "uri":"dcs-migration-0312004.html", "doc_type":"usermanual", - "p_code":"117", - "code":"119" + "p_code":"125", + "code":"127" }, { "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":"Migrating Redis Data from Another Cloud to DCS", + "title":"Migration from Another Cloud", "uri":"dcs-migration-0312005.html", "doc_type":"usermanual", - "p_code":"107", - "code":"120" + "p_code":"114", + "code":"128" }, { "desc":"If the source and target instances are interconnected and the SYNC and PSYNC commands are supported by the source instance, data can be migrated online in full or increme", "product_code":"dcs", - "title":"Online Migration from Another Cloud", + "title":"Migrating Redis from Another Cloud Online", "uri":"dcs-migration-0312006.html", "doc_type":"usermanual", - "p_code":"120", - "code":"121" + "p_code":"128", + "code":"129" }, { - "desc":"Use the DCS console to migrate Redis data from Redis of another cloud or self-hosted Redis to DCS for Redis.Simply download the source Redis data and then upload the data", + "desc":"This section describes how to migrate Redis from another cloud to DCS by importing backup files.Simply download the source Redis data and then upload the data to an OBS b", "product_code":"dcs", - "title":"Backup Migration from Another Cloud", + "title":"Backup Import from Another Cloud", "uri":"dcs-migration-1117001.html", "doc_type":"usermanual", - "p_code":"120", - "code":"122" + "p_code":"128", + "code":"130" }, { "desc":"Redis instances provided by some cloud service vendors do not allow SLAVEOF, BGSAVE, and PSYNC commands to be issued from Redis clients. As a result, redis-cli, redis-sha", "product_code":"dcs", - "title":"Online Migration with Rump", + "title":"Online Migration from Another Cloud Using Rump", "uri":"dcs-migration-090626001_0.html", "doc_type":"usermanual", - "p_code":"120", - "code":"123" + "p_code":"128", + "code":"131" }, { "desc":"redis-shake is an open-source tool for migrating data online or offline (by importing backup files) between Redis Clusters. If the source Redis Cluster is deployed in ano", "product_code":"dcs", - "title":"Offline Migration of Redis Cluster from Another Cloud with redis-shake", + "title":"Backup Import from Another Cloud Using redis-shake", "uri":"dcs-migrate-1117003.html", "doc_type":"usermanual", - "p_code":"120", - "code":"124" + "p_code":"128", + "code":"132" }, { "desc":"redis-shake is an open-source Redis migration tool. Its rump mode allows you to obtain the full data of a source Redis using the SCAN command and write the data to a targ", "product_code":"dcs", - "title":"Online Full Migration of Redis from Another Cloud with redis-shake", + "title":"Migrating from Another Cloud Online Using redis-shake", "uri":"dcs-migrate-0220411.html", "doc_type":"usermanual", - "p_code":"120", - "code":"125" + "p_code":"128", + "code":"133" }, { "desc":"You can use the online migration function of the DCS console to migrate DCS Redis instances to your self-hosted Redis. You can also export the DCS instance data to an RDB", @@ -1130,8 +1202,8 @@ "title":"Migrating Data from DCS to Self-Hosted Redis", "uri":"dcs-migration-0312007.html", "doc_type":"usermanual", - "p_code":"107", - "code":"126" + "p_code":"114", + "code":"134" }, { "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.", @@ -1140,7 +1212,7 @@ "uri":"dcs-faq-0326019.html", "doc_type":"usermanual", "p_code":"", - "code":"127" + "code":"135" }, { "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.", @@ -1148,8 +1220,8 @@ "title":"Client and Network Connection", "uri":"dcs-faq-0326020.html", "doc_type":"usermanual", - "p_code":"127", - "code":"128" + "p_code":"135", + "code":"136" }, { "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", @@ -1157,17 +1229,17 @@ "title":"Security Group Configurations", "uri":"en-us_topic_0090662012.html", "doc_type":"usermanual", - "p_code":"128", - "code":"129" + "p_code":"136", + "code":"137" }, { - "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", + "desc":"No. DCS instances cannot be accessed at their EIPs over public networks. To ensure security, the ECS that serves as a client and the DCS instance that the client will acc", "product_code":"dcs", "title":"Does DCS Support Access over Public Networks?", "uri":"dcs-faq-0730001.html", "doc_type":"usermanual", - "p_code":"128", - "code":"130" + "p_code":"136", + "code":"138" }, { "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", @@ -1175,8 +1247,8 @@ "title":"Does DCS Support Cross-VPC Access?", "uri":"en-us_topic_0100698850.html", "doc_type":"usermanual", - "p_code":"128", - "code":"131" + "p_code":"136", + "code":"139" }, { "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.", @@ -1184,8 +1256,8 @@ "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":"128", - "code":"132" + "p_code":"136", + "code":"140" }, { "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", @@ -1193,8 +1265,8 @@ "title":"What Should I Do If Access to DCS Fails After Server Disconnects?", "uri":"dcs-faq-0730004.html", "doc_type":"usermanual", - "p_code":"128", - "code":"133" + "p_code":"136", + "code":"141" }, { "desc":"Occasional timeout errors are normal because of network connectivity and client timeout configurations.You are advised to include reconnection operations into your servic", @@ -1202,8 +1274,8 @@ "title":"Why Do Requests Sometimes Time Out in Clients?", "uri":"dcs-faq-0730005.html", "doc_type":"usermanual", - "p_code":"128", - "code":"134" + "p_code":"136", + "code":"142" }, { "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 ", @@ -1211,8 +1283,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":"128", - "code":"135" + "p_code":"136", + "code":"143" }, { "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", @@ -1220,8 +1292,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":"128", - "code":"136" + "p_code":"136", + "code":"144" }, { "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 ", @@ -1229,8 +1301,8 @@ "title":"How Do I Access a DCS Redis Instance Through Redis Desktop Manager?", "uri":"dcs-faq-0730008.html", "doc_type":"usermanual", - "p_code":"128", - "code":"137" + "p_code":"136", + "code":"145" }, { "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", @@ -1238,8 +1310,8 @@ "title":"What If \"ERR Unsupported CONFIG subcommand\" is Displayed in SpringCloud?", "uri":"dcs-faq-0730009.html", "doc_type":"usermanual", - "p_code":"128", - "code":"138" + "p_code":"136", + "code":"146" }, { "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", @@ -1247,8 +1319,8 @@ "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":"128", - "code":"139" + "p_code":"136", + "code":"147" }, { "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", @@ -1256,8 +1328,8 @@ "title":"What Should Be Noted When Using Redis for Pub/Sub?", "uri":"dcs-faq-0730011.html", "doc_type":"usermanual", - "p_code":"128", - "code":"140" + "p_code":"136", + "code":"148" }, { "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", @@ -1265,8 +1337,8 @@ "title":"How Do I Troubleshoot Redis Connection Failures?", "uri":"dcs-faq-0730010.html", "doc_type":"usermanual", - "p_code":"128", - "code":"141" + "p_code":"136", + "code":"149" }, { "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.", @@ -1274,8 +1346,8 @@ "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":"128", - "code":"142" + "p_code":"136", + "code":"150" }, { "desc":"The comparison between Lettuce and Jedis is as follows:LettuceLettuce does not perform connection keepalive detection. If an abnormal connection exists in the connection ", @@ -1283,26 +1355,26 @@ "title":"Connection Pool Selection and Recommended Jedis Parameter Settings", "uri":"dcs-faq-211230001.html", "doc_type":"usermanual", - "p_code":"128", - "code":"143" + "p_code":"136", + "code":"151" }, { - "desc":"Single-node, and Proxy Cluster:Each instance has only one IP address and one domain name address. The addresses remain unchanged before and after master/standby switchove", + "desc":"Single-node, read/write splitting, and Proxy Cluster:Each instance has only one IP address and one domain name address. The addresses remain unchanged before and after ma", "product_code":"dcs", "title":"Should I Use a Domain Name or an IP Address to Connect to a DCS Redis Instance?", "uri":"dcs-faq-022025.html", "doc_type":"usermanual", - "p_code":"128", - "code":"144" + "p_code":"136", + "code":"152" }, { - "desc":"A master/standby DCS Redis 4.0/5.0/6.0 instance has a Connection Address and a Read-only Address. The connection address is used to connect to the master node of the inst", + "desc":"A master/standby DCS Redis 4.0 or later instance has a Connection Address and a Read-only Address. The connection address is used to connect to the master node of the ins", "product_code":"dcs", "title":"Is the Read-only Address of a Master/Standby Instance Connected to the Master or Standby Node?", "uri":"dcs-faq-221222.html", "doc_type":"usermanual", - "p_code":"128", - "code":"145" + "p_code":"136", + "code":"153" }, { "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.", @@ -1310,8 +1382,8 @@ "title":"Redis Usage", "uri":"dcs-faq-0326021.html", "doc_type":"usermanual", - "p_code":"127", - "code":"146" + "p_code":"135", + "code":"154" }, { "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", @@ -1319,8 +1391,8 @@ "title":"Why Is CPU Usage of a DCS Redis Instance 100%?", "uri":"dcs-faq-0730012.html", "doc_type":"usermanual", - "p_code":"146", - "code":"147" + "p_code":"154", + "code":"155" }, { "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 ", @@ -1328,17 +1400,17 @@ "title":"Can I Change the VPC and Subnet for a DCS Redis Instance?", "uri":"dcs-faq-0730013.html", "doc_type":"usermanual", - "p_code":"146", - "code":"148" + "p_code":"154", + "code":"156" }, { - "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", + "desc":"Currently, DCS Redis 4.0 and later instances use VPC endpoints and do not support security groups. You can configure whitelists instead. For details, see Managing IP Addr", "product_code":"dcs", - "title":"Why Aren't Security Groups Configured for DCS Redis 4.0/5.0/6.0 Instances?", + "title":"Why Aren't Security Groups Configured for DCS Redis 4.0 and Later Instances?", "uri":"dcs-faq-0730014.html", "doc_type":"usermanual", - "p_code":"146", - "code":"149" + "p_code":"154", + "code":"157" }, { "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", @@ -1346,8 +1418,8 @@ "title":"Do DCS Redis Instances Limit the Size of a Key or Value?", "uri":"dcs-faq-0730015.html", "doc_type":"usermanual", - "p_code":"146", - "code":"150" + "p_code":"154", + "code":"158" }, { "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", @@ -1355,8 +1427,8 @@ "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":"146", - "code":"151" + "p_code":"154", + "code":"159" }, { "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.", @@ -1364,8 +1436,8 @@ "title":"Why Is Available Memory Smaller Than Instance Cache Size?", "uri":"dcs-faq-0730018.html", "doc_type":"usermanual", - "p_code":"146", - "code":"152" + "p_code":"154", + "code":"160" }, { "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", @@ -1373,8 +1445,8 @@ "title":"Does DCS for Redis Support Multiple Databases?", "uri":"dcs-faq-0730019.html", "doc_type":"usermanual", - "p_code":"146", - "code":"153" + "p_code":"154", + "code":"161" }, { "desc":"Yes. DCS for Redis 4.0 and later support Redis Clusters. DCS for Redis 3.0 supports Proxy Clusters.", @@ -1382,17 +1454,17 @@ "title":"Does DCS for Redis Support Redis Clusters?", "uri":"dcs-faq-0730020.html", "doc_type":"usermanual", - "p_code":"146", - "code":"154" + "p_code":"154", + "code":"162" }, { - "desc":"Cluster instances and master/standby DCS Redis 4.0 and later instances support Sentinels. Sentinels monitor the running status of both the master and standby nodes of a m", + "desc":"Master/Standby, read/write splitting, and cluster DCS Redis 4.0 and later instances support Sentinels (Each shard of a cluster is a master/standby instance.). Sentinels m", "product_code":"dcs", "title":"Does DCS for Redis Support Sentinel?", "uri":"dcs-faq-0730021.html", "doc_type":"usermanual", - "p_code":"146", - "code":"155" + "p_code":"154", + "code":"163" }, { "desc":"Data is evicted from cache based on a user-defined space limit in order to make space for new data. For details, see the Redis official website. You can view or change th", @@ -1400,8 +1472,8 @@ "title":"What Is the Default Data Eviction Policy?", "uri":"dcs-faq-0730022.html", "doc_type":"usermanual", - "p_code":"146", - "code":"156" + "p_code":"154", + "code":"164" }, { "desc":"Start the Redis exporter using the CLI. Based on the output, check for errors and troubleshoot accordingly.", @@ -1409,8 +1481,8 @@ "title":"What Should I Do If an Error Occurs in Redis Exporter?", "uri":"dcs-faq-0730023.html", "doc_type":"usermanual", - "p_code":"146", - "code":"157" + "p_code":"154", + "code":"165" }, { "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", @@ -1418,8 +1490,8 @@ "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":"146", - "code":"158" + "p_code":"154", + "code":"166" }, { "desc":"You cannot customize or change the port for accessing a DCS Redis 3.0 instance. You can customize (during instance creation) and change the port (on the instance details ", @@ -1427,8 +1499,8 @@ "title":"Can I Customize or Change the Port for Accessing a DCS Instance?", "uri":"dcs-faq-0730026.html", "doc_type":"usermanual", - "p_code":"146", - "code":"159" + "p_code":"154", + "code":"167" }, { "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 ", @@ -1436,17 +1508,17 @@ "title":"Can I Modify the Connection Addresses for Accessing a DCS Instance?", "uri":"dcs-faq-0730027.html", "doc_type":"usermanual", - "p_code":"146", - "code":"160" + "p_code":"154", + "code":"168" }, { - "desc":"Master/Standby and cluster DCS Redis instances can be deployed across availability zones (AZs).If instance nodes in an AZ are faulty, nodes in other AZs will not be affec", + "desc":"Master/Standby, read/write splitting, and cluster DCS Redis instances can be deployed across availability zones (AZs).If instance nodes in an AZ are faulty, nodes in othe", "product_code":"dcs", "title":"Does DCS Support Cross-AZ Deployment?", "uri":"dcs-faq-0730029.html", "doc_type":"usermanual", - "p_code":"146", - "code":"161" + "p_code":"154", + "code":"169" }, { "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 ", @@ -1454,8 +1526,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":"146", - "code":"162" + "p_code":"154", + "code":"170" }, { "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", @@ -1463,8 +1535,8 @@ "title":"Does DCS for Redis Provide Backend Management Software?", "uri":"dcs-faq-0730032.html", "doc_type":"usermanual", - "p_code":"146", - "code":"163" + "p_code":"154", + "code":"171" }, { "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", @@ -1472,8 +1544,8 @@ "title":"Can I Recover Data from Deleted DCS Instances?", "uri":"dcs-faq-0730034.html", "doc_type":"usermanual", - "p_code":"146", - "code":"164" + "p_code":"154", + "code":"172" }, { "desc":"Symptom: \"Error in execution; nested exception is io.lettuce.core.RedisCommandExecutionException: OOM command not allowed when used memory > 'maxmemory'\" is returned duri", @@ -1481,8 +1553,8 @@ "title":"Why Is \"Error in execution\" Returned When I Access Redis?", "uri":"dcs-faq-210223001.html", "doc_type":"usermanual", - "p_code":"146", - "code":"165" + "p_code":"154", + "code":"173" }, { "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", @@ -1490,8 +1562,8 @@ "title":"Why Does a Key Disappear in Redis?", "uri":"dcs-faq-210409001.html", "doc_type":"usermanual", - "p_code":"146", - "code":"166" + "p_code":"154", + "code":"174" }, { "desc":"Multi-key operations, such as those using the MSET command or Lua scripts, are atomic. All specified keys are executed at the same time. However, in a cluster, each key i", @@ -1499,17 +1571,17 @@ "title":"Explaining and Using Hash Tags", "uri":"dcs-faq-211228001.html", "doc_type":"usermanual", - "p_code":"146", - "code":"167" + "p_code":"154", + "code":"175" }, { - "desc":"After a single-node DCS instance is restarted, data in the instance is deleted.Master/Standby and cluster instances (except single-replica clusters) support AOF persisten", + "desc":"After a single-node DCS instance is restarted, data in the instance is deleted.Master/Standby, read/write splitting, and cluster instances (except single-replica clusters", "product_code":"dcs", "title":"Will Cached Data Be Retained After an Instance Is Restarted?", "uri":"dcs-faq-0220330.html", "doc_type":"usermanual", - "p_code":"146", - "code":"168" + "p_code":"154", + "code":"176" }, { "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.", @@ -1517,8 +1589,8 @@ "title":"Redis Commands", "uri":"dcs-faq-190921003.html", "doc_type":"usermanual", - "p_code":"127", - "code":"169" + "p_code":"135", + "code":"177" }, { "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", @@ -1526,8 +1598,8 @@ "title":"How Do I Clear Redis Data?", "uri":"dcs-faq-0730036.html", "doc_type":"usermanual", - "p_code":"169", - "code":"170" + "p_code":"177", + "code":"178" }, { "desc":"Yes. For more information about Redis command compatibility, see Command Compatibility.", @@ -1535,8 +1607,8 @@ "title":"Does DCS for Redis Support the INCR and EXPIRE Commands?", "uri":"dcs-faq-0730039.html", "doc_type":"usermanual", - "p_code":"169", - "code":"171" + "p_code":"177", + "code":"179" }, { "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 ", @@ -1544,8 +1616,8 @@ "title":"Why Do I Fail to Execute Some Redis Commands?", "uri":"dcs-faq-0730040.html", "doc_type":"usermanual", - "p_code":"169", - "code":"172" + "p_code":"177", + "code":"180" }, { "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", @@ -1553,17 +1625,17 @@ "title":"Why Does a Redis Command Fail to Take Effect?", "uri":"dcs-faq-0730041.html", "doc_type":"usermanual", - "p_code":"169", - "code":"173" + "p_code":"177", + "code":"181" }, { - "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", + "desc":"Redis timeouts happen on the client or server.Timeouts on the client are managed in the client code. Services can determine an appropriate timeout. For example, parameter", "product_code":"dcs", "title":"Is There a Time Limit on Executing Redis Commands? What Will Happen If a Command Times Out?", "uri":"dcs-faq-0427057.html", "doc_type":"usermanual", - "p_code":"169", - "code":"174" + "p_code":"177", + "code":"182" }, { "desc":"No. Like in open-source Redis, keys in DCS for Redis are case-sensitive and cannot be configured to be case-insensitive.", @@ -1571,8 +1643,8 @@ "title":"Can I Configure Redis Keys to Be Case-Insensitive?", "uri":"dcs-faq-0427058.html", "doc_type":"usermanual", - "p_code":"169", - "code":"175" + "p_code":"177", + "code":"183" }, { "desc":"No. Redis does not record commands and does not support viewing the most frequently used commands.", @@ -1580,8 +1652,8 @@ "title":"Can I View the Most Frequently Used Redis Commands?", "uri":"dcs-faq-0624001.html", "doc_type":"usermanual", - "p_code":"169", - "code":"176" + "p_code":"177", + "code":"184" }, { "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.", @@ -1589,8 +1661,8 @@ "title":"Instance Scaling and Upgrade", "uri":"dcs-faq-0326022.html", "doc_type":"usermanual", - "p_code":"127", - "code":"177" + "p_code":"135", + "code":"185" }, { "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,", @@ -1598,8 +1670,8 @@ "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":"177", - "code":"178" + "p_code":"185", + "code":"186" }, { "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", @@ -1607,8 +1679,8 @@ "title":"Are Services Interrupted If Maintenance is Performed During the Maintenance Time Window?", "uri":"dcs-faq-0730044.html", "doc_type":"usermanual", - "p_code":"177", - "code":"179" + "p_code":"185", + "code":"187" }, { "desc":"No. Specification modifications can take place while the instance is running and do not affect any other resources.", @@ -1616,17 +1688,17 @@ "title":"Are Instances Stopped or Restarted During Specification Modification?", "uri":"dcs-faq-0730045.html", "doc_type":"usermanual", - "p_code":"177", - "code":"180" + "p_code":"185", + "code":"188" }, { - "desc":"You are advised to change the instance specifications during off-peak hours because specification modification has the following impacts:Supported instance type changes:F", + "desc":"You are advised to change the instance specifications during off-peak hours because specification modification has the following impacts:The following table lists scaling", "product_code":"dcs", "title":"Are Services Interrupted During Specification Modification?", "uri":"dcs-faq-0730047.html", "doc_type":"usermanual", - "p_code":"177", - "code":"181" + "p_code":"185", + "code":"189" }, { "desc":"Check whether other tasks are running.Specifications of a DCS instance cannot be modified if another task of the instance is still running. For example, you cannot delete", @@ -1634,8 +1706,8 @@ "title":"Why Can't I Modify Specifications for a DCS Redis Instance?", "uri":"dcs-faq-0730048.html", "doc_type":"usermanual", - "p_code":"177", - "code":"182" + "p_code":"185", + "code":"190" }, { "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.", @@ -1643,8 +1715,8 @@ "title":"Monitoring and Alarm", "uri":"dcs-faq-0326023.html", "doc_type":"usermanual", - "p_code":"127", - "code":"183" + "p_code":"135", + "code":"191" }, { "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", @@ -1652,8 +1724,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":"183", - "code":"184" + "p_code":"191", + "code":"192" }, { "desc":"No. To ensure high-performance reads and writes, Redis does not audit commands. Commands are not printed.", @@ -1661,8 +1733,8 @@ "title":"Does Redis Support Command Audits?", "uri":"dcs-faq-0730049.html", "doc_type":"usermanual", - "p_code":"183", - "code":"185" + "p_code":"191", + "code":"193" }, { "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 ", @@ -1670,8 +1742,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":"183", - "code":"186" + "p_code":"191", + "code":"194" }, { "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 ", @@ -1679,8 +1751,8 @@ "title":"Why Is Used Memory Greater Than Available Memory?", "uri":"dcs-faq-0730052.html", "doc_type":"usermanual", - "p_code":"183", - "code":"187" + "p_code":"191", + "code":"195" }, { "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, ", @@ -1688,17 +1760,17 @@ "title":"Why Does Bandwidth Usage Exceed 100%?", "uri":"dcs-faq-0513001.html", "doc_type":"usermanual", - "p_code":"183", - "code":"188" + "p_code":"191", + "code":"196" }, { - "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.The Rejected ", "product_code":"dcs", "title":"Why Is the Rejected Connections Metric Displayed?", "uri":"dcs-faq-0603001.html", "doc_type":"usermanual", - "p_code":"183", - "code":"189" + "p_code":"191", + "code":"197" }, { "desc":"Flow control is triggered when the traffic used by a Redis instance in a period exceeds the maximum bandwidth.For details about the maximum bandwidth of an instance flavo", @@ -1706,8 +1778,8 @@ "title":"Why Is Flow Control Triggered? How Do I Handle It?", "uri":"dcs-faq-0220721.html", "doc_type":"usermanual", - "p_code":"183", - "code":"190" + "p_code":"191", + "code":"198" }, { "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.", @@ -1715,8 +1787,8 @@ "title":"Data Backup, Export, and Migration", "uri":"dcs-faq-0326024.html", "doc_type":"usermanual", - "p_code":"127", - "code":"191" + "p_code":"135", + "code":"199" }, { "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", @@ -1724,8 +1796,8 @@ "title":"How Do I Export DCS Redis Instance Data?", "uri":"dcs-faq-0730053.html", "doc_type":"usermanual", - "p_code":"191", - "code":"192" + "p_code":"199", + "code":"200" }, { "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", @@ -1733,17 +1805,17 @@ "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":"191", - "code":"193" + "p_code":"199", + "code":"201" }, { - "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:", + "desc":"Single-node: NoMaster/Standby, read/write splitting, and cluster (except single-replica clusters): YesDCS Redis instances supports only AOF persistence by default. You ca", "product_code":"dcs", - "title":"Does DCS Support Data Persistence? What Is the Impact of Persistence?", + "title":"Do DCS Redis Instances Support Data Persistence? What Is the Impact of Persistence?", "uri":"dcs-faq-0427081.html", "doc_type":"usermanual", - "p_code":"191", - "code":"194" + "p_code":"199", + "code":"202" }, { "desc":"AOF rewrites involve the following concepts:Rewrite window, which is currently 01:00 to 04:59Disk usage threshold, which is 50%Dataset memory, which is the percentage of ", @@ -1751,8 +1823,8 @@ "title":"When Will AOF Rewrites Be Triggered?", "uri":"dcs-faq-210706001.html", "doc_type":"usermanual", - "p_code":"191", - "code":"195" + "p_code":"199", + "code":"203" }, { "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.", @@ -1760,26 +1832,17 @@ "title":"Can I Migrate Data to Multiple Target Instances in One Migration Task?", "uri":"dcs-faq-220317.html", "doc_type":"usermanual", - "p_code":"191", - "code":"196" + "p_code":"199", + "code":"204" }, { - "desc":"Migration within DCS:By default, the SYNC and PSYNC commands can be used when self-hosted Redis is migrated to DCS.During online migration between DCS Redis instances in ", + "desc":"Migration within DCS:If the online migration task uses the same account and region as the source instance, select a DCS instance (cloud Redis) as the source. The SYNC and", "product_code":"dcs", "title":"How Do I Enable the SYNC and PSYNC Commands?", "uri":"dcs-faq-210721001.html", "doc_type":"usermanual", - "p_code":"191", - "code":"197" - }, - { - "desc":"Possible causes:The underlying resources are insufficient.The specifications of the ECS used for the migration are insufficient.The memory of the target Redis created bef", - "product_code":"dcs", - "title":"Why Does Migration Task Creation Fail?", - "uri":"dcs-faq-210721002.html", - "doc_type":"usermanual", - "p_code":"191", - "code":"198" + "p_code":"199", + "code":"205" }, { "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", @@ -1787,8 +1850,8 @@ "title":"Will the Same Keys Be Overwritten During Data Migration or Backup Import?", "uri":"dcs-faq-11185.html", "doc_type":"usermanual", - "p_code":"191", - "code":"199" + "p_code":"199", + "code":"206" }, { "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", @@ -1796,8 +1859,8 @@ "title":"Online Migration with Rump", "uri":"dcs-migration-090626001.html", "doc_type":"usermanual", - "p_code":"191", - "code":"200" + "p_code":"199", + "code":"207" }, { "desc":"Convert the format of a data file before importing the file.Run the following command to convert the format of a file in the Windows OS to that in the Unix-like OS:dos2un", @@ -1805,17 +1868,17 @@ "title":"What Should I Consider When Transferring or Operating Data Between Different OSs?", "uri":"dcs-migration-0312016.html", "doc_type":"usermanual", - "p_code":"191", - "code":"201" + "p_code":"199", + "code":"208" }, { - "desc":"A total of 256 DBs (DB 0 to DB 255) can be configured for a single-node or master/standby DCS instance.If the target is a cluster instance (a cluster instance has only on", + "desc":"A total of 256 DBs (DB 0 to DB 255) can be configured for a single-node, read/write splitting, or master/standby DCS instance.If the target is a cluster instance (a clust", "product_code":"dcs", "title":"Can I Migrate Data from a Multi-DB Source Redis Instance to a Cluster DCS Redis Instance?", "uri":"dcs-migration-0312017.html", "doc_type":"usermanual", - "p_code":"191", - "code":"202" + "p_code":"199", + "code":"209" }, { "desc":"The online migration function provided on the console does not support migration of specified DBs. If you want to migrate specified Redis DBs, use redis-shake to export o", @@ -1823,8 +1886,8 @@ "title":"How Can I Migrate Partial Data?", "uri":"dcs-migration-0312018.html", "doc_type":"usermanual", - "p_code":"191", - "code":"203" + "p_code":"199", + "code":"210" }, { "desc":"Proxy Cluster instancesProxy Cluster instances are used in the same way that you use single-node or master/standby instances. However, only one DB is configured for a Pro", @@ -1832,8 +1895,8 @@ "title":"What Are the Constraints and Precautions for Migrating Redis Data to a Cluster Instance?", "uri":"dcs-migration-0312019.html", "doc_type":"usermanual", - "p_code":"191", - "code":"204" + "p_code":"199", + "code":"211" }, { "desc":"NetworkBefore online migration, ensure that the network configured for the migration task is connected to source and target Redis instances.Before online migration, ensur", @@ -1841,8 +1904,8 @@ "title":"What Should I Consider for Online Migration?", "uri":"dcs-migration-0312020.html", "doc_type":"usermanual", - "p_code":"191", - "code":"205" + "p_code":"199", + "code":"212" }, { "desc":"Yes. You can use the application dual-write mode. In this mode, during data migration, data is still read from the source Redis instance, and operations such as adding, d", @@ -1850,8 +1913,8 @@ "title":"Can I Perform Online Migration Without Any Service Interruption?", "uri":"dcs-migration-0312021.html", "doc_type":"usermanual", - "p_code":"191", - "code":"206" + "p_code":"199", + "code":"213" }, { "desc":"The following error messages may be displayed during online migration:\"Disconnecting timedout slave\" is reported on the source instance, as shown in the following figure:", @@ -1859,8 +1922,8 @@ "title":"What If \"Disconnecting timedout slave\" and \"overcoming of output buffer limits\" Are Reported on the Source Instance During Online Migration?", "uri":"dcs-migration-211125001.html", "doc_type":"usermanual", - "p_code":"191", - "code":"207" + "p_code":"199", + "code":"214" }, { "desc":"For details on how to use Rump, see the Data Migration Guide.Possible causes:Rump does not support migration to cluster DCS instances.Commands are incorrectly run in Rump", @@ -1868,8 +1931,8 @@ "title":"Why Is Memory of a DCS Redis Instance Unchanged After Data Migration Using Rump, Even If No Error Message Is Returned?", "uri":"dcs-faq-0427076.html", "doc_type":"usermanual", - "p_code":"191", - "code":"208" + "p_code":"199", + "code":"215" }, { "desc":"Yes. Redis is backward compatible.The version of the source Redis (DCS, self-built, or another cloud) can be earlier than or the same as the target DCS instance.", @@ -1877,8 +1940,8 @@ "title":"Can I Migrate Data from a Lower Redis Version to a Higher One?", "uri":"dcs-migration-0715005.html", "doc_type":"usermanual", - "p_code":"191", - "code":"209" + "p_code":"199", + "code":"216" }, { "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.", @@ -1886,8 +1949,8 @@ "title":"Big/Hot Key Analysis and Expired Key Scan", "uri":"dcs-faq-0805001.html", "doc_type":"usermanual", - "p_code":"127", - "code":"210" + "p_code":"135", + "code":"217" }, { "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.", @@ -1895,8 +1958,8 @@ "title":"What Are Big Keys and Hot Keys?", "uri":"dcs-faq-0521003.html", "doc_type":"usermanual", - "p_code":"210", - "code":"211" + "p_code":"217", + "code":"218" }, { "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.", @@ -1904,8 +1967,8 @@ "title":"What Is the Impact of Big Keys or Hot Keys?", "uri":"dcs-faq-0521004.html", "doc_type":"usermanual", - "p_code":"210", - "code":"212" + "p_code":"217", + "code":"219" }, { "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 ", @@ -1913,8 +1976,8 @@ "title":"How Do I Avoid Big Keys and Hot Keys?", "uri":"dcs-faq-0521005.html", "doc_type":"usermanual", - "p_code":"210", - "code":"213" + "p_code":"217", + "code":"220" }, { "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", @@ -1922,8 +1985,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":"210", - "code":"214" + "p_code":"217", + "code":"221" }, { "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", @@ -1931,8 +1994,8 @@ "title":"How Do I Detect Big Keys and Hot Keys in Advance?", "uri":"dcs-faq-0606002.html", "doc_type":"usermanual", - "p_code":"210", - "code":"215" + "p_code":"217", + "code":"222" }, { "desc":"What are the rules for scheduled deletion of expired keys on a daily basis? Can I customize the rules?Lazy free deletion: The deletion strategy is controlled in the main ", @@ -1940,8 +2003,8 @@ "title":"How Does DCS Delete Expired Keys?", "uri":"dcs-faq-210531002.html", "doc_type":"usermanual", - "p_code":"210", - "code":"216" + "p_code":"217", + "code":"223" }, { "desc":"Key storage durationKeys that do not have an expiration are stored permanently.Keys that have an expiration are deleted after they expire. For details, see Scanning Expir", @@ -1949,8 +2012,8 @@ "title":"How Long Are Keys Stored? How Do I Set Key Expiration?", "uri":"dcs-faq-210812001.html", "doc_type":"usermanual", - "p_code":"210", - "code":"217" + "p_code":"217", + "code":"224" }, { "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.", @@ -1958,8 +2021,8 @@ "title":"Master/Standby Switchover", "uri":"dcs-faq-191204001.html", "doc_type":"usermanual", - "p_code":"127", - "code":"218" + "p_code":"135", + "code":"225" }, { "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", @@ -1967,8 +2030,8 @@ "title":"When Does a Master/Standby Switchover Occur?", "uri":"dcs-faq-0730058.html", "doc_type":"usermanual", - "p_code":"218", - "code":"219" + "p_code":"225", + "code":"226" }, { "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", @@ -1976,8 +2039,8 @@ "title":"How Does Master/Standby Switchover Affect Services?", "uri":"dcs-faq-0730059.html", "doc_type":"usermanual", - "p_code":"218", - "code":"220" + "p_code":"225", + "code":"227" }, { "desc":"No. If the master fails, the standby node will be promoted to master and takes the original IP address.", @@ -1985,8 +2048,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":"218", - "code":"221" + "p_code":"225", + "code":"228" }, { "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 ", @@ -1994,8 +2057,8 @@ "title":"How Does Redis Master/Standby Replication Work?", "uri":"dcs-faq-0730061.html", "doc_type":"usermanual", - "p_code":"218", - "code":"222" + "p_code":"225", + "code":"229" }, { "desc":"For details about the terms involved in this document, see Glossary.", @@ -2004,7 +2067,7 @@ "uri":"en-us_topic_0072429345.html", "doc_type":"usermanual", "p_code":"", - "code":"223" + "code":"230" }, { "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.", @@ -2013,6 +2076,6 @@ "uri":"dcs-ug-0326026.html", "doc_type":"usermanual", "p_code":"", - "code":"224" + "code":"231" } ] \ No newline at end of file diff --git a/docs/dcs/umn/CacheCluster.html b/docs/dcs/umn/CacheCluster.html index baa9dfd44..0f4a60db9 100644 --- a/docs/dcs/umn/CacheCluster.html +++ b/docs/dcs/umn/CacheCluster.html @@ -5,63 +5,173 @@
  • The client is decoupled from the cloud service.
  • They support millions of concurrent requests, equivalent to Redis Cluster instances.
  • A wide range of memory specifications adapt to different scenarios.
  • 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.

+

Proxy Cluster DCS Redis 4.0/5.0 Instances

Proxy Cluster DCS Redis 4.0/5.0 instances are built based on open-source Redis 4.0/5.0 and compatible with open source codis. They provide multiple large-capacity specifications ranging from 4 GB to 1024 GB and .

+

Table 1 lists the number of shards corresponding to different specifications. You can customize the shard size when creating an instance. Currently, the number of shards and replicas cannot be customized. By default, each shard has two replicas.

+

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

-
- diff --git a/docs/dcs/umn/dcs-faq-0603001.html b/docs/dcs/umn/dcs-faq-0603001.html index 30e6f1a1a..17407c219 100644 --- a/docs/dcs/umn/dcs-faq-0603001.html +++ b/docs/dcs/umn/dcs-faq-0603001.html @@ -1,8 +1,10 @@

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. (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 Rejected Connections metric is displayed, check if the number of connected clients exceeds the maximum allowed number of connections of the instances.

+

The Rejected Connections metric of data nodes can be checked only for master/standby, cluster, and read/write splitting DCS Redis 4.0/5.0/6.0 instances.

+
+
  • To check the maximum number of connections, go to the Parameters tab page of the instance and check the maxclients metric. (Currently, read/write splitting instances do not have this parameter. To query the maximum connections of them, see .)
  • 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-0730001.html b/docs/dcs/umn/dcs-faq-0730001.html index fbff2937e..1f100e15b 100644 --- a/docs/dcs/umn/dcs-faq-0730001.html +++ b/docs/dcs/umn/dcs-faq-0730001.html @@ -1,7 +1,7 @@

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.

+

No. DCS instances cannot be accessed 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.

diff --git a/docs/dcs/umn/dcs-faq-0730009.html b/docs/dcs/umn/dcs-faq-0730009.html index 090149585..a5caebbf1 100644 --- a/docs/dcs/umn/dcs-faq-0730009.html +++ b/docs/dcs/umn/dcs-faq-0730009.html @@ -6,13 +6,13 @@

For security purposes, DCS does not support the CONFIG command initiated by a client. You need to perform the following steps:

  1. On the DCS console, set the value of the notify-keyspace-event parameter to Egx for a DCS Redis instance.
  2. Add the following content to the XML configuration file of the Spring framework:

    <util:constant

    static-field="org.springframework.session.data.redis.config.ConfigureRedisAction.NO_OP"/>

    -
  3. Modify the related Spring code. Enable the ConfigureRedisAction.NO_OP bean component to forbid a client to invoke the CONFIG command.

    @Bean

    -

    public static ConfigureRedisAction configureRedisAction() {

    -

    return ConfigureRedisAction.NO_OP;

    -

    }

    +
  4. Modify the related Spring code. Enable the ConfigureRedisAction.NO_OP bean component to forbid a client to invoke the CONFIG command.
    @Bean
+public static ConfigureRedisAction configureRedisAction() {
+    return ConfigureRedisAction.NO_OP;
+}

For more information, see the Spring Session Documentation.

-

Session sharing is supported only by single-node and master/standby DCS Redis instances, but not by cluster DCS Redis instances.

+

Session sharing is supported by single-node, read/write splitting, and master/standby DCS Redis instances, but not by cluster DCS Redis instances.

diff --git a/docs/dcs/umn/dcs-faq-0730010.html b/docs/dcs/umn/dcs-faq-0730010.html index 3c9b1b61d..e6ebea2be 100644 --- a/docs/dcs/umn/dcs-faq-0730010.html +++ b/docs/dcs/umn/dcs-faq-0730010.html @@ -8,7 +8,7 @@
  • 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.

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

    -
  • 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 a DCS Redis 4.0 or later 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.

  • 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 e6a704ab0..8816950c0 100644 --- a/docs/dcs/umn/dcs-faq-0730014.html +++ b/docs/dcs/umn/dcs-faq-0730014.html @@ -1,7 +1,7 @@ -

    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.

    +

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

    +

    Currently, DCS Redis 4.0 and later 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-0730021.html b/docs/dcs/umn/dcs-faq-0730021.html index 080f5f82a..55c0ade5f 100644 --- a/docs/dcs/umn/dcs-faq-0730021.html +++ b/docs/dcs/umn/dcs-faq-0730021.html @@ -1,8 +1,8 @@

    Does DCS for Redis Support Sentinel?

    -

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

    -

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

    +

    Master/Standby, read/write splitting, and cluster DCS Redis 4.0 and later instances support Sentinels (Each shard of a cluster is a master/standby instance.). Sentinels monitor the running status of both the master and standby nodes of a master/standby instance and each shard of a cluster instance. If the master node becomes faulty, a failover will be performed.

    +

    DCS Redis 3.0 does not support Sentinels.

    diff --git a/docs/dcs/umn/dcs-faq-0730026.html b/docs/dcs/umn/dcs-faq-0730026.html index 4f45d5b87..3d461f6a3 100644 --- a/docs/dcs/umn/dcs-faq-0730026.html +++ b/docs/dcs/umn/dcs-faq-0730026.html @@ -6,6 +6,13 @@
  • 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.

    +

    Customizing a Port

    When creating a DCS Redis 4.0, 5.0, or 6.0 instance, you can enter a port number for IP Address. If you do not specify a port, the default port 6379 is used.

    +
    +

    Changing the Port

    After a DCS Redis 4.0 or later instance is created, you can change its port.

    +
    1. In the navigation pane of the DCS console, choose Cache Manager.
    2. Click a DCS Redis instance.
    3. In the Connection area, click next to Connection Address.

      After the port is changed, all connections to the Redis instance are interrupted, and services are connected to the new port.

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

    Does DCS Support Cross-AZ Deployment?

    -

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

    +

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

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

    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.

    -

    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.

    +

    You can restore backup data to an instance other than a single-node one 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-0730047.html b/docs/dcs/umn/dcs-faq-0730047.html index 4a65b2639..1e375532e 100644 --- a/docs/dcs/umn/dcs-faq-0730047.html +++ b/docs/dcs/umn/dcs-faq-0730047.html @@ -2,68 +2,58 @@

    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:

    -

    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 Total memory, proxies, and shards of Proxy Cluster DCS Redis 3.0 instances

    Total Memory

    +
    - - + - - - + - - - + - - - + - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Specifications of Proxy Cluster DCS Redis 4.0/5.0 instances

    Total Memory

    Proxies

    +

    Proxies

    Shards

    +

    Shards

    +

    Memory per Shard (GB)

    64 GB

    +

    4 GB

    3

    +

    3

    8

    +

    3

    +

    1.33

    128 GB

    +

    8 GB

    6

    +

    3

    16

    +

    3

    +

    2.67

    256 GB

    +

    16 GB

    8

    +

    3

    32

    +

    3

    +

    5.33

    512 GB

    +

    24 GB

    16

    +

    3

    64

    +

    3

    +

    8

    +

    32 GB

    +

    3

    +

    3

    +

    10.67

    +

    48 GB

    +

    6

    +

    6

    +

    8

    +

    64 GB

    +

    8

    +

    8

    +

    8

    +

    96 GB

    +

    12

    +

    12

    +

    8

    +

    128 GB

    +

    16

    +

    16

    +

    8

    +

    192 GB

    +

    24

    +

    24

    +

    8

    +

    256 GB

    +

    32

    +

    32

    +

    8

    +

    384 GB

    +

    48

    +

    48

    +

    8

    +

    512 GB

    +

    64

    +

    64

    +

    8

    +

    768 GB

    +

    96

    +

    96

    +

    8

    +

    1024 GB

    +

    128

    +

    128

    +

    8
    -
    Figure 1 Proxy Cluster 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.

      -

      For details, see Security Group Configurations.

      +
      Figure 1 Architecture of a Proxy Cluster DCS Redis 4.0/5.0 instance
      +

      Architecture description:

      +
      • VPC

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

        +

        The client and the cluster instance must be in the same VPC, and the instance whitelist must allow access from the client IP address.

        -
      • Application

        The client used to access the instance.

        -

        DCS Redis instances can be accessed through open-source clients. For details about accessing DCS instances, see Accessing an Instance.

        -
      • LB-M/LB-S

        The load balancers, which are deployed in master/standby HA mode. The connection addresses (IP address:Port) of the cluster DCS Redis instance are the addresses of the load balancers.

        -
      • Proxy

        The proxy server used to achieve high availability and process high-concurrency client requests.

        -

        You can connect to a Proxy Cluster instance at the IP addresses of its proxies.

        -
      • Redis shard

        A shard of the cluster.

        -

        Each shard consists of a pair of master/standby nodes. If the master node becomes faulty, the standby node automatically takes over cluster services.

        -

        If both the master and standby nodes of a shard are faulty, the cluster can still provide services but the data on the faulty shard is inaccessible.

        -
      • Cluster manager

        The cluster configuration managers, which store configurations and partitioning policies of the cluster. You cannot modify the information about the configuration managers.

        +
      • Application

        The client used to access the instance.

        +

        DCS Redis instances can be accessed through open-source clients. For details about accessing DCS instances in different languages, see Accessing an Instance.

        +
      • VPC endpoint service

        You can configure your DCS Redis instance as a VPC endpoint service and access the instance at the VPC endpoint service address.

        +

        The IP address of the Proxy Cluster DCS Redis instance is the address of the VPC endpoint service.

        +
      • ELB

        The load balancers, which are deployed in cluster HA mode.

        +
      • Proxy

        The proxy server used to achieve high availability and process high-concurrency client requests.

        +

        You cannot connect to a Proxy Cluster instance at the IP addresses of its proxies.

        +
      • Redis cluster

        A shard of the cluster.

        +

        By default, each shard is a master/standby dual-replica Redis instance. When the master instance is faulty, the standby node will be switched to the master one after 15 to 30 seconds. Access to the shard will fail until the switchover is complete.

        +

        If both the master and standby nodes of a shard are faulty, the cluster can still provide services but the data on the faulty shard is inaccessible.

      diff --git a/docs/dcs/umn/CacheMasterSlave.html b/docs/dcs/umn/CacheMasterSlave.html index 945ed7e4b..25b9df336 100644 --- a/docs/dcs/umn/CacheMasterSlave.html +++ b/docs/dcs/umn/CacheMasterSlave.html @@ -7,37 +7,25 @@

      Features

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

      Master/Standby DCS instances have the following features:

      1. Data persistence and high reliability

        By default, data persistence is enabled by both the master and the standby node of a master/standby instance.

        -

        The standby node of a DCS Redis 3.0 instance is invisible to you. Only the master node provides data read/write operations.

        -

        The standby node of a Redis 4.0/5.0/6.0 instance is visible to you. You can read data from the standby node by connecting to it using the instance read-only address.

        +

        The standby node of a Redis 4.0 or later instance is visible to you. You can read data from the standby node by connecting to it using the instance read-only address.

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

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

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

        +
        • Disconnections and unavailability occur during the failover. The service client should be able to reconnect or retry.
        • After a master/standby switchover is complete, the last master node (already switched to the replica) is not recovered immediately and services will fail to access it. In this case, configure a Redis SDK by referring to Access in Different Languages.
        +
        +
      5. DR policies

        Each master/standby, read/write splitting, or cluster 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.

        +
      6. Read/Write splitting

        Master/Standby DCS Redis 4.0 and later instances support client read/write splitting. When connecting to such an instance, you can use the read/write address to connect to the master node or use the read-only address to connect to the standby node.

        +

        To implement read/write splitting for a master/standby instance, configure it on a client. To use the read/write splitting function, you are advised to use read/write splitting instances.

      -

      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.

        -

        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 Redis client of the instance, which is the application running on the ECS.

        -

        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 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 of Master/Standby DCS Redis 4.0/5.0/6.0/7.0 Instances

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

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

      Architecture description:

      -
      1. Each master/standby DCS Redis 4.0/5.0/6.0 instance has two connection addresses. When connecting to such an instance, you can use the read/write domain name address to connect to the master node or use the read-only domain name address to connect to the standby node.

        The connection addresses can be obtained on the instance details page on the DCS console.

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

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

      To implement read/write splitting using a master/standby instance, ensure that your client can distinguish between read and write requests. The client directs write requests to the read/write domain name and read requests to the read-only domain name.

      -

      Requests to the read-only domain name address may fail if the standby node of a master/standby DCS Redis 4.0/5.0/6.0 instance is faulty. For higher reliability and lower latency, do not use the read-only address.

      +
      1. Each master/standby DCS Redis 4.0 or later instance has two connection addresses. When connecting to such an instance, you can use the read/write domain name address to connect to the master node or use the read-only domain name address to connect to the standby node.

        The connection addresses can be obtained on the instance details page on the DCS console.

        +
      2. Master/Standby DCS Redis 4.0 and later 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.

        +
      3. 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.
      4. To access a DCS Redis 4.0 or later 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.
      +
      • To implement read/write splitting using a master/standby instance, ensure that your client can distinguish between read and write requests. The client directs write requests to the read/write domain name and read requests to the read-only domain name.
      • Requests to the read-only domain name address may fail if the standby node of a master/standby DCS Redis 4.0 or later instance is faulty. For higher reliability and lower latency, do not use the read-only address.
      diff --git a/docs/dcs/umn/CacheProxy.html b/docs/dcs/umn/CacheProxy.html index 930af2d7d..3d94be3b5 100644 --- a/docs/dcs/umn/CacheProxy.html +++ b/docs/dcs/umn/CacheProxy.html @@ -75,6 +75,8 @@
      Figure 1 Distributed architecture of Redis Cluster
    • Presharding

      There are 16,384 hash slots in each Redis Cluster. The mapping between hash slots and Redis nodes is stored in Redis Servers. To compute what is the hash slot of a given key, simply take the CRC16 of the key modulo 16384. Example command output

      Figure 2 Redis Cluster presharding
      +
      • Each shard of a Redis Cluster is a master/standby Redis instance. When the master node on a shard is faulty, the connections on the shard are interrupted in seconds, and the shard becomes unavailable. The standby node is automatically switched over within 15 to 30 seconds. The fault only affects the shard itself.
      • When a master node on a single shard in a redis cluster is faulty, after a master/standby switchover is complete, the master node (already switched to the replica) is not recovered immediately and services will fail to access it. In this case, configure a Redis SDK by referring to Access in Different Languages.
      +
    diff --git a/docs/dcs/umn/CacheSingleNode.html b/docs/dcs/umn/CacheSingleNode.html index 287da6345..0931cd1fa 100644 --- a/docs/dcs/umn/CacheSingleNode.html +++ b/docs/dcs/umn/CacheSingleNode.html @@ -9,16 +9,15 @@
  • 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.

  • Low-cost and suitable for development and testing

    Single-node instances are 40% cheaper than master/standby DCS instances, suitable for setting up development or testing environments.

    • -

    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.

    +

    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 or stopped. 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/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.

    +

    To access a DCS Redis 3.0 instance, you must use port 6379. To access a DCS Redis 4.0 or later 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.

      -

      For details, see Security Group Configurations.

      +

      For intra-VPC access, the client and the instance must be in the same VPC. For a Redis 3.0 instance, security group rules are required.

    • Application

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

      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.

      diff --git a/docs/dcs/umn/GlobalDRPolicy.html b/docs/dcs/umn/GlobalDRPolicy.html index f3e9f8372..da335e7ec 100644 --- a/docs/dcs/umn/GlobalDRPolicy.html +++ b/docs/dcs/umn/GlobalDRPolicy.html @@ -7,17 +7,17 @@

      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.

      +

      By default, instances except for single-node ones support data persistence. Data is persisted to disk in the master node and incrementally synchronized and persisted to the standby node, achieving hot standby and persistent data backups.

      +

      For master/standby or read/write splitting instances, and each shard of cluster instances, the master node process synchronizes and persists data to the standby node processes, as shown in the following figure.

      Figure 3 HA for a master/standby DCS instance deployed within an AZ
      -

      Cluster DCS instance: Similar to a master/standby instance, data in each shard (instance process) of a cluster instance is synchronized between master and standby nodes and persisted on both nodes.

      -
      Figure 4 HA for a cluster DCS instance deployed within an AZ
      -

      Cross-AZ DR

      The master and standby nodes of a master/standby or cluster DCS instance can be deployed across AZs (in different equipment rooms). Power supplies and networks of different AZs are physically isolated. When a fault occurs in the AZ where the master node is deployed, the standby node connects to the client and takes over data read and write operations.

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

      -
      Figure 6 Selecting different AZs
      +

      Cross-AZ DR

      The master and standby nodes of a master/standby, read/write splitting, or cluster DCS instance can be deployed across AZs (in different equipment rooms). Power supplies and networks of different AZs are physically isolated. When a fault occurs in the AZ where the master node is deployed, the standby node connects to the client and takes over data read and write operations.

      +
      Figure 4 Cross-AZ deployment of a master/standby DCS instance
      +
      Figure 5 Cross-AZ deployment of a read/write splitting DCS instance
      +
      Figure 6 Cross-AZ deployment of a Proxy Cluster DCS instance
      +
      Figure 7 Cross-AZ deployment of a Redis Cluster DCS instance
      +

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

      +
      Figure 8 Selecting different AZs
      • You can deploy your application across AZs to ensure both data reliability and service availability in the event of power supply or network disruptions.
      • Cross-AZ instances do not support password changes, command renaming, and specification modification when an AZ is faulty.
      diff --git a/docs/dcs/umn/PurchasePreparation.html b/docs/dcs/umn/PurchasePreparation.html index d8109614e..2dd8a7d5a 100644 --- a/docs/dcs/umn/PurchasePreparation.html +++ b/docs/dcs/umn/PurchasePreparation.html @@ -3,13 +3,13 @@

      Identifying Requirements

      Before creating a DCS instance, identify your requirements and complete the following preparations:

      1. Decide on the required cache engine version.

        Different Redis versions have different features. For details, see Comparing Redis Versions.

        -
      2. Decide on the required instance type.

        DCS provides single-node, master/standby, Proxy Cluster, and Redis Cluster types of instances. Each type has its own architecture. For details about the instance architectures, see DCS Instance Types.

        +
      3. Decide on the required instance type.

        DCS provides single-node, master/standby, read/write splitting, Proxy Cluster, and Redis Cluster types of instances. Each type has its own architecture. For details about the instance architectures, see DCS Instance Types.

      4. Decide on the required instance specification.

        Each specification specifies the maximum available memory, number of connections, and bandwidth. For details, see DCS Instance Specifications.

      5. Decide on the region and whether cross-AZ deployment is required.

        Choose a region closest to your application to reduce latency.

        -

        A region consists of multiple availability zones (AZs) with physically isolated power supplies and networks. Master/standby and cluster DCS instances can be deployed across AZs.

        -
        • If a master/standby or cluster DCS instance is deployed across AZs, faults in an AZ do not affect cache nodes in other AZs. This is because when the master node is faulty, the standby cache node will automatically become the master node to provide services. Such deployment achieves better disaster recovery.
        • Deploying a DCS instance across AZs slightly reduces network efficiency compared with deploying an instance within an AZ. Therefore, if a DCS instance is deployed across AZs, synchronization between master and standby cache nodes is slightly less efficient.
        +

        A region consists of multiple availability zones (AZs) with physically isolated power supplies and networks. Master/Standby, read/write splitting, and cluster DCS instances can be deployed across AZs.

        +
        • If a master/standby, read/write splitting, or cluster DCS instance is deployed across AZs, faults in an AZ do not affect cache nodes in other AZs. This is because when the master node is faulty, the standby cache node will automatically become the master node to provide services. Such deployment achieves better disaster recovery.
        • Deploying a DCS instance across AZs slightly reduces network efficiency compared with deploying an instance within an AZ. Therefore, if a DCS instance is deployed across AZs, synchronization between master and standby cache nodes is slightly less efficient.
        -
      6. Decide whether backup policies are required.

        Currently, backup policies can be configured only for master/standby and cluster DCS instances. For details about backup and restoration, see Overview.

        +
      7. Decide whether backup policies are required.

        Currently, backup restoration policies can be configured for instances other than single-node ones. For details about backup and restoration, see Overview.

      diff --git a/docs/dcs/umn/RedisDifference.html b/docs/dcs/umn/RedisDifference.html index 0c46ef745..257c1f491 100644 --- a/docs/dcs/umn/RedisDifference.html +++ b/docs/dcs/umn/RedisDifference.html @@ -2,15 +2,15 @@

      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/5.0/6.0. The following table describes the differences between these versions.

        +
        • Version

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

          - - @@ -20,7 +20,7 @@ - - - - - @@ -91,7 +91,7 @@

          The underlying architectures vary by Redis version. Once a Redis version is chosen, it cannot be changed. For example, you cannot upgrade a DCS Redis 3.0 instance to Redis 4.0 or 5.0. If you require a higher Redis version, create a new instance that meets your requirements and then migrate data from the old instance to the new one.

          -
        • Instance type

          Select from single-node, master/standby, and cluster types. For details about their architectures and application scenarios, see DCS Instance Types.

          +
        • Instance type

          Select from single-node, master/standby, read/write splitting, and cluster types. For details about their architectures and application scenarios, see DCS Instance Types.

          • diff --git a/docs/dcs/umn/TagManagement.html b/docs/dcs/umn/TagManagement.html index 8d6a888ac..4dbaffe43 100644 --- a/docs/dcs/umn/TagManagement.html +++ b/docs/dcs/umn/TagManagement.html @@ -24,9 +24,8 @@
          Table 1 Differences between Redis versions

          Feature

          Redis 3.0

          Redis 4.0 & Redis 5.0

          +

          Redis 4.0 and Redis 5.0

          Redis 6.0

          +

          Redis 6.0/7.0

          Redis 4.0.14 and 5.0.14, respectively

          6.2.7

          +

          Redis 6.2.7 and 7.2, respectively

          Instance deployment mode

          @@ -63,9 +63,9 @@

          Single-node, master/standby, and Proxy Cluster

          Single-node, master/standby and Redis Cluster

          +

          Single-node, master/standby, Proxy Cluster, read/write splitting, and Redis Cluster

          Single-node, master/standby, Redis Cluster

          +

          Single-node, master/standby, and Redis Cluster

          Scale-up or scale-down

          @@ -81,9 +81,9 @@

          Supported for master/standby and cluster instances

          Supported for master/standby and cluster instances

          +

          Supported for master/standby, read/write splitting, and cluster instances

          Supported for master/standby instances

          +

          Supported for master/standby and cluster instances
          -

          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. Click the name of an instance.
          2. Choose Instance Configuration > Tags.

            View the tags of the instance.

            -

          3. Perform the following operations as required:

            • Add a tag
              1. Click Add/Edit Tag.

                If you have created predefined tags, select a predefined pair of tag key and value. To view predefined tags or create tags, click View predefined tags. You will be directed to the TMS console.

                -

                You can also create new tags by entering Tag key and Tag value.

                +

                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. Click the name of an instance.
                2. Choose Instance Configuration > Tags.

                  View the tags of the instance.

                  +

                3. Perform the following operations as required:

                  • Add a tag
                    1. Click Add/Edit Tag. You can create new tags by entering Tag key and Tag value.

                      If you have created predefined tags, select a predefined pair of tag key and value. To view predefined tags or create tags, click View predefined tags. You will be directed to the TMS console.

                    2. Click OK.
                  • Modify a tag

                    Click Add/Edit Tag. In the displayed Add/Edit Tag dialog box, delete the desired key, add the key again, enter a new tag value, and click Add.

                  • Delete a tag

                    In the row containing the tag to be deleted, click Delete in the Operation column. Then click Yes.

                    diff --git a/docs/dcs/umn/dcs-faq-022025.html b/docs/dcs/umn/dcs-faq-022025.html index 186df6f0b..c821aea66 100644 --- a/docs/dcs/umn/dcs-faq-022025.html +++ b/docs/dcs/umn/dcs-faq-022025.html @@ -1,13 +1,13 @@

                    Should I Use a Domain Name or an IP Address to Connect to a DCS Redis Instance?

                    -
                    • Single-node, and Proxy Cluster:

                      Each instance has only one IP address and one domain name address. The addresses remain unchanged before and after master/standby switchover. You can use either address to connect to the instance.

                      +
                      • Single-node, read/write splitting, and Proxy Cluster:

                        Each instance has only one IP address and one domain name address. The addresses remain unchanged before and after master/standby switchover. You can use either address to connect to the instance.

                      • Master/Standby:

                        Each instance has one IP address and two domain name addresses. One of the domain name addresses is used only for processing read requests. The addresses remain unchanged after master/standby switchover. You can use any address to connect to the instance.

                        -

                        When you use a domain name address, distinguish between read and write requests. If you use Connection Address or IP Address, functions are not affected. If you use Read-only Address, only read requests are processed.

                        +

                        When you use a domain name address, distinguish between read and write requests. If you use Connection Address or IP Address, functions are not affected. If you use Read-only Address, only read requests are processed. You are advised to use read/write splitting instances if you have read/write splitting requirements.

                      • Redis Cluster:

                        A Redis Cluster instance has multiple pairs of master and replica IP addresses and one domain name address. You can use any address to connect to the instance.

                        The connected node sends requests to the correct node. All nodes in the cluster can receive requests. Configure multiple or all IP addresses to prevent single points of failure.

                      -
                      • Domain names cannot be resolved across regions. If the client and the DCS Redis instance are not in the same region, the instance cannot be accessed using its domain name address. You can manually map the domain name to the IP address in the hosts file or access the instance using its IP address.
                      • For details about how to connect to an instance, see Accessing an Instance.
                      +
                      • Domain names cannot be resolved across regions. If the client server and the DCS Redis instance are not in the same region, the instance cannot be accessed using its domain name address. You can manually map the domain name to the IP address in the hosts file or access the instance using its IP address.
                      • For details about how to connect to an instance, see Accessing an Instance.
                      diff --git a/docs/dcs/umn/dcs-faq-0220330.html b/docs/dcs/umn/dcs-faq-0220330.html index faeba5b4d..89264211d 100644 --- a/docs/dcs/umn/dcs-faq-0220330.html +++ b/docs/dcs/umn/dcs-faq-0220330.html @@ -4,8 +4,7 @@

                      Will Cached Data Be Retained After an Instance Is Restarted?

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

                      -

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

                      -

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

                      +

                      Master/Standby, read/write splitting, and cluster instances (except single-replica clusters) support AOF persistence by default. Data is retained after these instances are restarted. If AOF persistence is disabled (appendonly is set to no), data is deleted after the instances are restarted.

                      diff --git a/docs/dcs/umn/dcs-faq-0326021.html b/docs/dcs/umn/dcs-faq-0326021.html index 1db8e8a9b..8b9bdff4e 100644 --- a/docs/dcs/umn/dcs-faq-0326021.html +++ b/docs/dcs/umn/dcs-faq-0326021.html @@ -8,7 +8,7 @@
                    • Can I Change the VPC and Subnet for a DCS Redis Instance?
                      • -
                    • Why Aren't Security Groups Configured for DCS Redis 4.0/5.0/6.0 Instances?
                      +
                    • Why Aren't Security Groups Configured for DCS Redis 4.0 and Later Instances?
                    • Do DCS Redis Instances Limit the Size of a Key or Value?
                      • diff --git a/docs/dcs/umn/dcs-faq-0326024.html b/docs/dcs/umn/dcs-faq-0326024.html index 5d8de936b..506bd4319 100644 --- a/docs/dcs/umn/dcs-faq-0326024.html +++ b/docs/dcs/umn/dcs-faq-0326024.html @@ -8,7 +8,7 @@
                    • Can I Export Backup Data of DCS Redis Instances to RDB Files Using the Console?
                      • -
                    • Does DCS Support Data Persistence? What Is the Impact of Persistence?
                      +
                    • Do DCS Redis Instances Support Data Persistence? What Is the Impact of Persistence?
                    • When Will AOF Rewrites Be Triggered?
                      • @@ -16,8 +16,6 @@
                    • How Do I Enable the SYNC and PSYNC Commands?
                      • -
                    • Why Does Migration Task Creation Fail?
                      -
                    • Will the Same Keys Be Overwritten During Data Migration or Backup Import?
                    • Online Migration with Rump
                      diff --git a/docs/dcs/umn/dcs-faq-0427057.html b/docs/dcs/umn/dcs-faq-0427057.html index 7c39d0f3f..04a62f7b3 100644 --- a/docs/dcs/umn/dcs-faq-0427057.html +++ b/docs/dcs/umn/dcs-faq-0427057.html @@ -1,8 +1,10 @@

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

                      Redis timeouts happen on the client or server.

                      +
                      • Timeouts on the client are managed in the client code. Services can determine an appropriate timeout. For example, parameter timeout can be configured on Java Lettuce.

                        When a command times out on the client, errors, command blocks, or client connection retries may occur.

                        +
                      • On the server, the timeout parameter is set to 0 by default, indicating that connections will not be terminated. To modify the setting, see Modifying Configuration Parameters.

                        If the timeout parameter is not 0, idle connections between the client and server will be terminated as specified.

                        +
                      diff --git a/docs/dcs/umn/dcs-faq-0427081.html b/docs/dcs/umn/dcs-faq-0427081.html index d362408be..2289d4781 100644 --- a/docs/dcs/umn/dcs-faq-0427081.html +++ b/docs/dcs/umn/dcs-faq-0427081.html @@ -1,18 +1,20 @@ -

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

                      Do DCS Redis Instances Support Data Persistence? What Is the Impact of Persistence?

                      +

                      Is Persistence Supported?

                      Single-node: No

                      +

                      Master/Standby, read/write splitting, and cluster (except single-replica clusters): Yes

                      -

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

                      How Is Data Persisted?

                      • DCS Redis instances 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 Redis instances do not support RDB persistence by default and the save parameter cannot be manually configured. 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 in 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?
                      +

                      Impact of AOF Persistence

                      After AOF persistence is enabled, the Redis-Server process records operations in the AOF file for data persistence. This may have the following impacts:
                      • 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 for application acceleration, you are advised to disable AOF persistence for higher performance and stability.

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

                      -

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

                      +
                      +

                      Configuring Redis Persistence

                      Set the instance configuration parameter appendonly to no to disable, or yes to enable AOF persistence. (Not available for single-node instances.)

                      +

                      For details, see Modifying Configuration Parameters.

                      diff --git a/docs/dcs/umn/dcs-faq-0521003.html b/docs/dcs/umn/dcs-faq-0521003.html index f8ac6d734..23d3904c4 100644 --- a/docs/dcs/umn/dcs-faq-0521003.html +++ b/docs/dcs/umn/dcs-faq-0521003.html @@ -16,7 +16,7 @@

    Hot key

    A key is defined as a hot key if it is frequently requested or if it occupies a large number of resources. For example:

    +

    A hot key is most frequently accessed, or consumes significant resources. For example:

    • In a cluster instance, a shard processes 10,000 requests per second, among which 3000 are performed on the same key.
    • In a cluster instance, a shard uses a total of 100 Mbits/s inbound and outbound bandwidth, among which 80 Mbits/s is used by the HGETALL operation on a Hash key.
    Table 1 Scaling options supported by different DCS instances

    Cache Engine

    +
    - - - - + - - - - - + - - - - - + - - - - - - - - - - - @@ -73,31 +63,38 @@

    Change the replica quantity and capacity separately.

  • Impact of scaling -
    • 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

    +

    Read/Write Splitting

    Redis 3.0

    +

    Redis 3.0

    Scaling up/down

    +

    Scaling up/down

    Scaling up/down

    +

    Scaling up/down

    N/A

    +

    N/A

    Scaling out

    +

    Scaling out

    +

    N/A

    Redis 4.0

    +

    Redis 4.0/5.0

    Scaling up/down

    +

    Scaling up/down

    Scaling up/down

    +

    Scaling up/down and replica quantity change

    Scaling up/out, down/in, and replica quantity change

    +

    Scaling up/down, out/in, and replica quantity change

    N/A

    +

    Scaling up/down and out/in

    +

    Scaling up/down and replica quantity change

    Redis 5.0

    +

    Redis 6.0/7.0

    Scaling up/down

    +

    Scaling up/down

    Scaling up/down

    +

    Scaling up/down and replica quantity change

    Scaling up/out, down/in, and replica quantity change

    +

    Scaling up/down, out/in, and replica quantity change

    N/A

    +

    N/A

    Redis 6.0

    -

    Scaling up/down

    -

    Scaling up/down

    -

    Scaling up/down, out/in, and replica quantity change

    -

    N/A

    +

    N/A
    - - - -
    Table 2 Impact of scaling

    Instance Type

    +
    - - - - - - - - + + + +
    Table 2 Impact of scaling

    Instance Type

    Scaling Type

    +

    Scaling Type

    Impact

    +

    Impact

    Single-node and master/standby

    +

    Single-node , read/write splitting, and master/standby

    Scaling up/down

    +

    Scaling up/down

    • During scaling up, a DCS Redis 4.0/5.0/6.0 instance will be disconnected for several seconds and remain read-only for about 1 minute. During scaling down, connections will not be interrupted.
    • A DCS Redis 3.0 instance will be disconnected for several seconds 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.
    • Single-node DCS instances do not support data persistence. Scaling may compromise data reliability. After scaling, check whether the data is complete and import data if required. If there is important data, use a migration tool to migrate the data to other instances for backup.
    • For master/standby instances, backup records created before scale-down cannot be used after scale-down. If necessary, download the backup file in advance or back up the data again after scale-down.
    +
    • During scaling up, a DCS Redis 4.0 or later instance will be disconnected for several seconds and remain read-only for about 1 minute. During scaling down, connections will not be interrupted.
    • A DCS Redis 3.0 instance will be disconnected for several seconds 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.
    • Single-node DCS instances do not support data persistence. Scaling may compromise data reliability. After scaling, check whether the data is complete and import data if required. If there is important data, use a migration tool to migrate the data to other instances for backup.
    • For master/standby and read/write splitting instances, backup records created before scale-down cannot be used after scale-down. If necessary, download the backup file in advance or back up the data again after scale-down.

    Proxy Cluster and Redis Cluster

    +

    Proxy Cluster and Redis Cluster

    Scaling up/down

    +

    Scaling up/down

    • Scaling out by adding shards:
      • Scaling out does not interrupt connections but will occupy CPU resources, decreasing performance by up to 20%.
      • If the shard quantity increases, new Redis Server nodes are added, and data is automatically balanced to the new nodes, increasing the access latency.
      +
    • Scaling out by adding shards:
      • Scaling out does not interrupt connections but will occupy CPU resources, decreasing performance by up to 20%.
      • If the shard quantity increases, new Redis Server nodes are added, and data is automatically balanced to the new nodes, increasing the access latency.
    • Scaling in by reducing shards:
      • If the shard quantity decreases, nodes will be deleted. Before scaling in a Redis Cluster instance, ensure that the deleted nodes are not directly referenced in your application, to prevent service access exceptions.
      • Nodes will be deleted, and connections will be interrupted. If your application cannot reconnect to Redis or handle exceptions, you may need to restart the application after scaling.
      -
    • Scaling up by shard size without changing the shard quantity:
      • Insufficient memory of the node's VM will cause the node to migrate. Service connections may stutter and the instance may become read-only during the migration.
      • Increasing the node capacity when the VM memory is sufficient does not affect services.
      +
    • Scaling up by increasing the size per shard:
      • Insufficient memory of the node's VM will cause the node to migrate. Service connections may stutter and the instance may become read-only during the migration.
      • Increasing the node capacity when the VM memory is sufficient does not affect services.
    • Scaling down by reducing the shard size without changing the shard quantity has no impact.
    • To scale down an instance, ensure that the used memory of each node is less than 70% of the maximum memory per node of the new flavor.
    • The flavor changing operation may involve data migration, and the latency may increase. For a Redis Cluster instance, ensure that the client can process the MOVED and ASK commands. Otherwise, the request will fail.
    • If the memory becomes full during scaling due to a large amount of data being written, scaling will fail.
    • Before scaling, check for big keys through Cache Analysis. Redis has a limit on key migration. If the instance has any single key greater than 512 MB, scaling will fail when big key migration between nodes times out. The bigger the key, the more likely the migration will fail.
    • Before scaling a Redis Cluster instance, ensure that automated cluster topology refresh is enabled. If it is disabled, you will need to restart the client after scaling. For details about how to enable automated refresh if you use Lettuce, see an example of using Lettuce to connect to a Redis Cluster instance.
    • Backup records created before scaling cannot be used. If necessary, download the backup file in advance or back up the data again after scaling.

    Master/Standby, read/write splitting, and Redis Cluster instances

    +

    Scaling out/in (replica quantity change)

    +
    • Before adding or removing replicas for a Redis Cluster instance, ensure that automated cluster topology refresh is enabled. If it is disabled, you will need to restart the client after scaling. For details about how to enable automated refresh if you use Lettuce, see an example of using Lettuce to connect to a Redis Cluster instance.
    • Deleting replicas interrupts connections. If your application cannot reconnect to Redis or handle exceptions, you may need to restart the application after scaling. Adding replicas does not interrupt connections.
    • If the number of replicas is already the minimum supported by the instance, you can no longer delete replicas.
    +
    diff --git a/docs/dcs/umn/dcs-faq-0730058.html b/docs/dcs/umn/dcs-faq-0730058.html index 84e05bfea..e69e66cf3 100644 --- a/docs/dcs/umn/dcs-faq-0730058.html +++ b/docs/dcs/umn/dcs-faq-0730058.html @@ -3,7 +3,7 @@

    When Does a Master/Standby Switchover Occur?

    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/standby instance fails, a master/standby switchover will be triggered.

      For example, running commands that consume a lot of resources, such as KEYS commands, will cause CPU usage to spike and as result triggers a master/standby switchover.

      -
    • If you restart a master/standby instance on the DCS console, a master/standby switchover will be triggered.
    • If you scale up a single-node or master/standby instance, a master/standby switchover will be triggered.

      During scale-up, a new standby node with the new specifications is created. After full and incremental data on the master node is synchronized to the standby node, a master/standby switchover is performed and the original node is deleted.

      +
    • If you restart a master/standby instance on the DCS console, a master/standby switchover will be triggered.
    • If you scale up a single-node, read/write splitting, or master/standby instance, a master/standby switchover will be triggered.

      During scale-up, a new standby node with the new specifications is created. After full and incremental data on the master node is synchronized to the standby node, a master/standby switchover is performed and the original node is deleted.

    After a master/standby switchover occurs, you will receive a notification. Check whether the client services are running properly. If not, check whether the TCP connection is normal and whether it can be re-established after the master/standby switchover to restore the services.

    diff --git a/docs/dcs/umn/dcs-faq-210721001.html b/docs/dcs/umn/dcs-faq-210721001.html index 1026cabf5..7d0a9b0e7 100644 --- a/docs/dcs/umn/dcs-faq-210721001.html +++ b/docs/dcs/umn/dcs-faq-210721001.html @@ -1,7 +1,7 @@

    How Do I Enable the SYNC and PSYNC Commands?

    -
    • Migration within DCS:
      • By default, the SYNC and PSYNC commands can be used when self-hosted Redis is migrated to DCS.
      • During online migration between DCS Redis instances in the same region under the same account, the SYNC and PSYNC commands are automatically enabled.
      • During online migration between DCS Redis instances in different regions or under different accounts within a region, the SYNC and PSYNC commands are not automatically enabled, and online migration cannot be used. You can migrate data using backup files.
      +
      • Migration within DCS:
        • If the online migration task uses the same account and region as the source instance, select a DCS instance (cloud Redis) as the source. The SYNC and PSYNC commands will be automatically allowed on the source instance.
        • If the online migration task uses a different account or in a different region from the source instance, the source instance cannot be a DCS instance (cloud Redis) and the SYNC and PSYNC commands are disabled on the source instance. In this case, online migration on the console is unavailable. You can migrate data using backup import.
        • By default, the SYNC and PSYNC commands can be used when self-hosted Redis is migrated to DCS.
      • Migration from other cloud vendors to DCS:
        • Generally, cloud vendors disable the SYNC and PSYNC commands. If you want to use the online migration function on the DCS console, contact the O&M personnel of the source cloud vendor to enable the commands. For offline migration, you can import backup files.
        • If incremental migration is not required, you can perform full migration by referring to Online Full Migration of Redis from Another Cloud with redis-shake. This method does not depend on SYNC and PSYNC.
      diff --git a/docs/dcs/umn/dcs-faq-210721002.html b/docs/dcs/umn/dcs-faq-210721002.html deleted file mode 100644 index 08fd56750..000000000 --- a/docs/dcs/umn/dcs-faq-210721002.html +++ /dev/null @@ -1,13 +0,0 @@ - - -

      Why Does Migration Task Creation Fail?

      -

      Possible causes:

      -
      1. The underlying resources are insufficient.
      2. The specifications of the ECS used for the migration are insufficient.
      3. The memory of the target Redis created before the migration is less than that of the source Redis.
      -

      In such cases, contact technical support.

      -
      - - diff --git a/docs/dcs/umn/dcs-faq-211230001.html b/docs/dcs/umn/dcs-faq-211230001.html index 570d8c394..b6d60ecb2 100644 --- a/docs/dcs/umn/dcs-faq-211230001.html +++ b/docs/dcs/umn/dcs-faq-211230001.html @@ -30,7 +30,7 @@

    Maximum number of idle connections

    Set this parameter to the value of maxTotal.

    +

    Use the same configuration as maxTotal.

    minIdle

    @@ -45,14 +45,14 @@

    Maximum waiting time for obtaining a connection, in milliseconds

    The recommended maximum waiting time for obtaining a connection from the connection pool is the maximum tolerable timeout of a single service minus the timeout for command execution. For example, if the maximum tolerable HTTP timeout is 15s and the timeout of Redis requests is 10s, set this parameter to 5s.

    +

    The recommended maximum waiting time for obtaining a connection from the connection pool is the maximum tolerable timeout of a single service minus the timeout for command execution. For example, if the maximum tolerable HTTP failure is 15s and the timeout of Redis requests is 10s, set this parameter to 5s.

    timeout

    Command execution timeout, in milliseconds

    This parameter indicates the maximum timeout for running a Redis command. Set this parameter based on the service logic. Generally, you are advised to set this timeout to longer than 210 ms to ensure network fault tolerance. For special detection logic or environment exception detection, you can adjust this timeout to seconds.

    +

    This parameter indicates the maximum timeout for running a Redis command. Set this parameter based on the service logic. You are advised to set this timeout to least 210 ms to ensure network fault tolerance. For special detection logic or environment exception detection, you can adjust this timeout to seconds.

    minEvictableIdleTimeMillis

    @@ -73,7 +73,7 @@

    Indicates whether to check the connection validity using the ping command when borrowing connections from the resource pool. Invalid connections will be removed.

    If your service is extremely sensitive to connections and the performance is acceptable, you can set this parameter to True. Generally, you are advised to set this parameter to False to enable idle connection detection.

    +

    If your service is extremely sensitive to connections and the performance is acceptable, you can set this parameter to True. Generally, you are advised to set this parameter to False to disable idle connection detection.

    testWhileIdle

    diff --git a/docs/dcs/umn/dcs-faq-221222.html b/docs/dcs/umn/dcs-faq-221222.html index a1e87574d..086556022 100644 --- a/docs/dcs/umn/dcs-faq-221222.html +++ b/docs/dcs/umn/dcs-faq-221222.html @@ -1,8 +1,8 @@

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

    -

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

    -

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

    +

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

    +

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

    Figure 1 Instance addresses

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

    diff --git a/docs/dcs/umn/dcs-migrate-0220411.html b/docs/dcs/umn/dcs-migrate-0220411.html index f8f359a33..aab6f68d4 100644 --- a/docs/dcs/umn/dcs-migrate-0220411.html +++ b/docs/dcs/umn/dcs-migrate-0220411.html @@ -1,10 +1,13 @@ -

    Online Full Migration of Redis from Another Cloud with redis-shake

    -

    redis-shake is an open-source Redis migration tool. Its rump mode allows you to obtain the full data of a source Redis using the SCAN command and write the data to a target Redis. This migration solution does not involve the SYNC or PSYNC command and can be widely used for migration between self-built Redis and cloud Redis.

    -

    This section describes how to use the rump mode of redis-shake to migrate the full Redis data of another cloud service vendor at a time online to DCS.

    +

    Migrating from Another Cloud Online Using redis-shake

    +

    redis-shake is an open-source Redis migration tool. Its rump mode allows you to obtain the full data of a source Redis using the SCAN command and write the data to a target Redis. This migration solution does not involve the SYNC or PSYNC command and can be widely used for migration between self-built Redis and cloud Redis.

    +

    This section describes how to use the rump mode of redis-shake to migrate the full Redis data of another cloud service vendor at a time online to DCS.

    Figure 1 Data flow in this solution
    -

    Prerequisites

    • A DCS Redis instance has been created on the target cloud.
    • An ECS has been created on the target cloud for running redis-shake.
    • The ECS is in the same VPC as the DCS Redis instance and bound with an EIP.
    • The rump mode does not support incremental data migration. To keep data consistency, stop writing data to the source Redis before migration.
    • This solution applies only to same-database mapping and does not apply to inter-database mapping.
    • If the source Redis has multiple databases (there are databases other than DB0), and your DCS instance is a cluster, this solution cannot be used. (Cluster DCS instances support only DB0.)
    +

    +

    Notes and Constraints

    • The rump mode does not support incremental data migration. To keep data consistency, stop writing data to the source Redis before migration.
    • This solution applies only to same-database mapping and does not apply to inter-database mapping.
    • If the source Redis has multiple databases (there are databases other than DB0), and your DCS instance is a cluster, this solution cannot be used. (Cluster DCS instances support only DB0.)
    • To migrate to an instance with SSL enabled, disable the SSL setting first. For details, see Transmitting DCS Redis Data with Encryption Using SSL.
    +
    +

    Prerequisites

    • A DCS Redis instance has been created.
    • An ECS has been created for running redis-shake. The ECS must use the same VPC as the Redis instance, and be bound to EIPs.

    Procedure

    1. Install Nginx on the ECS and the source forwarding server. The following describes how to install Nginx on an ECS running CentOS 7.x. The commands vary depending on the OS.

      1. Add Nginx to the Yum repository.
        sudo rpm -Uvh http://nginx.org/packages/centos/7/noarch/RPMS/nginx-release-centos-7-0.el7.ngx.noarch.rpm
      2. Check whether Nginx has been added successfully.
        yum search nginx
        @@ -33,8 +36,8 @@ vi nginx.conf

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

        Figure 3 Verification result
      -

    2. Configure Nginx forwarding for the ECS.

      1. Log in to the Linux ECS and run the following commands to open and modify the configuration file:

        cd /etc/nginx

        -

        vi nginx.conf

        +

      2. Configure Nginx forwarding for the ECS.

        1. Log in to the Linux ECS and run the following commands to open and modify the configuration file:
          cd /etc/nginx
+vi nginx.conf
        2. Configuration example:
          stream {
     server {
         listen 6666;
@@ -53,7 +56,7 @@ vi nginx.conf

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

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

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

          Figure 6 Connection example
          -

        4. Prepare the migration tool redis-shake.

          1. Log in to the ECS.
          2. Download redis-shake. Version 2.0.3 is used as an example. You can use other redis-shake versions as required.
            wget https://github.com/tair-opensource/RedisShake/releases/download/release-v2.0.3-20200724/redis-shake-v2.0.3.tar.gz
            +

          3. Prepare the migration tool redis-shake.

            1. Log in to the ECS.
            2. Download redis-shake on the ECS. Version 2.0.3 is used as an example. You can use other redis-shake versions as required.
              wget https://github.com/tair-opensource/RedisShake/releases/download/release-v2.0.3-20200724/redis-shake-v2.0.3.tar.gz
            3. Decompress the redis-shake file.
              tar -xvf redis-shake-v2.0.3.tar.gz

          4. Configure the redis-shake configuration file.

            1. Go to the directory generated after the decompression.
              cd redis-shake-v2.0.3
              @@ -79,7 +82,7 @@ vi nginx.conf
    diff --git a/docs/dcs/umn/dcs-migrate-1117003.html b/docs/dcs/umn/dcs-migrate-1117003.html index 419f872de..c20ec51c0 100644 --- a/docs/dcs/umn/dcs-migrate-1117003.html +++ b/docs/dcs/umn/dcs-migrate-1117003.html @@ -1,53 +1,44 @@ -

    Offline Migration of Redis Cluster from Another Cloud with redis-shake

    +

    Backup Import from Another Cloud Using redis-shake

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

    +

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

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

    -

    Importing Backup Files

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

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

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

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

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

      +

      Notes and Constraints

      To migrate to an instance with SSL enabled, disable the SSL setting first. For details, see Transmitting DCS Redis Data with Encryption Using SSL.

      +
      +

      Prerequisites

      • A DCS Redis instance has been created. Note that the memory of the DCS Redis Cluster instance cannot be smaller than that of the source cluster.
      • An ECS has been created for running redis-shake. The ECS must use the same VPC, subnet, and security group as the Redis instance.
      +
      +

      Procedure

      1. Access the target Redis instance using redis-cli. Obtain the IP address and port of the master node of the target instance.
        redis-cli -h {target_redis_address} -p {target_redis_port} -a {target_redis_password} cluster nodes
        +
        • {target_redis_address}: connection address of the target DCS Redis instance.
        • {target_redis_port}: port of the target DCS Redis instance.
        • {target_redis_password}: password for connecting to the target DCS Redis instance.

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

        -

        After Redis is installed, it runs with redis-cli. To install Redis on CentOS, run the yum install redis command.

        +
      2. Install redis-shake on the prepared ECS.
        1. Log in to the ECS.
        2. Download redis-shake on the ECS. Version 2.0.3 is used as an example. You can use other redis-shake versions as required.
          wget https://github.com/tair-opensource/RedisShake/releases/download/release-v2.0.3-20200724/redis-shake-v2.0.3.tar.gz
          +
        3. Decompress the redis-shake file.
          tar -xvf redis-shake-v2.0.3.tar.gz
          +
        +

        If the source Redis is deployed in the data center intranet, install redis-shake on the intranet server. Export data and then upload the data to the cloud server as instructed by the following steps.

        -
      3. Prepare a cloud server and install redis-shake.

        redis-shake must be able to access the target Redis and bound to an EIP.

        -

        You can use ECS and configure the same VPC, subnet, and security group for the ECS and the DCS instance.

        -

        Download and decompress the release version of redis-shake. (The following uses v2.1.2 as an example. You can also use other redis-shake versions.)

        -

        -

        If the source Redis is deployed in the data center intranet, install redis-shake on the intranet server. Export data and then upload the data to the cloud server as instructed by the following steps

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

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

          -

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

          -
          execute runner[*run.CmdDump] finished!
          -

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

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

            Save and exit.

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

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

            +

            Press Esc to exit the editing mode and enter :wq!. Press Enter to save the configuration and exit the editing interface.

            +
          4. Run the following command to import the RDB file to the target instance:
            ./redis-shake -type restore -conf redis-shake.conf

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

            Enabled http stats, set status (incr), and wait forever.
          -
        5. Verify the migration.

          After data synchronization, access the DCS Redis Cluster instance using redis-cli. Run the info command to query the number of keys in the Keyspace section to confirm that data has been fully imported.

          +
        6. Verify the migration.

          After data synchronization, access the target Redis Cluster DCS instance using redis-cli. Run the info command to query the number of keys in the Keyspace section to confirm that data has been fully imported.

          If the data has not been fully imported, run the flushall or flushdb command to clear the cached data in the instance, and synchronize data again.

    diff --git a/docs/dcs/umn/dcs-migrate-demo02.html b/docs/dcs/umn/dcs-migrate-demo02.html index f7a16e9f4..a443c154e 100644 --- a/docs/dcs/umn/dcs-migrate-demo02.html +++ b/docs/dcs/umn/dcs-migrate-demo02.html @@ -1,83 +1,49 @@ -

    Self-Hosted Redis Cluster Migration with redis-shake

    -

    redis-shake is an open-source tool for migrating data online or offline (by importing backup files) between Redis Clusters. Data can be migrated to DCS Redis Cluster instances seamlessly because DCS Redis Cluster inherits the native Redis Cluster design.

    -

    The following describes how to use redis-shake to migrate data to a DCS Redis Cluster instance.

    -

    Migrating Data Online

    You can migrate data online from a self-hosted Redis Cluster to a DCS Redis Cluster instance as long as the two clusters are directly connected or connected through a transit server.

    -

    Data in Redis Clusters of another cloud cannot be migrated online because the SYNC and PSYNC commands are disabled by some vendors.

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

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

      -
    2. Prepare a cloud server and install redis-shake.

      redis-shake must be able to access both the source and target Redis. Bound an EIP to the cloud server.

      -

      You can use ECS and configure the same VPC, subnet, and security group for the ECS and the DCS instance. If the source Redis is deployed on cloud servers of another cloud, allow public access to the servers.

      -

      Download and decompress the release version of redis-shake. (The following uses v2.1.2 as an example. You can also use other redis-shake versions.)

      -

      -
    3. Locate the masters of the source and target Redis Clusters and obtain the IP addresses of the masters.

      Online data migration must be performed node by node. Run the following command to query the IP addresses and port numbers of all nodes in both the source and target Redis Clusters.

      -

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

      -

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

      -

      -

      After Redis is installed, it runs with redis-cli. To install Redis on CentOS, run the yum install redis command.

      -
      -
    4. Edit the redis-shake configuration file.

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

      -
      source.type = cluster
+
      Self-Hosted Redis Cluster Migration with redis-shake (Online)
      
+
      redis-shake is an open-source tool for migrating data online or offline (by importing backup files) between Redis Clusters. Data can be migrated to DCS Redis Cluster instances seamlessly because DCS Redis Cluster inherits the native Redis Cluster design.
      
+
      The following describes how to use Linux redis-shake to migrate self-hosted Redis Cluster to a DCS Redis Cluster instance online.
      
+
      Notes and Constraints
      • To migrate data from a self-hosted Redis Cluster instance to a DCS Redis Cluster instance online, ensure that the source Redis is connected to the target Redis, or use a transit cloud server to connect the source and target cluster instances.
      • To migrate to an instance with SSL enabled, disable the SSL setting first. For details, see Transmitting DCS Redis Data with Encryption Using SSL.
      
+
      
+
      Prerequisites
      • If a target DCS Redis instance is not available, create one first. For details, see Creating a DCS Redis Instance.
      • If you already have a DCS Redis instance, you do not need to create one again. For comparing migration data and reserving sufficient memory, you are advised to clear the instance data before the migration. For details, see Clearing DCS Instance Data. If any data exists on the target instance, duplicate data between the source and target is overwritten. If the data exists only on the target instance, the data will be retained.
      
+
      • An Elastic Cloud Server (ECS) has been created. For details about how to create an ECS, see Elastic Cloud Server User Guide.
        Select the same VPC, subnet, and security group as the DCS Redis Cluster instance, and bind EIPs to the ECS.
        
+
      • If the source self-hosted Redis Cluster is deployed on cloud servers of another cloud, allow public access to the servers.
      
+
      
+
      Obtaining Information of the Source and Target Redis Nodes
      1. Connect to the source and target Redis instances, respectively. Connect to Redis by referring to Accessing a DCS Redis Instance Through redis-cli.
      2. In online migration of Redis Clusters, the migration must be performed node by node. Run the following command to query the IP addresses and ports of all nodes in both the source and target Redis Clusters.
        redis-cli -h {redis_address} -p {redis_port} -a {redis_password} cluster nodes
        
+
        {redis_address} indicates the Redis connection address, {redis_port} indicates the Redis port, and {redis_password} indicates the Redis connection password.
        
+
        In the command output similar to the following, obtain the IP addresses and ports of all masters.
        
+
        
+
      
+
      
+
      Configuring the redis-shake Tool
      1. Log in to the ECS.
      2. Run the following command on the ECS to download the redis-shake: This section uses v2.1.2 as an example. You can also download other redis-shake versions as required.
        wget https://github.com/tair-opensource/RedisShake/releases/download/release-v2.1.2-20220329/release-v2.1.2-20220329.tar.gz
        
+
      3. Decompress the redis-shake file.
        tar -xvf redis-shake-v2.1.2.tar.gz
        
+
        
+
      4. Go to the redis-shake directory.
        cd redis-shake-v2.0.3
        
+
      5. Edit the redis-shake.conf file by providing the following information about all the masters of both the source and the target:
        vim redis-shake.conf
        
+
        The modification is as follows:
        source.type = cluster
 # If there is no password, skip the following parameter.
 source.password_raw = {source_redis_password}
 # IP addresses and port numbers of all masters of the source Redis Cluster, which are separated by semicolons (;).
-source.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}…{masterN_ip}:{masterN_port}
+source.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}...{masterN_ip}:{masterN_port}
 target.type = cluster
 # If there is no password, skip the following parameter.
 target.password_raw = {target_redis_password}
 # IP addresses and port numbers of all masters of the target instance, which are separated by semicolons (;).
-target.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}…{masterN_ip}:{masterN_port}
        
-
        Save and exit.
        
-
      6. Migrate data online.
        Run the following command to synchronize data between the source and the target Redis:
        
-
        ./redis-shake -type sync -conf redis-shake.conf
        
-
        If the following information is displayed, the full synchronization has been completed and incremental synchronization begins.
        
-
        sync rdb done.
        
-
        If the following information is displayed, no new data is incremented. You can stop the incremental synchronization by pressing Ctrl+C.
        
-
        sync:  +forwardCommands=0  +filterCommands=0  +writeBytes=0
        
-
        Figure 1 Online migration using redis-shake
        
-
      7. Verify the migration.
        After data synchronization, access the DCS Redis Cluster instance using redis-cli. Run the info command to query the number of keys in the Keyspace section to confirm that data has been fully imported.
        
-
        If the data has not been fully imported, run the flushall or flushdb command to clear the cached data in the instance, and synchronize data again.
        
-
      8. Clear the redis-shake configuration file.
      
+target.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}...{masterN_ip}:{masterN_port}
    -

    Importing Backup Files

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

    -

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

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

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

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

      -

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

      -

      -

      After Redis is installed, it runs with redis-cli. To install Redis on CentOS, run the yum install redis command.

      -
      -
    3. Prepare a cloud server and install redis-shake.

      redis-shake must be able to access the target Redis and bound to an EIP.

      -

      You can use ECS and configure the same VPC, subnet, and security group for the ECS and the DCS instance.

      -

      Download and decompress the release version of redis-shake. (The following uses v2.1.2 as an example.)

      -

      -

      If the source Redis is deployed in the data center intranet, install redis-shake on the intranet server. Export data and then upload the data to the cloud server as instructed by the following steps

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

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

        -

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

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

        Press Esc to exit the editing mode and enter :wq!. Press Enter to save the configuration and exit the editing interface.

        +
    -

    Save and exit.

    -
  • Run the following command to import the RDB file to the target instance:

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

    -

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

    -
    Enabled http stats, set status (incr), and wait forever.
    -
    • -
  • Verify the migration.

    After data synchronization, access the DCS Redis Cluster instance using redis-cli. Run the info command to query the number of keys in the Keyspace section to confirm that data has been fully imported.

    -

    If the data has not been fully imported, run the flushall or flushdb command to clear the cached data in the instance, and synchronize data again.

    -
    • +

    Migrating Data Online

    Run the following command to synchronize data between the source and the target Redis:
    ./redis-shake -type sync -conf redis-shake.conf
    +
    +

    If the following information is displayed, the full synchronization has been completed and incremental synchronization begins.

    +
    sync rdb done.
    +

    If the following information is displayed, no new data is incremented. You can stop the incremental synchronization by pressing Ctrl+C.

    +
    sync:  +forwardCommands=0  +filterCommands=0  +writeBytes=0
    +
    Figure 1 Online migration using redis-shake
    +
    +

    Verifying the Migration

    1. After the data synchronization, connect to the Redis Cluster DCS instance by referring to Accessing a DCS Redis Instance Through redis-cli.
    2. Run the info command to check whether the data has been successfully imported as required.

      If the data has not been fully imported, run the flushall or flushdb command to clear the cached data in the target instance, and migrate data again.

      +
    3. After the verification is complete, delete the redis shake configuration file.
    diff --git a/docs/dcs/umn/dcs-migrate-demo03.html b/docs/dcs/umn/dcs-migrate-demo03.html new file mode 100644 index 000000000..c85fc0c18 --- /dev/null +++ b/docs/dcs/umn/dcs-migrate-demo03.html @@ -0,0 +1,64 @@ + + +

    Self-Hosted Redis Cluster Migration with redis-shake (RDB)

    +

    redis-shake is an open-source tool for migrating data online or offline (by importing backup files) between Redis Clusters. Data can be migrated to DCS Redis Cluster instances seamlessly because DCS Redis Cluster inherits the native Redis Cluster design.

    +

    The following describes how to use Linux redis-shake to migrate self-hosted Redis Cluster to a DCS Redis Cluster instance offline.

    +

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

    +
    +

    Notes and Constraints

    To migrate to an instance with SSL enabled, disable the SSL setting first. For details, see Transmitting DCS Redis Data with Encryption Using SSL.

    +
    +

    Prerequisites

    • A DCS Redis Cluster instance has been created. For details about how to create one, see Creating a DCS Redis Instance.

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

      +
    • An Elastic Cloud Server (ECS) has been created. For details about how to create an ECS, see Elastic Cloud Server User Guide. Select the same VPC, subnet, and security group as the DCS Redis Cluster instance.
    +
    +

    Obtaining Information of the Source and Target Redis Nodes

    1. Connect to the source and target Redis instances, respectively. Connect to Redis by referring to Accessing a DCS Redis Instance Through redis-cli.
    2. In online migration of Redis Clusters, the migration must be performed node by node. Run the following command to query the IP addresses and ports of all nodes in both the source and target Redis Clusters.
      redis-cli -h {redis_address} -p {redis_port} -a {redis_password} cluster nodes
      +

      {redis_address} indicates the Redis connection address, {redis_port} indicates the Redis port, and {redis_password} indicates the Redis connection password.

      +

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

      +

      +
    +
    +

    Installing RedisShake

    1. Log in to the ECS.
    2. Run the following command on the ECS to download the redis-shake: This section uses v2.1.2 as an example. You can also download other redis-shake versions as required.
      wget https://github.com/tair-opensource/RedisShake/releases/download/release-v2.1.2-20220329/release-v2.1.2-20220329.tar.gz
      +
    3. Decompress the redis-shake file.
      tar -xvf redis-shake-v2.1.2.tar.gz
      +

      +
    +

    If the source cluster is deployed in the data center intranet, install redis-shake on the intranet server. Export the source cluster backup file by referring to Exporting the Backup File. Upload the backup to the cloud server as instructed by the following steps

    +
    +
    +

    Exporting the Backup File

    1. Go to the redis-shake directory.
      cd redis-shake-v2.0.3
      +
    2. Edit the redis-shake.conf file by providing the following information about all the masters of the source:
      vim redis-shake.conf
      +
      The modification is as follows:
      source.type = cluster
+# If there is no password, skip the following parameter.
+source.password_raw = {source_redis_password}
+# IP addresses and port numbers of all masters of the source Redis Cluster, which are separated by semicolons (;).
+source.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}...{masterN_ip}:{masterN_port}
      +
      +

      Press Esc to exit the editing mode and enter :wq!. Press Enter to save the configuration and exit the editing interface.

      +
    3. Run the following command to export the RDB file:
      ./redis-shake -type dump -conf redis-shake.conf
      +

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

      +
      execute runner[*run.CmdDump] finished!
      +
    +
    +

    Importing the Backup File

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

      Press Esc to exit the editing mode and enter :wq!. Press Enter to save the configuration and exit the editing interface.

      +
    3. Run the following command to import the RDB file to the target instance:
      ./redis-shake -type restore -conf redis-shake.conf
      +

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

      +
      Enabled http stats, set status (incr), and wait forever.
      +
    +
    +

    Verifying the Migration

    1. After the data synchronization, connect to the Redis Cluster DCS instance by referring to Accessing a DCS Redis Instance Through redis-cli.
    2. Run the info command to check whether the data has been successfully imported as required.

      If the data has not been fully imported, run the flushall or flushdb command to clear the cached data in the target instance, and migrate data again.

      +
    3. After the verification is complete, delete the redis shake configuration file.
    +
    +
    + + diff --git a/docs/dcs/umn/dcs-migration-0312001.html b/docs/dcs/umn/dcs-migration-0312001.html index e7adb5eb5..70115e654 100644 --- a/docs/dcs/umn/dcs-migration-0312001.html +++ b/docs/dcs/umn/dcs-migration-0312001.html @@ -6,7 +6,7 @@
    • Number of instances
    • Number of databases (DBs) configured for each instance
    • Number of keys in each DB
    • DBs used for your services
    • Space occupied by each instance
    • Redis version
    • Redis instance configurations (single-node, master/standby, or cluster)
    • Mapping relationships between your services and instances
    Plan the following information about DCS instances based on the collected information:
    • Number of instances to be applied for
    • Specifications and type (single-node, master/standby, or cluster) of each instance
    • Virtual Private Clouds (VPCs), security groups, and subnets, and security groups, to which the instances and services belong
    -

    redis-cli -h ${redis_address} -p ${port}

    +

    redis-cli -h ${redis_address} -p ${port}

    • Run the following command to query the data distribution and obtain the IDs of DBs with data and the number of keys in each DB:

      info keyspace

      Query and record the number of keys in each DB for subsequent migration verification.

    @@ -20,7 +20,7 @@
  • Network resources

    Create VPCs and subnets based on service planning.

  • Server resources

    Apply for ECSs to bear Redis clients. The ECSs are used to export or import cached data.

    Recommended ECS specifications are 8 vCPUs | 16 GB or higher.

    -
  • DCS instances

    Create DCS instances based on the migration planning. If the number of instances exceeds the default quota, submit a service ticket or contact technical support.

    +
  • DCS instances

    Create DCS instances based on the migration planning. If the number of instances exceeds the default quota, submit a service ticket or contact customer service.

  • Related tools

    Install the FTP tool and Redis migration tools.

  • Information to be collected

    Collect the contact information of people involved in the migration, server addresses, login credentials, cache instance information, and DB information.

  • Overall migration plan

    Formulate the overall migration plan, including the personnel arrangement, rehearsal, migration, verification, service switchover, and rollback solutions.

    diff --git a/docs/dcs/umn/dcs-migration-0312002.html b/docs/dcs/umn/dcs-migration-0312002.html index 55ea2b652..0a31aff31 100644 --- a/docs/dcs/umn/dcs-migration-0312002.html +++ b/docs/dcs/umn/dcs-migration-0312002.html @@ -4,15 +4,17 @@
    diff --git a/docs/dcs/umn/dcs-migration-0312003.html b/docs/dcs/umn/dcs-migration-0312003.html index 12d1acd6f..488e7cd93 100644 --- a/docs/dcs/umn/dcs-migration-0312003.html +++ b/docs/dcs/umn/dcs-migration-0312003.html @@ -1,69 +1,79 @@ - -

    Online Migration Between DCS Redis Instances

    - -

    Application Scenarios

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

    -
    • If the SYNC and PSYNC commands are disabled on the source Redis instance, enable them before performing online migration. Otherwise, the migration fails. If you use a DCS Redis instance for online migration, the SYNC command is automatically enabled.
    • You cannot use public networks for online migration.
    • During online migration, you are advised to set repl-timeout on the source instance to 300s and client-output-buffer-limit to 20% of the maximum memory of the instance.
    • The source must be Redis 3.0 or later.
    +

    Online Migration Between Instances

    +

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

    +

    During online migration, data is essentially synchronized in full to a new replica. Therefore, perform online migration during low-demand hours. Otherwise, source instance CPU usage may surge and latency may increase.

    +

    Notes and Constraints

    • You cannot use public networks for online migration.
    • Before migrating data, read through Migration Solution Notes to learn about the DCS data migration function and select an appropriate target instance.
    • Migrating a later Redis instance to an earlier one may fail.
    • For earlier instances whose passwords contain single quotation marks ('), modify the password for online migration or try other methods.
    • By default, a cluster instance has only one DB (DB0). Before you migrate data from a multi-DB single-node or master/standby instance to a Redis Cluster instance, check whether any data exists on databases other than DB0. To ensure that the migration succeeds, move all data to DB0 by referring to Online Migration with Rump.
    • During online migration, you are advised to set repl-timeout on the source instance to 300s and client-output-buffer-slave-hard-limit and client-output-buffer-slave-soft-limit to 20% of the maximum memory of the instance.
    • To migrate to an instance with SSL enabled, disable the SSL setting first. For details, see Transmitting DCS Redis Data with Encryption Using SSL.
    -

    Impacts on Services

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

    -
    -

    Prerequisites

    • Before migrating data, read through Migration Tools and Schemes to learn about the DCS data migration function and select an appropriate target instance.
    • By default, a cluster instance has only one DB (DB0). Before you migrate data from a multi-DB single-node or master/standby instance to a Redis Cluster instance, check whether any data exists on databases other than DB0. To ensure that the migration succeeds, move all data to DB0 by referring to Online Migration with Rump.
    -
    -

    Step 1: Obtain the Source Redis Address

    Obtain the IP address/domain name and port number of the source Redis instance.

    -
    -

    Step 2: Prepare the Target DCS Redis Instance