vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity

DCS UMN 20240313 version

Browse Source 
Reviewed-by: Mützel, Andrea <andrea.muetzel@t-systems.com>
Co-authored-by: Chen, Junjie <chenjunjie@huawei.com>
Co-committed-by: Chen, Junjie <chenjunjie@huawei.com>
This commit is contained in:
Chen, Junjie 2024-04-10 14:46:00 +00:00 committed by zuul
parent d804d7d1be
commit 2b90aa9fff
63 changed files with 566 additions and 398 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/dcs/umn/ALL_META.TXT.json
View File

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

16
docs/dcs/umn/CLASS.TXT.json
View File

@ -36,7 +36,7 @@
"code":"4"
},
{
"desc":"Single-node DCS Redis instances are available in versions 3.0/4.0/5.0/6.0.You cannot upgrade the Redis version for an instance. For example, a single-node DCS Redis 4.0 i",
"desc":"A single-node DCS Redis instance has only one node and does not support data persistence. They are suitable for cache services that do not require data reliability.You ca",
"product_code":"dcs",
"title":"Single-Node Redis",
"uri":"CacheSingleNode.html",
@ -45,7 +45,7 @@
"code":"5"
},
{
"desc":"This section describes master/standby DCS Redis instances. Redis versions available for master/standby DCS Redis instances include Redis 3.0, 4.0, 5.0, and 6.0.You cannot",
"desc":"This section describes master/standby DCS Redis instances.You cannot upgrade the Redis version for an instance. For example, a master/standby DCS Redis 4.0 instance canno",
"product_code":"dcs",
"title":"Master/Standby Redis",
"uri":"CacheMasterSlave.html",
@ -1377,7 +1377,7 @@
"code":"153"
},
{
"desc":"Yes. DCS for Redis 4.0 and 5.0 support Redis Clusters. DCS for Redis 3.0 supports Proxy Clusters.",
"desc":"Yes. DCS for Redis 4.0 and later support Redis Clusters. DCS for Redis 3.0 supports Proxy Clusters.",
"product_code":"dcs",
"title":"Does DCS for Redis Support Redis Clusters?",
"uri":"dcs-faq-0730020.html",
@ -1386,7 +1386,7 @@
"code":"154"
},
{
"desc":"Cluster instances and master/standby DCS Redis 4.0/5.0/6.0 instances support Sentinels. Sentinels monitor the running status of both the master and standby nodes of a mas",
"desc":"Cluster instances and master/standby DCS Redis 4.0 and later instances support Sentinels. Sentinels monitor the running status of both the master and standby nodes of a m",
"product_code":"dcs",
"title":"Does DCS for Redis Support Sentinel?",
"uri":"dcs-faq-0730021.html",
@ -1440,7 +1440,7 @@
"code":"160"
},
{
"desc":"Master/Standby and cluster DCS Redis instances can be deployed across availability zones (AZs).If instances nodes in an AZ are faulty, nodes in other AZs will not be affe",
"desc":"Master/Standby and cluster DCS Redis instances can be deployed across availability zones (AZs).If instance nodes in an AZ are faulty, nodes in other AZs will not be affec",
"product_code":"dcs",
"title":"Does DCS Support Cross-AZ Deployment?",
"uri":"dcs-faq-0730029.html",
@ -1503,7 +1503,7 @@
"code":"167"
},
{
"desc":"After a single-node DCS instance is restarted, data in the instance is deleted.Master/standby and cluster instances (except single-replica clusters) support AOF persisten",
"desc":"After a single-node DCS instance is restarted, data in the instance is deleted.Master/Standby and cluster instances (except single-replica clusters) support AOF persisten",
"product_code":"dcs",
"title":"Will Cached Data Be Retained After an Instance Is Restarted?",
"uri":"dcs-faq-0220330.html",
@ -1701,7 +1701,7 @@
"code":"189"
},
{
"desc":"Flow control is triggered when the traffic used by a Redis instance in a period exceeds the maximum bandwidth.For details about the maximum allowed bandwidth, see the \"As",
"desc":"Flow control is triggered when the traffic used by a Redis instance in a period exceeds the maximum bandwidth.For details about the maximum bandwidth of an instance flavo",
"product_code":"dcs",
"title":"Why Is Flow Control Triggered? How Do I Handle It?",
"uri":"dcs-faq-0220721.html",
@ -1746,7 +1746,7 @@
"code":"194"
},
{
"desc":"AOF rewrites involve the following concepts:Rewrite window, which is currently 01:00 to 04:59Disk usage threshold, which is 50%AOF rewrites are triggered in the following",
"desc":"AOF rewrites involve the following concepts:Rewrite window, which is currently 01:00 to 04:59Disk usage threshold, which is 50%Dataset memory, which is the percentage of ",
"product_code":"dcs",
"title":"When Will AOF Rewrites Be Triggered?",
"uri":"dcs-faq-210706001.html",

4
docs/dcs/umn/CacheCluster.html
View File

@ -5,10 +5,10 @@
<ul id="CacheCluster__ul1265853801012"><li id="CacheCluster__li365893819101">The client is decoupled from the cloud service.</li><li id="CacheCluster__li565815388101">They support millions of concurrent requests, equivalent to Redis Cluster instances.</li><li id="CacheCluster__li465893811014">A wide range of memory specifications adapt to different scenarios.</li></ul>
<div class="note" id="CacheCluster__note134811721192210"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="CacheCluster__ul1758133822318"><li id="CacheCluster__li758133852319">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.</li></ul>
</div></div>
<div class="section" id="CacheCluster__section861823615325"><h4 class="sectiontitle">Proxy Cluster DCS Redis 3.0 Instances</h4><p id="CacheCluster__p10878151913448">Proxy Cluster DCS Redis 3.0 instances are compatible with <a href="https://github.com/CodisLabs/codis" target="_blank" rel="noopener noreferrer">codis</a>. The specifications range from 64 GB to 1024 GB, meeting requirements for <strong id="CacheCluster__b13211893475612">millions of concurrent connections</strong> and <strong id="CacheCluster__b45541541375612">massive data cache</strong>. Distributed data storage and access is implemented by DCS, without requiring development or maintenance.</p>
<div class="section" id="CacheCluster__section861823615325"><h4 class="sectiontitle">Proxy Cluster DCS Redis 3.0 Instances</h4><p id="CacheCluster__p10878151913448">Proxy Cluster DCS Redis 3.0 instances are compatible with <a href="https://github.com/CodisLabs/codis" target="_blank" rel="noopener noreferrer">codis</a>. The specifications range from 64 GB to 1024 GB, meeting requirements for <strong id="CacheCluster__b153271812575">millions of concurrent connections</strong> and <strong id="CacheCluster__b10334187579">massive data cache</strong>. Distributed data storage and access is implemented by DCS, without requiring development or maintenance.</p>
<p id="CacheCluster__p186619405101">Each Proxy Cluster instance consists of load balancers, proxies, cluster managers, and <a href="dcs-pd-200312004.html#dcs-pd-200312004__en-us_topic_0145956240_section20999323134412">shards</a>.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="CacheCluster__table13310319184" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Specifications of Proxy Cluster DCS Redis 3.0 instances</caption><thead align="left"><tr id="CacheCluster__row9312131191817"><th align="left" class="cellrowborder" valign="top" width="28.52%" id="mcps1.3.4.4.2.4.1.1"><p id="CacheCluster__p13128115183">Total Memory</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="CacheCluster__table13310319184" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Total memory, proxies, and shards of Proxy Cluster DCS Redis 3.0 instances</caption><thead align="left"><tr id="CacheCluster__row9312131191817"><th align="left" class="cellrowborder" valign="top" width="28.52%" id="mcps1.3.4.4.2.4.1.1"><p id="CacheCluster__p13128115183">Total Memory</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="36.13%" id="mcps1.3.4.4.2.4.1.2"><p id="CacheCluster__p231214131810">Proxies</p>
</th>

2
docs/dcs/umn/CacheMasterSlave.html
View File

@ -1,7 +1,7 @@
<a name="CacheMasterSlave"></a><a name="CacheMasterSlave"></a>
<h1 class="topictitle1">Master/Standby Redis</h1>
<div id="body1600250974776"><p id="CacheMasterSlave__p11826145419223">This section describes master/standby DCS Redis instances. Redis versions available for master/standby DCS Redis instances include Redis 3.0, 4.0, 5.0, and 6.0.</p>
<div id="body1600250974776"><p id="CacheMasterSlave__p312320720233">This section describes master/standby DCS Redis instances.</p>
<div class="note" id="CacheMasterSlave__note67021744211"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="CacheMasterSlave__p157220441816">You cannot upgrade the Redis version for an instance. For example, a master/standby DCS Redis 4.0 instance cannot be upgraded to a master/standby DCS Redis 5.0 instance. If your service requires the features of higher Redis versions, create a DCS Redis instance of a higher version and then migrate data from the old instance to the new one.</p>
</div></div>
<div class="section" id="CacheMasterSlave__section2115135632817"><h4 class="sectiontitle">Features</h4><p id="CacheMasterSlave__p29361111432">Master/Standby DCS instances have higher availability and reliability than single-node DCS instances.</p>

4
docs/dcs/umn/CacheSingleNode.html
View File

@ -1,8 +1,8 @@
<a name="CacheSingleNode"></a><a name="CacheSingleNode"></a>
<h1 class="topictitle1">Single-Node Redis</h1>
<div id="body1600250973735"><p id="CacheSingleNode__p11541643103710">Single-node DCS Redis instances are available in versions 3.0/4.0/5.0/6.0.</p>
<div class="note" id="CacheSingleNode__note5258316142416"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="CacheSingleNode__p11302105411119">You cannot upgrade the Redis version for an instance. For example, a single-node DCS Redis 4.0 instance cannot be upgraded to a single-node DCS Redis 5.0 instance. If your service requires the features of higher Redis versions, create a DCS Redis instance of a higher version and then migrate data from the old instance to the new one.</p>
<div id="body1600250973735"><p id="CacheSingleNode__p14829184616197">A single-node DCS Redis instance has only one node and does not support data persistence. They are suitable for cache services that do not require data reliability.</p>
<div class="note" id="CacheSingleNode__note5258316142416"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="CacheSingleNode__ul1225591220208"><li id="CacheSingleNode__li925551214201">You cannot upgrade the Redis version of an instance. For example, a single-node DCS instance cannot be upgraded from Redis 4.0 to Redis 5.0. If you need Redis features of later versions, create a DCS Redis instance of a later version and then migrate data from the earlier instance to the new one.</li><li id="CacheSingleNode__li1525561282018">Single-node instances cannot ensure data persistence and do not support manual or scheduled data backup. Exercise caution before using them.</li></ul>
</div></div>
<div class="section" id="CacheSingleNode__section19260552619"><h4 class="sectiontitle">Features</h4><ol id="CacheSingleNode__ol67507623011"><li id="CacheSingleNode__li107501061301">Low system overhead and high QPS<p id="CacheSingleNode__p22461983014"><a name="CacheSingleNode__li107501061301"></a><a name="li107501061301"></a>Single-node instances do not support data synchronization or data persistence, reducing system overhead and supporting higher concurrency. QPS of single-node DCS Redis instances reaches up to 100,000.</p>
</li><li id="CacheSingleNode__li77501762306">Process monitoring and automatic fault recovery<p id="CacheSingleNode__p1917103533114"><a name="CacheSingleNode__li77501762306"></a><a name="li77501762306"></a>With an HA monitoring mechanism, if a single-node DCS instance becomes faulty, a new process is started within 30 seconds to resume service provisioning.</p>

2
docs/dcs/umn/cache-instance-password.html
View File

@ -9,7 +9,7 @@
</div></div>
<div class="section" id="cache-instance-password__en-us_topic_0157078204_section4863101016391"><h4 class="sectiontitle">Using Passwords Securely</h4><ol id="cache-instance-password__en-us_topic_0157078204_ol2887434144012"><li id="cache-instance-password__en-us_topic_0157078204_li38871534174016">Hide the password when using redis-cli.<p id="cache-instance-password__en-us_topic_0157078204_p188144904012"><a name="cache-instance-password__en-us_topic_0157078204_li38871534174016"></a><a name="en-us_topic_0157078204_li38871534174016"></a>If the <strong id="cache-instance-password__en-us_topic_0157078204_b188123233553">-a &lt;password&gt;</strong> option is used in redis-cli in Linux, the password is prone to leakage because it is logged and kept in the history. You are advised not to use <strong id="cache-instance-password__b266115341594">-a &lt;password&gt;</strong> when running commands in redis-cli. After connecting to Redis, run the <strong id="cache-instance-password__b136618340913">auth</strong> command to complete authentication as shown in the following example:</p>
<pre class="screen" id="cache-instance-password__en-us_topic_0157078204_screen0635125654716">$ redis-cli -h 192.168.0.148 -p 6379
redis 192.168.0.148:6379&gt;<strong id="cache-instance-password__en-us_topic_0157078204_b535814614336">auth</strong> <em id="cache-instance-password__en-us_topic_0157078204_i4796183254916">yourPassword</em>
redis 192.168.0.148:6379&gt;auth <em id="cache-instance-password__i16439662062">{yourPassword}</em>
OK
redis 192.168.0.148:6379&gt;</pre>
</li><li id="cache-instance-password__en-us_topic_0157078204_li1188711348407">Use interactive password authentication or switch between users with different permissions.<p id="cache-instance-password__en-us_topic_0157078204_p3411122543917"><a name="cache-instance-password__en-us_topic_0157078204_li1188711348407"></a><a name="en-us_topic_0157078204_li1188711348407"></a>If the script involves DCS instance access, use interactive password authentication. To enable automatic script execution, manage the script as another user and authorize execution using sudo.</p>

2
docs/dcs/umn/dcs-faq-0220330.html
View File

@ -4,7 +4,7 @@
<h1 class="topictitle1">Will Cached Data Be Retained After an Instance Is Restarted?</h1>
<div id="body8662426"><p id="dcs-faq-0220330__en-us_topic_0000001226633976_p2938536145015">After a single-node DCS instance is restarted, data in the instance is deleted.</p>
<p id="dcs-faq-0220330__en-us_topic_0000001226633976_p157943519577">Master/standby and cluster instances (except single-replica clusters) support AOF persistence by default. Data is retained after these instances are restarted.</p>
<p id="dcs-faq-0220330__en-us_topic_0000001226633976_p157943519577">Master/Standby and cluster instances (except single-replica clusters) support AOF persistence by default. Data is retained after these instances are restarted.</p>
<p id="dcs-faq-0220330__en-us_topic_0000001226633976_p2938236195019">If AOF persistence is disabled (<strong id="dcs-faq-0220330__en-us_topic_0000001226633976_b1775833072617">appendonly</strong> is set to <strong id="dcs-faq-0220330__en-us_topic_0000001226633976_b1880493211267">no</strong>), data is deleted after the instances are restarted.</p>
</div>
<div>

2
docs/dcs/umn/dcs-faq-0220721.html
View File

@ -2,7 +2,7 @@
<h1 class="topictitle1">Why Is Flow Control Triggered? How Do I Handle It?</h1>
<div id="body8662426"><p id="dcs-faq-0220721__en-us_topic_0000001357973609_p11171144915210">Flow control is triggered when the traffic used by a Redis instance in a period exceeds the maximum bandwidth.</p>
<div class="note" id="dcs-faq-0220721__en-us_topic_0000001357973609_note19860103015720"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="dcs-faq-0220721__en-us_topic_0000001357973609_p662045412561">For details about the maximum allowed bandwidth, see the "Assured/Maximum Bandwidth" column of different instance types listed in <a href="en-us_topic_0054235835.html">DCS Instance Specifications</a>.</p>
<div class="note" id="dcs-faq-0220721__en-us_topic_0000001357973609_note19860103015720"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="dcs-faq-0220721__en-us_topic_0000001357973609_p662045412561">For details about the maximum bandwidth of an instance flavor, see <a href="en-us_topic_0054235835.html">Instance Specifications</a>, or refer to the page of creating an instance on the console.</p>
</div></div>
<p id="dcs-faq-0220721__en-us_topic_0000001357973609_p1273182501517">Even if the bandwidth usage is low, flow control may still be triggered. The real-time bandwidth usage is reported once in each reporting period. Flow controls are checked every second. The traffic may surge within seconds and then fall back between reporting periods. By the time the bandwidth usage is reported, it may have already restored to the normal level.</p>
<p id="dcs-faq-0220721__en-us_topic_0000001357973609_p206341115114814">For master/standby instances:</p>

3
docs/dcs/umn/dcs-faq-0427081.html
View File

@ -10,7 +10,8 @@
</div>
<div class="section" id="dcs-faq-0427081__en-us_topic_0000001152024118_section1530716418282"><h4 class="sectiontitle">Impact of AOF Persistence</h4><div class="p" id="dcs-faq-0427081__en-us_topic_0000001152024118_p154892314174">After AOF persistence is enabled, the Redis-Server process needs to record operations in the AOF file for data persistence.<ul id="dcs-faq-0427081__en-us_topic_0000001152024118_ul1986274393117"><li id="dcs-faq-0427081__en-us_topic_0000001152024118_li3321124219310">If the disk or I/O of the underlying compute node is faulty, the latency may increase or a master/standby switchover may occur.</li><li id="dcs-faq-0427081__en-us_topic_0000001152024118_li415512683212">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 <a href="dcs-faq-210706001.html">When Will AOF Rewrites Be Triggered?</a></li></ul>
</div>
<p id="dcs-faq-0427081__en-us_topic_0000001152024118_p2024623618266">If DCS instances are used to accelerate applications, you are advised to disable persistence for higher performance and stability. Exercise caution when disabling persistence. Without persistence, cached data may be lost in extreme scenarios (for example, when both the master and standby nodes are faulty).</p>
<p id="dcs-faq-0427081__en-us_topic_0000001152024118_p13384536152612">If DCS instances are used for application acceleration, you are advised to disable AOF persistence for higher performance and stability.</p>
<p id="dcs-faq-0427081__en-us_topic_0000001152024118_p2024623618266"><strong id="dcs-faq-0427081__en-us_topic_0000001152024118_b14799129183512">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.</strong></p>
<p id="dcs-faq-0427081__en-us_topic_0000001152024118_p13246173612268">To disable AOF persistence, set parameter <strong id="dcs-faq-0427081__en-us_topic_0000001152024118_b158831227155919">appendonly</strong> to <strong id="dcs-faq-0427081__en-us_topic_0000001152024118_b488312785910">no</strong> on the instance details page.</p>
</div>
</div>

4
docs/dcs/umn/dcs-faq-0513001.html
View File

@ -37,8 +37,8 @@
</tbody>
</table>
</div>
<p id="dcs-faq-0513001__en-us_topic_0000001152183968_p81021619517">Bandwidth usage = (Input flow + Output flow)/(2 x Maximum bandwidth) x 100%</p>
<p id="dcs-faq-0513001__en-us_topic_0000001152183968_p9331103545411">According to the formula, the bandwidth usage counts in the input flow and output flow, which include the traffic for replication between the master and replicas. Therefore, the total traffic is greater than the normal service traffic.</p>
<p id="dcs-faq-0513001__en-us_topic_0000001152183968_p15732252122318">Bandwidth usage = (Input flow + Output flow)/(2 x Maximum bandwidth) x 100%</p>
<p id="dcs-faq-0513001__en-us_topic_0000001152183968_p9331103545411">According to the formula, the bandwidth usage counts in the input flow and output flow, which include the traffic for replication between the master and replicas. Therefore, the total bandwidth usage is larger than the normal service traffic, and may exceed 100%.</p>
<p id="dcs-faq-0513001__en-us_topic_0000001152183968_p17209224155218">If the value of the <strong id="dcs-faq-0513001__en-us_topic_0000001152183968_b4139183117258">Flow Control Times</strong> metric is larger than 0, the maximum bandwidth has been reached and flow control has been performed.</p>
<p id="dcs-faq-0513001__en-us_topic_0000001152183968_p62091247528">However, flow control decisions are made without considering the traffic for replication between the master and replicas. Therefore, sometimes the bandwidth usage exceeds 100% but the number of flow control times is 0.</p>
</div>

2
docs/dcs/umn/dcs-faq-0730020.html
View File

@ -1,7 +1,7 @@
<a name="dcs-faq-0730020"></a><a name="dcs-faq-0730020"></a>
<h1 class="topictitle1">Does DCS for Redis Support Redis Clusters?</h1>
<div id="body1596093268950"><p id="dcs-faq-0730020__en-us_topic_0152099097_p725111122119">Yes. DCS for Redis 4.0 and 5.0 support Redis Clusters. DCS for Redis 3.0 supports Proxy Clusters.</p>
<div id="body1596093268950"><p id="dcs-faq-0730020__en-us_topic_0152099097_p725111122119">Yes. DCS for Redis 4.0 and later support Redis Clusters. DCS for Redis 3.0 supports Proxy Clusters.</p>
</div>
<div>
<div class="familylinks">

4
docs/dcs/umn/dcs-faq-0730021.html
View File

@ -1,8 +1,8 @@
<a name="dcs-faq-0730021"></a><a name="dcs-faq-0730021"></a>
<h1 class="topictitle1">Does DCS for Redis Support Sentinel?</h1>
<div id="body1596093268950"><p id="dcs-faq-0730021__en-us_topic_0152099097_p047315232012">Cluster instances and master/standby DCS Redis 4.0/5.0/6.0 instances support Sentinels. Sentinels monitor the running status of both the master and standby nodes of a master/standby instance and each shard of a cluster instance. If the master node becomes faulty, a failover will be performed.</p>
<p id="dcs-faq-0730021__en-us_topic_0152099097_p74691819125910">However, DCS for Redis 3.0 does not support Redis Sentinel. Instead, it uses keepalive to monitor master and replica nodes and to manage failovers.</p>
<div id="body1596093268950"><p id="dcs-faq-0730021__en-us_topic_0152099097_p047315232012">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.</p>
<p id="dcs-faq-0730021__en-us_topic_0152099097_p74691819125910">DCS for Redis 3.0 does not support Redis Sentinel. Instead, it uses keepalive to monitor master and replica nodes and to manage failovers.</p>
</div>
<div>
<div class="familylinks">

2
docs/dcs/umn/dcs-faq-0730025.html
View File

@ -2,7 +2,7 @@
<h1 class="topictitle1">Why Is Redisson Distributed Lock Not Supported by DCS Proxy Cluster Redis 3.0 Instances?</h1>
<div id="body1596093268950"><p id="dcs-faq-0730025__en-us_topic_0152099097_p227692415350">Redisson implements lock acquisition and unlocking in the following process:</p>
<ol id="dcs-faq-0730025__en-us_topic_0152099097_ol106890279329"><li id="dcs-faq-0730025__en-us_topic_0152099097_li10690122714325">Redisson lock acquisition and unlocking are implemented by running Lua scripts.</li><li id="dcs-faq-0730025__en-us_topic_0152099097_li13690527103212">During lock acquisition, the <strong id="dcs-faq-0730025__b973819493115">EXISTS</strong>, <strong id="dcs-faq-0730025__b147431491411">HSET</strong>, <strong id="dcs-faq-0730025__b1474319496118">PEXPIRE</strong>, <strong id="dcs-faq-0730025__b574324919119">HEXISTS</strong>, <strong id="dcs-faq-0730025__b18743649813">HINCRBY</strong>, <strong id="dcs-faq-0730025__b37431549912">PEXPIRE</strong>, and <strong id="dcs-faq-0730025__b17441491117">PTTL</strong> commands must be executed in the Lua script.</li><li id="dcs-faq-0730025__en-us_topic_0152099097_li126904275320">During unlocking, the <strong id="dcs-faq-0730025__b6722145010113">EXISTS</strong>, <strong id="dcs-faq-0730025__b472325014114">PUBLISH</strong>, <strong id="dcs-faq-0730025__b1072320501312">HEXISTS</strong>, <strong id="dcs-faq-0730025__b1172313502117">PEXIPRE</strong>, and <strong id="dcs-faq-0730025__b47231850311">DEL</strong> commands must be executed in the Lua script.</li></ol>
<ol id="dcs-faq-0730025__en-us_topic_0152099097_ol106890279329"><li id="dcs-faq-0730025__en-us_topic_0152099097_li10690122714325">Redisson lock acquisition and unlocking are implemented by running Lua scripts.</li><li id="dcs-faq-0730025__en-us_topic_0152099097_li13690527103212">During lock acquisition, the <strong id="dcs-faq-0730025__b973819493115">EXISTS</strong>, <strong id="dcs-faq-0730025__b147431491411">HSET</strong>, <strong id="dcs-faq-0730025__b1474319496118">PEXPIRE</strong>, <strong id="dcs-faq-0730025__b574324919119">HEXISTS</strong>, <strong id="dcs-faq-0730025__b18743649813">HINCRBY</strong>, <strong id="dcs-faq-0730025__b37431549912">PEXPIRE</strong>, and <strong id="dcs-faq-0730025__b17441491117">PTTL</strong> commands must be executed in the Lua script.</li><li id="dcs-faq-0730025__en-us_topic_0152099097_li126904275320">During unlocking, the <strong id="dcs-faq-0730025__b6722145010113">EXISTS</strong>, <strong id="dcs-faq-0730025__b472325014114">PUBLISH</strong>, <strong id="dcs-faq-0730025__b1072320501312">HEXISTS</strong>, <strong id="dcs-faq-0730025__b1172313502117">PEXPIRE</strong>, and <strong id="dcs-faq-0730025__b47231850311">DEL</strong> commands must be executed in the Lua script.</li></ol>
<p id="dcs-faq-0730025__en-us_topic_0152099097_p82082536353">In a proxy-based cluster, the proxy processes <strong id="dcs-faq-0730025__b86291151212">PUBLISH</strong> and <strong id="dcs-faq-0730025__b5629135120111">SUBSCRIBE</strong> commands and forwards requests to the Redis server. The <strong id="dcs-faq-0730025__b146301851418">PUBLISH</strong> command cannot be executed in the Lua script.</p>
<p id="dcs-faq-0730025__en-us_topic_0152099097_p10806319113210">As a result, Proxy Cluster DCS Redis 3.0 instances do not support Redisson distributed locks. To use Redisson, resort to Redis 4.0 or 5.0 instead.</p>
</div>

2
docs/dcs/umn/dcs-faq-0730029.html
View File

@ -2,7 +2,7 @@
<h1 class="topictitle1">Does DCS Support Cross-AZ Deployment?</h1>
<div id="body1596093268950"><p id="dcs-faq-0730029__p15277568910">Master/Standby and cluster DCS Redis instances can be deployed across availability zones (AZs).</p>
<ul id="dcs-faq-0730029__en-us_topic_0152099097_ul1253034413517"><li id="dcs-faq-0730029__en-us_topic_0152099097_li35311444514">If instances nodes in an AZ are faulty, nodes in other AZs will not be affected. The standby node automatically becomes the master node to continue to operate, ensuring disaster recovery (DR).</li><li id="dcs-faq-0730029__en-us_topic_0152099097_li7539944115110">Cross-AZ deployment does not compromise the speed of data synchronization between the master and standby nodes.</li></ul>
<ul id="dcs-faq-0730029__en-us_topic_0152099097_ul1253034413517"><li id="dcs-faq-0730029__en-us_topic_0152099097_li35311444514">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).</li><li id="dcs-faq-0730029__en-us_topic_0152099097_li7539944115110">Cross-AZ deployment does not compromise the speed of data synchronization between the master and standby nodes.</li></ul>
</div>
<div>
<div class="familylinks">

2
docs/dcs/umn/dcs-faq-0730036.html
View File

@ -5,7 +5,7 @@
<ul id="dcs-faq-0730036__ul5345182618333"><li id="dcs-faq-0730036__li1345132623311">Redis 3.0<p id="dcs-faq-0730036__p10964478357"><a name="dcs-faq-0730036__li1345132623311"></a><a name="li1345132623311"></a>Data of a DCS Redis 3.0 instance cannot be cleared on the console, and can only be cleared by the <strong id="dcs-faq-0730036__b689814018266">FLUSHDB</strong> or <strong id="dcs-faq-0730036__b3166163914269">FLUSHALL</strong> command in redis-cli.</p>
<p id="dcs-faq-0730036__p8472203333612">Run the <strong id="dcs-faq-0730036__b13145640878138">FLUSHALL</strong> command to clear all the data in the instance.</p>
<p id="dcs-faq-0730036__p647293333619">Run the <strong id="dcs-faq-0730036__b12348169898138">FLUSHDB</strong> command to clear the data in the currently selected DB.</p>
</li><li id="dcs-faq-0730036__li18813103819364">Redis 4.0 and later<p id="dcs-faq-0730036__p1515135633616"><a name="dcs-faq-0730036__li18813103819364"></a><a name="li18813103819364"></a>To clear data of a DCS Redis 4.0 and later instance, you can run the <strong id="dcs-faq-0730036__b3485143010548">FLUSHDB</strong> or <strong id="dcs-faq-0730036__b124911430165419">FLUSHALL</strong> command in redis-cli, use the data clearing function on the DCS console, or run the <strong id="dcs-faq-0730036__b1676102514715">FLUSHDB</strong> command on Web CLI.</p>
</li><li id="dcs-faq-0730036__li18813103819364">Redis 4.0 and later<p id="dcs-faq-0730036__p1515135633616"><a name="dcs-faq-0730036__li18813103819364"></a><a name="li18813103819364"></a>To clear data of a DCS Redis 4.0 and later instance, you can run the <strong id="dcs-faq-0730036__b19434487295">FLUSHDB</strong> or <strong id="dcs-faq-0730036__b0434787291">FLUSHALL</strong> command in redis-cli, use the data clearing function on the DCS console, or run the <strong id="dcs-faq-0730036__b1343411815297">FLUSHDB</strong> command on Web CLI.</p>
<p id="dcs-faq-0730036__p963916114382">To clear data of a Redis Cluster instance, run the <strong id="dcs-faq-0730036__b9521924153015">FLUSHDB</strong> or <strong id="dcs-faq-0730036__b431212296307">FLUSHALL</strong> command on every shard of the instance. Otherwise, data may not be completely cleared.</p>
<div class="note" id="dcs-faq-0730036__note168212515318"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="dcs-faq-0730036__ul191791322143115"><li id="dcs-faq-0730036__li111791022143119">Currently, only DCS Redis 4.0 and later instances support data clearing by using the DCS console and by running the <strong id="dcs-faq-0730036__b263057135217">FLUSHDB</strong> command on Web CLI.</li><li id="dcs-faq-0730036__li13479118163312">When you run the <strong id="dcs-faq-0730036__b1741316535415">FLUSHDB</strong> command on Web CLI, only one shard is cleared at a time. If there are multiple shards, connect to the master node of each shard and run the <strong id="dcs-faq-0730036__b174141653154116">FLUSHDB</strong> command separately.</li><li id="dcs-faq-0730036__li1079819242316">Redis Cluster data cannot be cleared by using Web CLI.</li></ul>
</div></div>

4
docs/dcs/umn/dcs-faq-0730053.html
View File

@ -6,8 +6,8 @@
<div class="note" id="dcs-faq-0730053__note16381317154011"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="dcs-faq-0730053__p11207233113316">If your DCS instances were created a long time ago, the versions of these instances may not be advanced enough to support some new functions (such as backup and restoration). You can contact technical support to upgrade your DCS instances. After the upgrade, you can back up and restore your instances.</p>
</div></div>
</li><li id="dcs-faq-0730053__li3717203812310">For single-node instances:<p id="dcs-faq-0730053__p1483512383277"><a name="dcs-faq-0730053__li3717203812310"></a><a name="li3717203812310"></a>Single-node instances do not support the backup function. You can use redis-cli to export RDB files. This operation depends on <strong id="dcs-faq-0730053__b1633103315364">SYNC</strong> command.</p>
<ul id="dcs-faq-0730053__ul5358144153214"><li id="dcs-faq-0730053__li10301124213323">If the instance allows the <strong id="dcs-faq-0730053__b3451191011386">SYNC</strong> command (such as a Redis 3.0 single-node instance), run the following command to export the instance data:<p id="dcs-faq-0730053__p6257123652712"><strong id="dcs-faq-0730053__b12571336122715">redis-cli -h {source_redis_address} -p 6379 [-a password] --rdb {output.rdb}</strong></p>
</li><li id="dcs-faq-0730053__li104941949133213">If the instance does not allow the <strong id="dcs-faq-0730053__b773324217387">SYNC</strong> command (such as a Redis 4.0 or 5.0 single-node instance), migrate the instance data to a master/standby instance and export the data by using the backup function.</li></ul>
<ul id="dcs-faq-0730053__ul5358144153214"><li id="dcs-faq-0730053__li10301124213323">If the instance allows the <strong id="dcs-faq-0730053__b78591842102913">SYNC</strong> command (such as a Redis 3.0 single-node instance), run the following command to export the instance data:<p id="dcs-faq-0730053__p6257123652712"><strong id="dcs-faq-0730053__b12571336122715">redis-cli -h {source_redis_address} -p 6379 [-a password] --rdb {output.rdb}</strong></p>
</li><li id="dcs-faq-0730053__li104941949133213">If the instance does not allow the <strong id="dcs-faq-0730053__b1847734562916">SYNC</strong> command (such as a Redis 4.0 or 5.0 single-node instance), migrate the instance data to a master/standby instance and export the data by using the backup function.</li></ul>
</li></ul>
</div>
<div>

2
docs/dcs/umn/dcs-faq-210531002.html
View File

@ -9,6 +9,8 @@
</div>
<div class="section" id="dcs-faq-210531002__en-us_topic_0000001152183926_section454735651113"><h4 class="sectiontitle">Solutions</h4><ul id="dcs-faq-210531002__en-us_topic_0000001152183926_ul9145171671310"><li id="dcs-faq-210531002__en-us_topic_0000001152183926_li1948913317134">Configure scheduled hot key analysis tasks by referring to <a href="dcs-ug-190808001.html#dcs-ug-190808001__section47852016145218">Hot Key Analysis</a>, or use the <strong id="dcs-faq-210531002__en-us_topic_0000001152183926_b1067355655613">SCAN</strong> command to traverse all keys on a scheduled basis and remove expired keys from the memory.</li><li id="dcs-faq-210531002__en-us_topic_0000001152183926_li19583910191613">Configure a scheduled task to scan all master nodes of the instance. All keys will be scanned, and Redis will determine whether the keys have expired. Expired keys will be released. For details, see <a href="dcs-ug-210330002.html">Scanning Expired Keys</a>.</li></ul>
</div>
<div class="section" id="dcs-faq-210531002__en-us_topic_0000001152183926_section13981316163316"><h4 class="sectiontitle">How Do I Know Which Expired Keys Have Been Deleted?</h4><p id="dcs-faq-210531002__en-us_topic_0000001152183926_p13848148153312">Deleted expired keys cannot be queried.</p>
</div>
</div>
<div>
<div class="familylinks">

4
docs/dcs/umn/dcs-faq-210706001.html
View File

@ -2,9 +2,9 @@
<h1 class="topictitle1">When Will AOF Rewrites Be Triggered?</h1>
<div id="body8662426"><p id="dcs-faq-210706001__en-us_topic_0000001152024158_p54524461314">AOF rewrites involve the following concepts:</p>
<ul id="dcs-faq-210706001__en-us_topic_0000001152024158_ul146702431769"><li id="dcs-faq-210706001__en-us_topic_0000001152024158_li156702431965">Rewrite window, which is currently 01:00 to 04:59</li><li id="dcs-faq-210706001__en-us_topic_0000001152024158_li1328112522188">Disk usage threshold, which is 50%</li></ul>
<ul id="dcs-faq-210706001__en-us_topic_0000001152024158_ul146702431769"><li id="dcs-faq-210706001__en-us_topic_0000001152024158_li156702431965">Rewrite window, which is currently 01:00 to 04:59</li><li id="dcs-faq-210706001__en-us_topic_0000001152024158_li1328112522188">Disk usage threshold, which is 50%</li><li id="dcs-faq-210706001__en-us_topic_0000001152024158_li163198143256">Dataset memory, which is the percentage of memory that Redis dataset has used.</li></ul>
<p id="dcs-faq-210706001__en-us_topic_0000001152024158_p175619556184">AOF rewrites are triggered in the following scenarios:</p>
<ul id="dcs-faq-210706001__en-us_topic_0000001152024158_ul51511214141918"><li id="dcs-faq-210706001__en-us_topic_0000001152024158_li13729184517211">If the disk usage reaches the threshold (regardless of whether the current time is within the rewrite window), rewrites will be triggered on instances whose AOF file size is larger than the memory dataset size.</li><li id="dcs-faq-210706001__en-us_topic_0000001152024158_li773024516219">If the disk usage is below the threshold and the current time is within the rewrite window, rewrites will be triggered on instances whose AOF file size is larger than the dataset memory multiplied by 1.5.</li><li id="dcs-faq-210706001__en-us_topic_0000001152024158_li13730445122110">If the disk usage is below the threshold but the current time is out of the rewrite window, rewrites will be triggered on instances whose AOF file size is larger than the maximum memory multiplied by 4.5.</li></ul>
<ul id="dcs-faq-210706001__en-us_topic_0000001152024158_ul57261618134519"><li id="dcs-faq-210706001__en-us_topic_0000001152024158_li20726171812452">If the disk usage reaches the threshold (regardless of whether the current time is within the rewrite window), rewrites will be triggered on instances whose AOF file size is larger than the dataset memory.</li><li id="dcs-faq-210706001__en-us_topic_0000001152024158_li12726141814511">If the disk usage is below the threshold and the current time is within the rewrite window, rewrites will be triggered on instances whose AOF file size is larger than the dataset memory multiplied by 1.5.</li><li id="dcs-faq-210706001__en-us_topic_0000001152024158_li17261018174510">If the disk usage is below the threshold but the current time is out of the rewrite window, rewrites will be triggered on instances whose AOF file size is larger than the instance's maximum memory multiplied by 4.5.</li></ul>
</div>
<div>
<div class="familylinks">

4
docs/dcs/umn/dcs-faq-221222.html
View File

@ -2,9 +2,9 @@
<h1 class="topictitle1">Is the Read-only Address of a Master/Standby Instance Connected to the Master or Standby Node?</h1>
<div id="body8662426"><p id="dcs-faq-221222__en-us_topic_0000001431664584_p8060118">A master/standby DCS Redis 4.0/5.0/6.0 instance has a <strong id="dcs-faq-221222__en-us_topic_0000001431664584_b8927124911157">Connection Address</strong> and a <strong id="dcs-faq-221222__en-us_topic_0000001431664584_b1927124921519">Read-only Address</strong>. 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.</p>
<p id="dcs-faq-221222__en-us_topic_0000001431664584_p99251850144516">For details, see <a href="CacheMasterSlave.html#CacheMasterSlave__section5805185095215">architecture of Master/Standby DCS Redis 4.0/5.0/6.0 Instances</a>.</p>
<p id="dcs-faq-221222__en-us_topic_0000001431664584_p99251850144516">For details, see <a href="CacheMasterSlave.html#CacheMasterSlave__section5805185095215">Architecture of Master/Standby DCS Redis 4.0/5.0/6.0 Instances</a>.</p>
<div class="fignone" id="dcs-faq-221222__en-us_topic_0000001431664584_fig1636541875315"><span class="figcap"><b>Figure 1 </b>Instance addresses</span><br><span><img id="dcs-faq-221222__en-us_topic_0000001431664584_image336621810537" src="en-us_image_0000001431665772.png"></span></div>
<p id="dcs-faq-221222__en-us_topic_0000001431664584_p4769144185313"></p>
<p id="dcs-faq-221222__en-us_topic_0000001431664584_p4769144185313">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.</p>
</div>
<div>
<div class="familylinks">

14
docs/dcs/umn/dcs-migrate-0220411.html
View File

@ -20,8 +20,8 @@ sudo systemctl enable nginx.service</pre>
vi nginx.conf</pre>
</li><li id="dcs-migrate-0220411__li06401357104818">Example forwarding configuration:<pre class="screen" id="dcs-migrate-0220411__screen34331446184818">stream {
server {
listen <em id="dcs-migrate-0220411__i12180154014492">6379</em>;
proxy_pass <em id="dcs-migrate-0220411__i820217582526">{source_instance_address}</em>:<em id="dcs-migrate-0220411__i430001812532">{port}</em>;
listen 6379;
proxy_pass {source_instance_address}:{port};
}
}</pre>
<p id="dcs-migrate-0220411__p232810156114"><strong id="dcs-migrate-0220411__b17662158131214">6379</strong> is the listening port of the source forwarding server. <em id="dcs-migrate-0220411__i437151691218">{source_instance_address}</em> and <em id="dcs-migrate-0220411__i18885102313128">{port}</em> are the connection address and port of the source Redis instance.</p>
@ -29,7 +29,7 @@ vi nginx.conf</pre>
<p id="dcs-migrate-0220411__p0452103812178">This configuration must be added exactly where it is shown in the following figure.</p>
<div class="fignone" id="dcs-migrate-0220411__fig42351341142517"><span class="figcap"><b>Figure 2 </b>Configuration location</span><br><span><img id="dcs-migrate-0220411__image162354412253" src="en-us_image_0000001299155037.png"></span></div>
</li><li id="dcs-migrate-0220411__li1416762953011">Restart Nginx.<pre class="screen" id="dcs-migrate-0220411__screen182391643118">service nginx restart</pre>
</li><li id="dcs-migrate-0220411__li1334411452304">Verify whether Nginx has been started.<pre class="screen" id="dcs-migrate-0220411__screen366531193118">netstat -an|grep <em id="dcs-migrate-0220411__i14356146171516">6379</em></pre>
</li><li id="dcs-migrate-0220411__li1334411452304">Verify whether Nginx has been started.<pre class="screen" id="dcs-migrate-0220411__screen366531193118">netstat -an|grep 6379</pre>
<p id="dcs-migrate-0220411__p593853532713">If the port is being listened, Nginx has been started successfully.</p>
<div class="fignone" id="dcs-migrate-0220411__fig15433124613489"><span class="figcap"><b>Figure 3 </b>Verification result</span><br><span><img id="dcs-migrate-0220411__image1243324614819" src="en-us_image_0000001299513869.png"></span></div>
</li></ol>
@ -37,8 +37,8 @@ vi nginx.conf</pre>
<p id="dcs-migrate-0220411__p951915610209"><strong id="dcs-migrate-0220411__b156351631173618">vi nginx.conf</strong></p>
</li><li id="dcs-migrate-0220411__li28611116103716">Configuration example:<pre class="screen" id="dcs-migrate-0220411__screen1418219241098">stream {
server {
listen <em id="dcs-migrate-0220411__i026722419197">6666</em>;
proxy_pass <em id="dcs-migrate-0220411__i12154114378">{source_ecs_address}</em>:<em id="dcs-migrate-0220411__i64199430315">6379</em>;
listen 6666;
proxy_pass {source_ecs_address}:6379;
}
}</pre>
<p id="dcs-migrate-0220411__p52110532392"><strong id="dcs-migrate-0220411__b1624173815217">6666</strong> is ECS's listening port, <em id="dcs-migrate-0220411__i216411091914">{source_ecs_address}</em> is the public IP address of the source forwarding server, and <strong id="dcs-migrate-0220411__b1672424382111">6379</strong> is the listening port of the source forwarding server Nginx.</p>
@ -46,11 +46,11 @@ vi nginx.conf</pre>
<p id="dcs-migrate-0220411__p15629194810343">This configuration must be added exactly where it is shown in the following figure.</p>
<div class="fignone" id="dcs-migrate-0220411__fig262974853410"><span class="figcap"><b>Figure 4 </b>Configuration location</span><br><span><img id="dcs-migrate-0220411__image76291748143412" src="en-us_image_0000001299274493.png"></span></div>
</li><li id="dcs-migrate-0220411__li11629448133418">Restart Nginx.<pre class="screen" id="dcs-migrate-0220411__screen5629154873411">service nginx restart</pre>
</li><li id="dcs-migrate-0220411__li7629248173410">Verify whether Nginx has been started.<pre class="screen" id="dcs-migrate-0220411__screen1562954833418">netstat -an|grep <em id="dcs-migrate-0220411__i2012245400">6</em><em id="dcs-migrate-0220411__i1921724194014">666</em></pre>
</li><li id="dcs-migrate-0220411__li7629248173410">Verify whether Nginx has been started.<pre class="screen" id="dcs-migrate-0220411__screen1562954833418">netstat -an|grep 6666</pre>
<p id="dcs-migrate-0220411__p1459184772816">If the port is being listened, Nginx has been started successfully.</p>
<div class="fignone" id="dcs-migrate-0220411__fig52972206350"><span class="figcap"><b>Figure 5 </b>Verification result</span><br><span><img id="dcs-migrate-0220411__image1129752063519" src="en-us_image_0000001299354449.png"></span></div>
</li></ol>
</p></li><li id="dcs-migrate-0220411__li1629316143413"><span>Run the following command on the ECS to test the network connection of port 6666:</span><p><pre class="screen" id="dcs-migrate-0220411__screen1993319292420">redis-cli -h <em id="dcs-migrate-0220411__i66898101201">{target_ecs_address} </em>-p <em id="dcs-migrate-0220411__i718313304597">6666</em> -a <em id="dcs-migrate-0220411__i158914352597">{password}</em></pre>
</p></li><li id="dcs-migrate-0220411__li1629316143413"><span>Run the following command on the ECS to test the network connection of port 6666:</span><p><pre class="screen" id="dcs-migrate-0220411__screen9189230121519">redis-cli -h {target_ecs_address} -p 6666 -a {password}</pre>
<p id="dcs-migrate-0220411__p16330112132510"><em id="dcs-migrate-0220411__i132590214215">{target_ecs_address}</em> is the EIP of the ECS, <strong id="dcs-migrate-0220411__b1927283314218">6666</strong> is the listening port of the ECS, and <em id="dcs-migrate-0220411__i254115492111">{password}</em> is the source Redis password. If there is no password, leave it blank.</p>
<div class="fignone" id="dcs-migrate-0220411__fig1168715172413"><span class="figcap"><b>Figure 6 </b>Connection example</span><br><span><img id="dcs-migrate-0220411__image446672703311" src="en-us_image_0000001252915210.png"></span></div>
</p></li><li id="dcs-migrate-0220411__li13564181913214"><span>Prepare the migration tool redis-shake.</span><p><ol type="a" id="dcs-migrate-0220411__ol0483154263117"><li id="dcs-migrate-0220411__li630814352317">Log in to the ECS.</li><li id="dcs-migrate-0220411__li15905189153217">Download redis-shake. Version 2.0.3 is used as an example. You can use <a href="https://github.com/alibaba/RedisShake/releases" target="_blank" rel="noopener noreferrer">other redis-shake versions</a> as required.<pre class="screen" id="dcs-migrate-0220411__screen195204110481">wget https://github.com/tair-opensource/RedisShake/releases/download/release-v2.0.3-20200724/redis-shake-v2.0.3.tar.gz</pre>

13
docs/dcs/umn/dcs-migrate-1117003.html
View File

@ -4,7 +4,6 @@
<div id="body1605698129613"><p id="dcs-migrate-1117003__p783020494275">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.</p>
<p id="dcs-migrate-1117003__dcs-migrate-demo02_p1814154103513">The following describes how to use redis-shake for backup migration to a DCS Redis Cluster instance.</p>
<div class="section" id="dcs-migrate-1117003__dcs-migrate-demo02_section2230197183316"><h4 class="sectiontitle">Importing Backup Files</h4><p id="dcs-migrate-1117003__dcs-migrate-demo02_p1897312853312">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.</p>
<p id="dcs-migrate-1117003__dcs-migrate-demo02_p1937501419433"></p>
<ol id="dcs-migrate-1117003__dcs-migrate-demo02_ol082075784215"><li id="dcs-migrate-1117003__dcs-migrate-demo02_li18820145718421">Create a Redis Cluster instance on the DCS console.<p id="dcs-migrate-1117003__dcs-migrate-demo02_p17820457194216"><a name="dcs-migrate-1117003__dcs-migrate-demo02_li18820145718421"></a><a name="dcs-migrate-demo02_li18820145718421"></a>The memory of this instance cannot be smaller than that of the source Redis.</p>
</li><li id="dcs-migrate-1117003__dcs-migrate-demo02_li104985015119">Run the following command to obtain the IP addresses and port numbers of all masters of the source Redis and target Redis:<p id="dcs-migrate-1117003__dcs-migrate-demo02_p522517529213"><a name="dcs-migrate-1117003__dcs-migrate-demo02_li104985015119"></a><a name="dcs-migrate-demo02_li104985015119"></a><strong id="dcs-migrate-1117003__dcs-migrate-demo02_b15225175214219">redis-cli -h <em id="dcs-migrate-1117003__dcs-migrate-demo02_i1422585211213">{redis_address}</em> -p <em id="dcs-migrate-1117003__dcs-migrate-demo02_i1722525219212">{redis_port}</em> -a <em id="dcs-migrate-1117003__dcs-migrate-demo02_i1022516521523">{redis_password}</em> cluster nodes</strong></p>
<p id="dcs-migrate-1117003__dcs-migrate-demo02_p6225352528">In the command output similar to the following, obtain the IP addresses and ports of all masters.</p>
@ -19,20 +18,22 @@
</div></div>
</li><li id="dcs-migrate-1117003__dcs-migrate-demo02_li31771323165319">Export the RDB file.<ul id="dcs-migrate-1117003__dcs-migrate-demo02_ul181391212136"><li id="dcs-migrate-1117003__dcs-migrate-demo02_li5813141221318">Edit the <strong id="dcs-migrate-1117003__b197048921212">redis-shake.conf</strong> file by providing the following information about all the masters of both the source and the target:<pre class="screen" id="dcs-migrate-1117003__dcs-migrate-demo02_screen1248155110107">source.type = cluster
# If there is no password, skip the following parameter.
source.password_raw = <strong id="dcs-migrate-1117003__dcs-migrate-demo02_b12493515105"><em id="dcs-migrate-1117003__dcs-migrate-demo02_i1649105191015">{source_redis_password} </em></strong>
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 = <strong id="dcs-migrate-1117003__dcs-migrate-demo02_b184991236999"><em id="dcs-migrate-1117003__i194973362916">{master1_ip}:{master1_port};{master2_ip}:{master2_port}</em>...<em id="dcs-migrate-1117003__i1749817361897">{masterN_ip}:{masterN_port}</em></strong></pre>
source.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}…{masterN_ip}:{masterN_port}</pre>
</li><li id="dcs-migrate-1117003__dcs-migrate-demo02_li8813201217136">Run the following command to export the RDB file:<p id="dcs-migrate-1117003__dcs-migrate-demo02_p331212346137"><a name="dcs-migrate-1117003__dcs-migrate-demo02_li8813201217136"></a><a name="dcs-migrate-demo02_li8813201217136"></a><strong id="dcs-migrate-1117003__dcs-migrate-demo02_b1931273412131">./redis-shake -type dump -conf redis-shake.conf</strong></p>
<p id="dcs-migrate-1117003__dcs-migrate-demo02_p0312193411319">If the following information is displayed in the execution log, the backup file is exported successfully:</p>
<pre class="screen" id="dcs-migrate-1117003__dcs-migrate-demo02_screen5845144815132">execute runner[*run.CmdDump] finished!</pre>
<div class="note" id="dcs-migrate-1117003__note123524443215"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="dcs-migrate-1117003__p14352184452118">If you cannot export the source Redis backup files using this method due to cloud vendors' restrictions on the <strong id="dcs-migrate-1117003__b159737194296">SYNC</strong> and <strong id="dcs-migrate-1117003__b1864462218292">PSYNC</strong> commands, export the files on the source console or contact the source technical support.</p>
</div></div>
</li></ul>
</li><li id="dcs-migrate-1117003__dcs-migrate-demo02_li2088910245149">Import the RDB file.<ol type="a" id="dcs-migrate-1117003__dcs-migrate-demo02_ol2327112018216"><li id="dcs-migrate-1117003__dcs-migrate-demo02_li6327192011215">Import the RDB file (or files) to the cloud server. The cloud server must be connected to the target DCS instance.</li><li id="dcs-migrate-1117003__dcs-migrate-demo02_li832782018219">Edit the redis-shake configuration file.<div class="p" id="dcs-migrate-1117003__dcs-migrate-demo02_p1825892672116"><a name="dcs-migrate-1117003__dcs-migrate-demo02_li832782018219"></a><a name="dcs-migrate-demo02_li832782018219"></a>Edit the <strong id="dcs-migrate-1117003__b19204181619121">redis-shake.conf</strong> file by providing the following information about all the masters of both the source and the target:<pre class="screen" id="dcs-migrate-1117003__dcs-migrate-demo02_screen1882155716429">target.type = cluster
# If there is no password, skip the following parameter.
target.password_raw = <strong id="dcs-migrate-1117003__dcs-migrate-demo02_b4822857164211"><em id="dcs-migrate-1117003__dcs-migrate-demo02_i16822145784210">{target_redis_password} </em></strong>
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 = <strong id="dcs-migrate-1117003__dcs-migrate-demo02_b143109517118"><em id="dcs-migrate-1117003__i143094551116">{master1_ip}:{master1_port};{master2_ip}:{master2_port}</em>...<em id="dcs-migrate-1117003__i193092518113">{masterN_ip}:{masterN_port}</em></strong>
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 = <strong id="dcs-migrate-1117003__dcs-migrate-demo02_b193601012192017"><em id="dcs-migrate-1117003__dcs-migrate-demo02_i3201811112014">local_dump.0</em></strong><strong id="dcs-migrate-1117003__dcs-migrate-demo02_b2029282072015"><em id="dcs-migrate-1117003__dcs-migrate-demo02_i139757192201">;local_dump.1;local_dump.2;local_dump.3</em></strong></pre>
rdb.input = {local_dump.0};{local_dump.1};{local_dump.2};{local_dump.3}</pre>
</div>
<p id="dcs-migrate-1117003__dcs-migrate-demo02_p2840103122112">Save and exit.</p>
</li><li id="dcs-migrate-1117003__dcs-migrate-demo02_li1132710201214">Run the following command to import the RDB file to the target instance:<p id="dcs-migrate-1117003__dcs-migrate-demo02_p592783512112"><a name="dcs-migrate-1117003__dcs-migrate-demo02_li1132710201214"></a><a name="dcs-migrate-demo02_li1132710201214"></a><strong id="dcs-migrate-1117003__dcs-migrate-demo02_b89111406213">./redis-shake -type restore -conf redis-shake.conf</strong></p>

18
docs/dcs/umn/dcs-migrate-demo02.html
View File

@ -19,14 +19,14 @@
</li><li id="dcs-migrate-demo02__li984815114135">Edit the redis-shake configuration file.<p id="dcs-migrate-demo02__p165301315101"><a name="dcs-migrate-demo02__li984815114135"></a><a name="li984815114135"></a>Edit the <strong id="dcs-migrate-demo02__b15129291552">redis-shake.conf</strong> file by providing the following information about all the masters of both the source and the target:</p>
<pre class="screen" id="dcs-migrate-demo02__screen24734391550">source.type = cluster
# If there is no password, skip the following parameter.
source.password_raw = <strong id="dcs-migrate-demo02__b1650010390558"><em id="dcs-migrate-demo02__i3500103911558">{source_redis_password} </em></strong>
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 = <strong id="dcs-migrate-demo02__b550010391559"><em id="dcs-migrate-demo02__i115001939135513">{master1_ip}:{master1_port};{master2_ip}:{master2_port}</em>...<em id="dcs-migrate-demo02__i18500139115514">{masterN_ip}:{masterN_port}</em></strong>
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 = <strong id="dcs-migrate-demo02__b1950010392559"><em id="dcs-migrate-demo02__i1650063919551">{target_redis_password} </em></strong>
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 = <strong id="dcs-migrate-demo02__b45561343346"><em id="dcs-migrate-demo02__i75558417341">{master1_ip}:{master1_port};{master2_ip}:{master2_port}</em>...<em id="dcs-migrate-demo02__i1955610443419">{masterN_ip}:{masterN_port}</em></strong></pre>
target.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}…{masterN_ip}:{masterN_port}</pre>
<p id="dcs-migrate-demo02__p253913201019">Save and exit.</p>
</li><li id="dcs-migrate-demo02__li13477121417134">Migrate data online.<p id="dcs-migrate-demo02__p133087271005"><a name="dcs-migrate-demo02__li13477121417134"></a><a name="li13477121417134"></a>Run the following command to synchronize data between the source and the target Redis:</p>
<p id="dcs-migrate-demo02__p830810272002"><strong id="dcs-migrate-demo02__b03085277020">./redis-shake -type sync -conf redis-shake.conf</strong></p>
@ -55,20 +55,20 @@ target.address = <strong id="dcs-migrate-demo02__b45561343346"><em id="dcs-migra
</div></div>
</li><li id="dcs-migrate-demo02__li31771323165319">Export the RDB file.<ul id="dcs-migrate-demo02__ul181391212136"><li id="dcs-migrate-demo02__li5813141221318">Edit the <strong id="dcs-migrate-demo02__b165661730896">redis-shake.conf</strong> file by providing the following information about all the masters of both the source and the target:<pre class="screen" id="dcs-migrate-demo02__screen1248155110107">source.type = cluster
# If there is no password, skip the following parameter.
source.password_raw = <strong id="dcs-migrate-demo02__b12493515105"><em id="dcs-migrate-demo02__i1649105191015">{source_redis_password} </em></strong>
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 = <strong id="dcs-migrate-demo02__b184991236999"><em id="dcs-migrate-demo02__i194973362916">{master1_ip}:{master1_port};{master2_ip}:{master2_port}</em>...<em id="dcs-migrate-demo02__i1749817361897">{masterN_ip}:{masterN_port}</em></strong></pre>
source.address = {master1_ip}:{master1_port};{master2_ip}:{master2_port}…{masterN_ip}:{masterN_port}</pre>
</li><li id="dcs-migrate-demo02__li8813201217136">Run the following command to export the RDB file:<p id="dcs-migrate-demo02__p331212346137"><a name="dcs-migrate-demo02__li8813201217136"></a><a name="li8813201217136"></a><strong id="dcs-migrate-demo02__b1931273412131">./redis-shake -type dump -conf redis-shake.conf</strong></p>
<p id="dcs-migrate-demo02__p0312193411319">If the following information is displayed in the execution log, the backup file is exported successfully:</p>
<pre class="screen" id="dcs-migrate-demo02__screen5845144815132">execute runner[*run.CmdDump] finished!</pre>
</li></ul>
</li><li id="dcs-migrate-demo02__li2088910245149">Import the RDB file.<ol type="a" id="dcs-migrate-demo02__ol2327112018216"><li id="dcs-migrate-demo02__li6327192011215">Import the RDB file (or files) to the cloud server. The cloud server must be connected to the target DCS instance.</li><li id="dcs-migrate-demo02__li832782018219">Edit the redis-shake configuration file.<div class="p" id="dcs-migrate-demo02__p1825892672116"><a name="dcs-migrate-demo02__li832782018219"></a><a name="li832782018219"></a>Edit the <strong id="dcs-migrate-demo02__b5238125171018">redis-shake.conf</strong> file by providing the following information about all the masters of both the source and the target:<pre class="screen" id="dcs-migrate-demo02__screen1882155716429">target.type = cluster
# If there is no password, skip the following parameter.
target.password_raw = <strong id="dcs-migrate-demo02__b4822857164211"><em id="dcs-migrate-demo02__i16822145784210">{target_redis_password} </em></strong>
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 = <strong id="dcs-migrate-demo02__b143109517118"><em id="dcs-migrate-demo02__i143094551116">{master1_ip}:{master1_port};{master2_ip}:{master2_port}</em>...<em id="dcs-migrate-demo02__i193092518113">{masterN_ip}:{masterN_port}</em></strong>
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 = <strong id="dcs-migrate-demo02__b193601012192017"><em id="dcs-migrate-demo02__i3201811112014">local_dump.0</em></strong><strong id="dcs-migrate-demo02__b2029282072015"><em id="dcs-migrate-demo02__i139757192201">;local_dump.1;local_dump.2;local_dump.3</em></strong></pre>
rdb.input = {local_dump.0};{local_dump.1};{local_dump.2};{local_dump.3}</pre>
</div>
<p id="dcs-migrate-demo02__p2840103122112">Save and exit.</p>
</li><li id="dcs-migrate-demo02__li1132710201214">Run the following command to import the RDB file to the target instance:<p id="dcs-migrate-demo02__p592783512112"><a name="dcs-migrate-demo02__li1132710201214"></a><a name="li1132710201214"></a><strong id="dcs-migrate-demo02__b89111406213">./redis-shake -type restore -conf redis-shake.conf</strong></p>

4
docs/dcs/umn/dcs-migration-0312004.html
View File

@ -20,9 +20,9 @@
</li><li id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_li11225208162112">Install OBS Browser+.<p id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_p1022518842111"><a name="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_li11225208162112"></a><a name="dcs-migration-190703002_dcs-ug-0312037_li11225208162112"></a>For details, see section "Installing OBS Browser+" in <em id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_i118557531214">Object Storage Service (OBS) Tools Guide (OBS Browser+)</em>.</p>
</li><li id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_li201961913103814">Log in to OBS Browser+.<p id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_p1119621313811"><a name="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_li201961913103814"></a><a name="dcs-migration-190703002_dcs-ug-0312037_li201961913103814"></a>For details, see section "Logging In to OBS Browser+" in <em id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_i104881711215">Object Storage Service (OBS) Tools Guide (OBS Browser+)</em>.</p>
</li><li id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_li144125145718">Create a bucket.</li><li id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li10948943114817">Upload backup data.</li></ol>
</p></li><li id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_li8307135965315"><a name="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_li8307135965315"></a><a name="dcs-migration-190703002_dcs-ug-0312037_li8307135965315"></a><span>On the OBS console, upload the backup data files to the OBS bucket.</span><p><div class="p" id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_p73071659115311">Perform the following steps if the backup file size does not exceed 5 GB:<ol type="a" id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_ol17307059105315"><li id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li11425644112117">In the bucket list, click the name of the created bucket.</li><li id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li6425134472111">In the navigation pane, choose <strong id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_b2037028687">Objects</strong>.</li><li id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li8425844162114">On the <strong id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_b2088588249">Objects</strong> tab page, click <strong id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_b1409091267">Upload Object</strong>.</li><li id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li4601227114516">Upload the objects.<p id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_p2092314104615"><a name="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li4601227114516"></a><a name="dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li4601227114516"></a>To upload objects, drag files or folders to the <strong id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_b1459915347">Upload Object</strong> area or click <strong id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_b1648442873">add file</strong>. A maximum of 100 files can be uploaded at a time. The total size cannot exceed 5 GB.</p>
</p></li><li id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_li8307135965315"><a name="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_li8307135965315"></a><a name="dcs-migration-190703002_dcs-ug-0312037_li8307135965315"></a><span>On the OBS console, upload the backup data files to the OBS bucket.</span><p><div class="p" id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_p73071659115311">Perform the following steps if the backup file size does not exceed 5 GB:<ol type="a" id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_ol17307059105315"><li id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li11425644112117">In the bucket list, click the name of the created bucket.</li><li id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li6425134472111">In the navigation pane, choose <strong id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_b7335667220">Objects</strong>.</li><li id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li8425844162114">On the <strong id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_b1434535111128">Objects</strong> tab page, click <strong id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_b8346251131216">Upload Object</strong>.</li><li id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li4601227114516">Upload the objects.<p id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_p2092314104615"><a name="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li4601227114516"></a><a name="dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li4601227114516"></a>To upload objects, drag files or folders to the <strong id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_b1466016717292">Upload Object</strong> area or click <strong id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_b13375203619291">add file</strong>. A maximum of 100 files can be uploaded at a time. The total size cannot exceed 5 GB.</p>
<div class="fignone" id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_fig184786179256"><span class="figcap"><b>Figure 1 </b>Uploading an object</span><br><span><img id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_image174788172258" src="en-us_image_0000001634759086.png"></span></div>
</li><li id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_li29854713516">(Optional) Select <strong id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_b859379742">KMS encryption</strong> to encrypt the file you want to upload.</li><li id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_li103071459205315">Click <strong id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_b2373124572710">Upload</strong>.</li></ol>
</li><li id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_li29854713516">(Optional) Select <strong id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_b418982912617">KMS encryption</strong> to encrypt the file you want to upload.</li><li id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_li103071459205315">Click <strong id="dcs-migration-0312004__dcs-migration-190703002_dcs-ug-0312037_b2373124572710">Upload</strong>.</li></ol>
</div>
</p></li></ol>
</div>

2
docs/dcs/umn/dcs-migration-0312010.html
View File

@ -18,7 +18,7 @@
<div class="note" id="dcs-migration-0312010__note22211616174320"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="dcs-migration-0312010__dcs-migration-0312012_p1922181634311">Ensure that the ECS has sufficient disk space for data file decompression, and can communicate with the DCS instance. Generally, the ECS and DCS instance are configured to belong to the same VPC and subnet, and the configured security group rules do not restrict access ports. For details about how to configure a security group, see <a href="en-us_topic_0090662012.html">Security Group Configurations</a>.</p>
</div></div>
</div>
<div class="section" id="dcs-migration-0312010__section1458283216500"><h4 class="sectiontitle">Step 3: Importing Data</h4><p id="dcs-migration-0312010__p61091244194614"><strong id="dcs-migration-0312010__b04081317175912">redis-cli -h <em id="dcs-migration-0312010__i1940751714594">{dcs_instance_address} </em>-p <em id="dcs-migration-0312010__i3408151710598">6379</em> <em id="dcs-migration-0312010__i4408171755911"> </em></strong><strong id="dcs-migration-0312010__b39958183595">-a</strong><strong id="dcs-migration-0312010__b16408181711595"><em id="dcs-migration-0312010__i540818173593"> {password} </em>--pipe &lt; appendonly.aof</strong></p>
<div class="section" id="dcs-migration-0312010__section1458283216500"><h4 class="sectiontitle">Step 3: Importing Data</h4><p id="dcs-migration-0312010__p011163204217"><strong id="dcs-migration-0312010__b278592218432">redis-cli -h {dcs_instance_address} -p <em id="dcs-migration-0312010__i1590341311434">6379</em> -a {password} --pipe &lt; appendonly.aof</strong></p>
</div>
<div class="section" id="dcs-migration-0312010__section1762337185412"><h4 class="sectiontitle">Step 4: Verifying Migration</h4><p id="dcs-migration-0312010__p279273895413">After the data is imported successfully, access the DCS instance and run the <strong id="dcs-migration-0312010__b4358102614910">info</strong> command to check whether the data has been successfully imported as required.</p>
<p id="dcs-migration-0312010__p1692631220146">If the data import fails, analyze the cause, modify the data import statement, run the <strong id="dcs-migration-0312010__b2512221013">flushall</strong> or <strong id="dcs-migration-0312010__b179081749105">flushdb</strong> command to clear the cached data in the instance, and import the data again.</p>

2
docs/dcs/umn/dcs-migration-0312019.html
View File

@ -8,7 +8,7 @@
<p id="dcs-migration-0312019__dcs-migration-0312019_0_p9601149175816">Note that:</p>
<ul id="dcs-migration-0312019__dcs-migration-0312019_0_ul03521563718"><li id="dcs-migration-0312019__dcs-migration-0312019_0_li10411423180">If different DBs in the source Redis instance contain the same keys, values of keys in the DB with the largest ID will overwrite those in the other DBs.</li><li id="dcs-migration-0312019__dcs-migration-0312019_0_li163527563717">If the source Redis instance contains multiple DBs, data is stored in the same DB after being migrated to a cluster DCS instance, and the <strong id="dcs-migration-0312019__dcs-migration-0312019_0_b997762792213">SELECT</strong> command is not supported. In this case, modify the configurations for your services.</li></ul>
</li><li id="dcs-migration-0312019__dcs-migration-0312019_0_li8481155114365">Redis Cluster instances<p id="dcs-migration-0312019__dcs-migration-0312019_0_p156281544153816"><a name="dcs-migration-0312019__dcs-migration-0312019_0_li8481155114365"></a><a name="dcs-migration-0312019_0_li8481155114365"></a>Only one DB is configured for a Redis Cluster instance. Data is migrated to a Redis Cluster instance in a different way from other types of instances. Nodes in the shards of a Redis Cluster must be connected separately through clients. Data is imported to the nodes separately. Run the following command to query the IP addresses of the cluster nodes:</p>
<p id="dcs-migration-0312019__dcs-migration-0312019_0_p1654462342611"><strong id="dcs-migration-0312019__dcs-migration-0312019_0_b19264216193218">redis-cli -h <em id="dcs-migration-0312019__dcs-migration-0312019_0_i6137133142718">{Redis Cluster IP} </em>-p 6379 -a<em id="dcs-migration-0312019__dcs-migration-0312019_0_i6181101772716"> {password}</em> cluster nodes</strong></p>
<p id="dcs-migration-0312019__dcs-migration-0312019_0_p1654462342611"><strong id="dcs-migration-0312019__dcs-migration-0312019_0_b19264216193218">redis-cli -h <em id="dcs-migration-0312019__dcs-migration-0312019_0_i7893733141512">{Redis Cluster IP}</em> -p 6379 -a <em id="dcs-migration-0312019__dcs-migration-0312019_0_i1994617429153">{password}</em> cluster nodes</strong></p>
<p id="dcs-migration-0312019__dcs-migration-0312019_0_p1446191953213">In the returned list of IP addresses, record the ones marked by "master".</p>
</li></ul>
</div>

4
docs/dcs/umn/dcs-migration-1117001.html
View File

@ -20,9 +20,9 @@
</li><li id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_li11225208162112">Install OBS Browser+.<p id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_p1022518842111"><a name="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_li11225208162112"></a><a name="dcs-migration-190703002_dcs-ug-0312037_li11225208162112"></a>For details, see section "Installing OBS Browser+" in <em id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_i118557531214">Object Storage Service (OBS) Tools Guide (OBS Browser+)</em>.</p>
</li><li id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_li201961913103814">Log in to OBS Browser+.<p id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_p1119621313811"><a name="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_li201961913103814"></a><a name="dcs-migration-190703002_dcs-ug-0312037_li201961913103814"></a>For details, see section "Logging In to OBS Browser+" in <em id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_i104881711215">Object Storage Service (OBS) Tools Guide (OBS Browser+)</em>.</p>
</li><li id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_li144125145718">Create a bucket.</li><li id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li10948943114817">Upload backup data.</li></ol>
</p></li><li id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_li8307135965315"><a name="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_li8307135965315"></a><a name="dcs-migration-190703002_dcs-ug-0312037_li8307135965315"></a><span>On the OBS console, upload the backup data files to the OBS bucket.</span><p><div class="p" id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_p73071659115311">Perform the following steps if the backup file size does not exceed 5 GB:<ol type="a" id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_ol17307059105315"><li id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li11425644112117">In the bucket list, click the name of the created bucket.</li><li id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li6425134472111">In the navigation pane, choose <strong id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_b2037028687">Objects</strong>.</li><li id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li8425844162114">On the <strong id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_b2088588249">Objects</strong> tab page, click <strong id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_b1409091267">Upload Object</strong>.</li><li id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li4601227114516">Upload the objects.<p id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_p2092314104615"><a name="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li4601227114516"></a><a name="dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li4601227114516"></a>To upload objects, drag files or folders to the <strong id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_b1459915347">Upload Object</strong> area or click <strong id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_b1648442873">add file</strong>. A maximum of 100 files can be uploaded at a time. The total size cannot exceed 5 GB.</p>
</p></li><li id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_li8307135965315"><a name="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_li8307135965315"></a><a name="dcs-migration-190703002_dcs-ug-0312037_li8307135965315"></a><span>On the OBS console, upload the backup data files to the OBS bucket.</span><p><div class="p" id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_p73071659115311">Perform the following steps if the backup file size does not exceed 5 GB:<ol type="a" id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_ol17307059105315"><li id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li11425644112117">In the bucket list, click the name of the created bucket.</li><li id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li6425134472111">In the navigation pane, choose <strong id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_b7335667220">Objects</strong>.</li><li id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li8425844162114">On the <strong id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_b1434535111128">Objects</strong> tab page, click <strong id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_b8346251131216">Upload Object</strong>.</li><li id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li4601227114516">Upload the objects.<p id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_p2092314104615"><a name="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li4601227114516"></a><a name="dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li4601227114516"></a>To upload objects, drag files or folders to the <strong id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_b1466016717292">Upload Object</strong> area or click <strong id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_b13375203619291">add file</strong>. A maximum of 100 files can be uploaded at a time. The total size cannot exceed 5 GB.</p>
<div class="fignone" id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_fig184786179256"><span class="figcap"><b>Figure 1 </b>Uploading an object</span><br><span><img id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_image174788172258" src="en-us_image_0000001634759086.png"></span></div>
</li><li id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_li29854713516">(Optional) Select <strong id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_b859379742">KMS encryption</strong> to encrypt the file you want to upload.</li><li id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_li103071459205315">Click <strong id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_b2373124572710">Upload</strong>.</li></ol>
</li><li id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_li29854713516">(Optional) Select <strong id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_b418982912617">KMS encryption</strong> to encrypt the file you want to upload.</li><li id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_li103071459205315">Click <strong id="dcs-migration-1117001__dcs-migration-190703002_dcs-ug-0312037_b2373124572710">Upload</strong>.</li></ol>
</div>
</p></li></ol>
</div>

4
docs/dcs/umn/dcs-migration-190703002.html
View File

@ -18,9 +18,9 @@
</li><li id="dcs-migration-190703002__dcs-ug-0312037_li11225208162112">Install OBS Browser+.<p id="dcs-migration-190703002__dcs-ug-0312037_p1022518842111"><a name="dcs-migration-190703002__dcs-ug-0312037_li11225208162112"></a><a name="dcs-ug-0312037_li11225208162112"></a>For details, see section "Installing OBS Browser+" in <em id="dcs-migration-190703002__dcs-ug-0312037_i118557531214">Object Storage Service (OBS) Tools Guide (OBS Browser+)</em>.</p>
</li><li id="dcs-migration-190703002__dcs-ug-0312037_li201961913103814">Log in to OBS Browser+.<p id="dcs-migration-190703002__dcs-ug-0312037_p1119621313811"><a name="dcs-migration-190703002__dcs-ug-0312037_li201961913103814"></a><a name="dcs-ug-0312037_li201961913103814"></a>For details, see section "Logging In to OBS Browser+" in <em id="dcs-migration-190703002__dcs-ug-0312037_i104881711215">Object Storage Service (OBS) Tools Guide (OBS Browser+)</em>.</p>
</li><li id="dcs-migration-190703002__dcs-ug-0312037_li144125145718">Create a bucket.</li><li id="dcs-migration-190703002__dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li10948943114817">Upload backup data.</li></ol>
</p></li><li id="dcs-migration-190703002__dcs-ug-0312037_li8307135965315"><a name="dcs-migration-190703002__dcs-ug-0312037_li8307135965315"></a><a name="dcs-ug-0312037_li8307135965315"></a><span>On the OBS console, upload the backup data files to the OBS bucket.</span><p><div class="p" id="dcs-migration-190703002__dcs-ug-0312037_p73071659115311">Perform the following steps if the backup file size does not exceed 5 GB:<ol type="a" id="dcs-migration-190703002__dcs-ug-0312037_ol17307059105315"><li id="dcs-migration-190703002__dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li11425644112117">In the bucket list, click the name of the created bucket.</li><li id="dcs-migration-190703002__dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li6425134472111">In the navigation pane, choose <strong id="dcs-migration-190703002__dcs-ug-0312037_b2037028687">Objects</strong>.</li><li id="dcs-migration-190703002__dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li8425844162114">On the <strong id="dcs-migration-190703002__dcs-ug-0312037_b2088588249">Objects</strong> tab page, click <strong id="dcs-migration-190703002__dcs-ug-0312037_b1409091267">Upload Object</strong>.</li><li id="dcs-migration-190703002__dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li4601227114516">Upload the objects.<p id="dcs-migration-190703002__dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_p2092314104615"><a name="dcs-migration-190703002__dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li4601227114516"></a><a name="dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li4601227114516"></a>To upload objects, drag files or folders to the <strong id="dcs-migration-190703002__dcs-ug-0312037_b1459915347">Upload Object</strong> area or click <strong id="dcs-migration-190703002__dcs-ug-0312037_b1648442873">add file</strong>. A maximum of 100 files can be uploaded at a time. The total size cannot exceed 5 GB.</p>
</p></li><li id="dcs-migration-190703002__dcs-ug-0312037_li8307135965315"><a name="dcs-migration-190703002__dcs-ug-0312037_li8307135965315"></a><a name="dcs-ug-0312037_li8307135965315"></a><span>On the OBS console, upload the backup data files to the OBS bucket.</span><p><div class="p" id="dcs-migration-190703002__dcs-ug-0312037_p73071659115311">Perform the following steps if the backup file size does not exceed 5 GB:<ol type="a" id="dcs-migration-190703002__dcs-ug-0312037_ol17307059105315"><li id="dcs-migration-190703002__dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li11425644112117">In the bucket list, click the name of the created bucket.</li><li id="dcs-migration-190703002__dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li6425134472111">In the navigation pane, choose <strong id="dcs-migration-190703002__dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_b7335667220">Objects</strong>.</li><li id="dcs-migration-190703002__dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li8425844162114">On the <strong id="dcs-migration-190703002__dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_b1434535111128">Objects</strong> tab page, click <strong id="dcs-migration-190703002__dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_b8346251131216">Upload Object</strong>.</li><li id="dcs-migration-190703002__dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li4601227114516">Upload the objects.<p id="dcs-migration-190703002__dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_p2092314104615"><a name="dcs-migration-190703002__dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li4601227114516"></a><a name="dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_li4601227114516"></a>To upload objects, drag files or folders to the <strong id="dcs-migration-190703002__dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_b1466016717292">Upload Object</strong> area or click <strong id="dcs-migration-190703002__dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_b13375203619291">add file</strong>. A maximum of 100 files can be uploaded at a time. The total size cannot exceed 5 GB.</p>
<div class="fignone" id="dcs-migration-190703002__dcs-ug-0312037_fig184786179256"><span class="figcap"><b>Figure 1 </b>Uploading an object</span><br><span><img id="dcs-migration-190703002__dcs-ug-0312037_image174788172258" src="en-us_image_0000001634759086.png"></span></div>
</li><li id="dcs-migration-190703002__dcs-ug-0312037_li29854713516">(Optional) Select <strong id="dcs-migration-190703002__dcs-ug-0312037_b859379742">KMS encryption</strong> to encrypt the file you want to upload.</li><li id="dcs-migration-190703002__dcs-ug-0312037_li103071459205315">Click <strong id="dcs-migration-190703002__dcs-ug-0312037_b2373124572710">Upload</strong>.</li></ol>
</li><li id="dcs-migration-190703002__dcs-ug-0312037_li29854713516">(Optional) Select <strong id="dcs-migration-190703002__dcs-ug-0312037_en-us_topic_0179456697_dcs-migration-190703002_b418982912617">KMS encryption</strong> to encrypt the file you want to upload.</li><li id="dcs-migration-190703002__dcs-ug-0312037_li103071459205315">Click <strong id="dcs-migration-190703002__dcs-ug-0312037_b2373124572710">Upload</strong>.</li></ol>
</div>
</p></li></ol>
</div>

2
docs/dcs/umn/dcs-pd-0326002.html
View File

@ -6,7 +6,7 @@
<ol id="dcs-pd-0326002__en-us_topic_0145956241_ol12178220195820"><li id="dcs-pd-0326002__en-us_topic_0145956241_li3178192019584"><strong id="dcs-pd-0326002__en-us_topic_0145956241_b1450214288278">E-commerce flash sales</strong><p id="dcs-pd-0326002__en-us_topic_0145956241_p2279324175820">E-commerce product catalogue, deals, and flash sales data can be cached to Redis.</p>
<p id="dcs-pd-0326002__en-us_topic_0145956241_p379443010317">For example, the high-concurrency data access in flash sales can be hardly handled by traditional relational databases. It requires the hardware to have higher configuration such as disk I/O. By contrast, Redis supports 100,000 QPS per node and allows you to implement locking using simple commands such as <strong id="dcs-pd-0326002__b177019815611">SET</strong>, <strong id="dcs-pd-0326002__b207018135619">GET</strong>, <strong id="dcs-pd-0326002__b1719895614">DEL</strong>, and <strong id="dcs-pd-0326002__b971198145619">RPUSH</strong> to handle flash sales.</p>
</li><li id="dcs-pd-0326002__en-us_topic_0145956241_li141780207582"><strong id="dcs-pd-0326002__en-us_topic_0145956241_b320193235417">Live video commenting</strong><p id="dcs-pd-0326002__en-us_topic_0145956241_p101341557143912">In live streaming, online user, gift ranking, and bullet comment data can be stored as sorted sets in Redis.</p>
<p id="dcs-pd-0326002__en-us_topic_0145956241_p589613262586">For example, bullet comments can be returned using the <strong id="dcs-pd-0326002__en-us_topic_0145956241_b8145174833710">ZREVRANGEBYSCORE</strong> command. The <strong id="dcs-pd-0326002__en-us_topic_0145956241_b15630131983920">ZPOPMAX</strong> and <strong id="dcs-pd-0326002__en-us_topic_0145956241_b17724182112399">ZPOPMIN</strong> commands in Redis 5.0 can further facilitate message processing.</p>
<p id="dcs-pd-0326002__en-us_topic_0145956241_p589613262586">For example, bullet comments can be returned using the <strong id="dcs-pd-0326002__b05495580560">ZREVRANGEBYSCORE</strong> command. The <strong id="dcs-pd-0326002__b185494580567">ZPOPMAX</strong> and <strong id="dcs-pd-0326002__b75491958195612">ZPOPMIN</strong> commands in Redis 5.0 can further facilitate message processing.</p>
</li><li id="dcs-pd-0326002__en-us_topic_0145956241_li1178172035816"><strong id="dcs-pd-0326002__en-us_topic_0145956241_b1404183925411">Game leaderboard</strong><p id="dcs-pd-0326002__en-us_topic_0145956241_p1626994118258">In online gaming, the highest ranking players are displayed and updated in real time. The leaderboard ranking can be stored as sorted sets, which are easy to use with up to 20 commands.</p>
</li><li id="dcs-pd-0326002__en-us_topic_0145956241_li117918551934"><strong id="dcs-pd-0326002__en-us_topic_0145956241_b35791620485">Social networking comments</strong><p id="dcs-pd-0326002__en-us_topic_0145956241_p19560112410516">In web applications, queries of post comments often involve sorting by time in descending order. As comments pile up, sorting becomes less efficient.</p>
<p id="dcs-pd-0326002__en-us_topic_0145956241_p17663315101013">By using lists in Redis, a preset number of comments can be returned from the cache, rather than from disk, easing the load off the database and accelerating application responses.</p>

4
docs/dcs/umn/dcs-pd-0326003.html
View File

@ -23,7 +23,7 @@
</td>
<td class="cellrowborder" valign="top" width="25.03%" headers="mcps1.3.3.2.2.4.1.2 "><p id="dcs-pd-0326003__en-us_topic_0145956234_p11598569365">-</p>
</td>
<td class="cellrowborder" valign="top" width="60.08%" headers="mcps1.3.3.2.2.4.1.3 "><p id="dcs-pd-0326003__en-us_topic_0145956234_p20598116183613">Deeply engaged in the open-source community and supports the latest Redis version. Redis 3.0/4.0/5.0/6.0 are supported.</p>
<td class="cellrowborder" valign="top" width="60.08%" headers="mcps1.3.3.2.2.4.1.3 "><p id="dcs-pd-0326003__en-us_topic_0145956234_p20598116183613">Deeply engaged in the open-source community and supports the latest Redis version. Available for Redis 3.0/4.0/5.0/6.0.</p>
</td>
</tr>
<tr id="dcs-pd-0326003__en-us_topic_0145956234_row6598126123618"><td class="cellrowborder" valign="top" width="14.89%" headers="mcps1.3.3.2.2.4.1.1 "><p id="dcs-pd-0326003__en-us_topic_0145956234_p115984618364">Security</p>
@ -46,7 +46,7 @@
</td>
<td class="cellrowborder" valign="top" width="60.08%" headers="mcps1.3.3.2.2.4.1.3 "><p id="dcs-pd-0326003__en-us_topic_0145956234_p124714371085">Provides more than 30 monitoring metrics and customizable alarm threshold and policies.</p>
<ul id="dcs-pd-0326003__en-us_topic_0145956234_ul74714374813"><li id="dcs-pd-0326003__en-us_topic_0145956234_li124716372816">Various metrics<ul id="dcs-pd-0326003__en-us_topic_0145956234_ul16471837289"><li id="dcs-pd-0326003__en-us_topic_0145956234_li114711376811">External metrics include the number of commands, concurrent operations, connections, clients, and denied connections.</li><li id="dcs-pd-0326003__en-us_topic_0145956234_li34773718816">Resource usage metrics include CPU usage, physical memory usage, network input throughput, and network output throughput.</li><li id="dcs-pd-0326003__en-us_topic_0145956234_li54718378818">Internal metrics include instance capacity usage, as well as the number of keys, expired keys, PubSub channels, PubSub patterns, keyspace hits, and keyspace misses.</li></ul>
</li><li id="dcs-pd-0326003__en-us_topic_0145956234_li64723712816">Custom alarm thresholds and policies for different metrics to help identify service faults.</li></ul>
</li><li id="dcs-pd-0326003__en-us_topic_0145956234_li64723712816">Customize alarm thresholds and policies for different metrics to help identify service faults.</li></ul>
</td>
</tr>
<tr id="dcs-pd-0326003__en-us_topic_0145956234_row135984683610"><td class="cellrowborder" valign="top" width="14.89%" headers="mcps1.3.3.2.2.4.1.1 "><p id="dcs-pd-0326003__en-us_topic_0145956234_p159817653611">Backup and restoration</p>

2
docs/dcs/umn/dcs-pd-0916001.html
View File

@ -1,7 +1,7 @@
<a name="dcs-pd-0916001"></a><a name="dcs-pd-0916001"></a>
<h1 class="topictitle1">Redis 3.0 Instance Specifications</h1>
<div id="body1600250977976"><p id="dcs-pd-0916001__p154261042172718">This section describes <span class="keyword" id="dcs-pd-0916001__keyword16904857975732">DCS Redis 3.0 instance specifications</span>, including the total memory, available memory, maximum number of connections allowed, maximum/assured bandwidth, and reference performance.</p>
<div id="body1600250977976"><p id="dcs-pd-0916001__p154261042172718">This section describes <span class="keyword" id="dcs-pd-0916001__keyword1934414341581">DCS Redis 3.0 instance specifications</span>, including the total memory, available memory, maximum number of connections allowed, maximum/assured bandwidth, and reference performance.</p>
<p id="dcs-pd-0916001__p993813111219">The following metrics are related to the instance specifications:</p>
<ul id="dcs-pd-0916001__ul174431454161112"><li id="dcs-pd-0916001__li5444115461114">Used memory: You can check the memory usage of an instance by viewing the <strong id="dcs-pd-0916001__b174918436275732">Memory Usage</strong> and <strong id="dcs-pd-0916001__b43072430975732">Used Memory</strong> metrics.</li><li id="dcs-pd-0916001__li4444155417117">Maximum connections: The maximum number of connections allowed is the maximum number of clients that can be connected to an instance. To check the number of connections to an instance, view the <strong id="dcs-pd-0916001__b39937184975732">Connected Clients</strong> metric.</li><li id="dcs-pd-0916001__li12444145419113">QPS represents queries per second, which is the number of commands processed per second.<div class="note" id="dcs-pd-0916001__nbd28d4bd47184ebbaad5bc928e17bd9a"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="dcs-pd-0916001__ul18305845124510"><li id="dcs-pd-0916001__li1730584511456">Single-node, master/standby, and Proxy Cluster types are available.</li><li id="dcs-pd-0916001__li10496164715452">Only the x86 architecture is supported. The Arm architecture is not supported.</li></ul>
</div></div>

2
docs/dcs/umn/dcs-pd-0916002.html
View File

@ -1,7 +1,7 @@
<a name="dcs-pd-0916002"></a><a name="dcs-pd-0916002"></a>
<h1 class="topictitle1">Redis 4.0 and 5.0 Instance Specifications</h1>
<div id="body1600250978002"><p id="dcs-pd-0916002__p154261042172718">This section describes <span class="keyword" id="dcs-pd-0916002__keyword6287920097594">DCS Redis 4.0 and 5.0 instance specifications</span>, including the total memory, available memory, maximum number of connections allowed, maximum/assured bandwidth, and reference performance.</p>
<div id="body1600250978002"><p id="dcs-pd-0916002__p154261042172718">This section describes <span class="keyword" id="dcs-pd-0916002__keyword61951224299">DCS Redis 4.0 and 5.0 instance specifications</span>, including the total memory, available memory, maximum number of connections allowed, maximum/assured bandwidth, and reference performance.</p>
<p id="dcs-pd-0916002__p993813111219">The following metrics are related to the instance specifications:</p>
<ul id="dcs-pd-0916002__ul174431454161112"><li id="dcs-pd-0916002__li5444115461114">Used memory: You can check the memory usage of an instance by viewing the <strong id="dcs-pd-0916002__b19299386447594">Memory Usage</strong> and <strong id="dcs-pd-0916002__b2681614187594">Used Memory</strong> metrics.</li><li id="dcs-pd-0916002__li4444155417117">Maximum connections: The maximum number of connections allowed is the maximum number of clients that can be connected to an instance. To check the number of connections to an instance, view the <strong id="dcs-pd-0916002__b11315278257594">Connected Clients</strong> metric. After an instance is created, you can change the maximum number of connections of the instance by modifying the <strong id="dcs-pd-0916002__b27141915503">maxclients</strong> parameter on the <strong id="dcs-pd-0916002__b371489155019">Instance Configuration</strong> &gt; <strong id="dcs-pd-0916002__b371469145011">Parameters</strong> page on the console.</li><li id="dcs-pd-0916002__li12444145419113">QPS represents queries per second, which is the number of commands processed per second.</li><li id="dcs-pd-0916002__li11666341415">Bandwidth: You can view the <strong id="dcs-pd-0916002__b13812174717594">Flow Control Times</strong> metric to check whether the bandwidth has exceeded the limit.<p id="dcs-pd-0916002__p040220814264">You can also check the <strong id="dcs-pd-0916002__b26955815525">Bandwidth Usage</strong> metric. This metric is for reference only, because it may be higher than 100%. For details, see <a href="dcs-faq-0513001.html">Why Does Bandwidth Usage Exceed 100%?</a></p>
</li></ul>

2
docs/dcs/umn/dcs-pd-200312004.html
View File

@ -12,7 +12,7 @@
<p id="dcs-pd-200312004__en-us_topic_0145956240_p6683155115346">For details, see: <a href="dcs-ug-0312025.html">Modifying Maintenance Time Window</a>.</p>
</div>
<div class="section" id="dcs-pd-200312004__en-us_topic_0145956240_section27941513183211"><h4 class="sectiontitle">Cross-AZ Deployment</h4><p id="dcs-pd-200312004__en-us_topic_0145956240_p187388152325">Master/Standby instances are deployed across different AZs with physically isolated power supplies and networks. Applications can also be deployed across AZs to achieve HA for both data and applications.</p>
<p id="dcs-pd-200312004__p18724141752918">When creating a master/standby or cluster DCS Redis instance, you can select a standby AZ for the standby node.</p>
<p id="dcs-pd-200312004__p18724141752918">When creating a master/standby or cluster DCS Redis instance, you can select a standby AZ for the node.</p>
</div>
<div class="section" id="dcs-pd-200312004__en-us_topic_0145956240_section20999323134412"><a name="dcs-pd-200312004__en-us_topic_0145956240_section20999323134412"></a><a name="en-us_topic_0145956240_section20999323134412"></a><h4 class="sectiontitle">Shard</h4><p id="dcs-pd-200312004__en-us_topic_0145956240_p485319256447">A shard is a management unit of a cluster DCS Redis instance. Each shard corresponds to a redis-server process. A cluster consists of multiple shards. Each shard has multiple slots. Data is distributedly stored in the slots. The use of shards increases cache capacity and concurrent connections.</p>
<p id="dcs-pd-200312004__p1728812129347">Each cluster instance consists of multiple shards. By default, each shard is a master/standby instance with two replicas. The number of shards is equal to the number of master nodes in a cluster instance.</p>

8
docs/dcs/umn/dcs-pd-200713005.html
View File

@ -10,7 +10,7 @@
</li></ul>
</div></div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="dcs-pd-200713005__table7721852165419" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Commands supported by DCS Redis 3.0 instances 1</caption><thead align="left"><tr id="dcs-pd-200713005__row6721752185415"><th align="left" class="cellrowborder" valign="top" width="13.62%" id="mcps1.3.5.4.2.8.1.1"><p id="dcs-pd-200713005__p872852165414"><a href="https://redis.io/commands#generic" target="_blank" rel="noopener noreferrer">Keys</a></p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="dcs-pd-200713005__table7721852165419" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Commands supported by DCS Redis 3.0 instances (1)</caption><thead align="left"><tr id="dcs-pd-200713005__row6721752185415"><th align="left" class="cellrowborder" valign="top" width="13.62%" id="mcps1.3.5.4.2.8.1.1"><p id="dcs-pd-200713005__p872852165414"><a href="https://redis.io/commands#generic" target="_blank" rel="noopener noreferrer">Keys</a></p>
</th>
<th align="left" class="cellrowborder" valign="top" width="15.25%" id="mcps1.3.5.4.2.8.1.2"><p id="dcs-pd-200713005__p1472195225416"><a href="https://redis.io/commands#string" target="_blank" rel="noopener noreferrer">String</a></p>
</th>
@ -360,7 +360,7 @@
</table>
</div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="dcs-pd-200713005__table16968255165120" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Commands supported by DCS Redis 3.0 instances 2</caption><thead align="left"><tr id="dcs-pd-200713005__row20969195585113"><th align="left" class="cellrowborder" valign="top" width="16.361636163616364%" id="mcps1.3.5.5.2.7.1.1"><p id="dcs-pd-200713005__p179666106529"><a href="https://redis.io/commands#hyperloglog" target="_blank" rel="noopener noreferrer">HyperLoglog</a></p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="dcs-pd-200713005__table16968255165120" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Commands supported by DCS Redis 3.0 instances (2)</caption><thead align="left"><tr id="dcs-pd-200713005__row20969195585113"><th align="left" class="cellrowborder" valign="top" width="16.361636163616364%" id="mcps1.3.5.5.2.7.1.1"><p id="dcs-pd-200713005__p179666106529"><a href="https://redis.io/commands#hyperloglog" target="_blank" rel="noopener noreferrer">HyperLoglog</a></p>
</th>
<th align="left" class="cellrowborder" valign="top" width="15.401540154015404%" id="mcps1.3.5.5.2.7.1.2"><p id="dcs-pd-200713005__p596513107528"><a href="https://redis.io/commands#pubsub" target="_blank" rel="noopener noreferrer">Pub/Sub</a></p>
</th>
@ -458,7 +458,7 @@
</div>
<div class="section" id="dcs-pd-200713005__section144182915424"><a name="dcs-pd-200713005__section144182915424"></a><a name="section144182915424"></a><h4 class="sectiontitle">Commands Disabled by DCS for Redis 3.0</h4><p id="dcs-pd-200713005__p188611032123510">The following lists commands disabled by DCS for Redis 3.0.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="dcs-pd-200713005__table62148252438" frame="border" border="1" rules="all"><caption><b>Table 3 </b>Redis commands disabled in single-node and master/standby Redis 3.0 instances</caption><thead align="left"><tr id="dcs-pd-200713005__row1821472513435"><th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.6.3.2.3.1.1"><p id="dcs-pd-200713005__p7678192231220"><a href="https://redis.io/commands#generic" target="_blank" rel="noopener noreferrer">Keys</a></p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="dcs-pd-200713005__table62148252438" frame="border" border="1" rules="all"><caption><b>Table 3 </b>Redis commands disabled in single-node and master/standby DCS Redis 3.0 instances</caption><thead align="left"><tr id="dcs-pd-200713005__row1821472513435"><th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.6.3.2.3.1.1"><p id="dcs-pd-200713005__p7678192231220"><a href="https://redis.io/commands#generic" target="_blank" rel="noopener noreferrer">Keys</a></p>
</th>
<th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.6.3.2.3.1.2"><p id="dcs-pd-200713005__p16214925114310"><a href="https://redis.io/commands#server" target="_blank" rel="noopener noreferrer">Server</a></p>
</th>
@ -508,7 +508,7 @@
</table>
</div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="dcs-pd-200713005__table162593454712" frame="border" border="1" rules="all"><caption><b>Table 4 </b>Redis commands disabled in Proxy Cluster Redis 3.0 instances</caption><thead align="left"><tr id="dcs-pd-200713005__row1462683444715"><th align="left" class="cellrowborder" valign="top" width="12.112422484496898%" id="mcps1.3.6.4.2.8.1.1"><p id="dcs-pd-200713005__p2626183411473"><a href="https://redis.io/commands#generic" target="_blank" rel="noopener noreferrer">Keys</a></p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="dcs-pd-200713005__table162593454712" frame="border" border="1" rules="all"><caption><b>Table 4 </b>Redis commands disabled in Proxy Cluster DCS Redis 3.0 instances</caption><thead align="left"><tr id="dcs-pd-200713005__row1462683444715"><th align="left" class="cellrowborder" valign="top" width="12.112422484496898%" id="mcps1.3.6.4.2.8.1.1"><p id="dcs-pd-200713005__p2626183411473"><a href="https://redis.io/commands#generic" target="_blank" rel="noopener noreferrer">Keys</a></p>
</th>
<th align="left" class="cellrowborder" valign="top" width="15.723144628925786%" id="mcps1.3.6.4.2.8.1.2"><p id="dcs-pd-200713005__p15626134194712"><a href="https://redis.io/commands#server" target="_blank" rel="noopener noreferrer">Server</a></p>
</th>

2
docs/dcs/umn/dcs-pd-200813002.html
View File

@ -651,7 +651,7 @@
</table>
</div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="dcs-pd-200813002__table18562182810110" frame="border" border="1" rules="all"><caption><b>Table 4 </b>Redis commands disabled in Redis Cluster Redis 5.0 instances</caption><thead align="left"><tr id="dcs-pd-200813002__row135621028511"><th align="left" class="cellrowborder" valign="top" width="32.26%" id="mcps1.3.6.4.2.4.1.1"><p id="dcs-pd-200813002__p456372812119"><a href="https://redis.io/commands#generic" target="_blank" rel="noopener noreferrer">Keys</a></p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="dcs-pd-200813002__table18562182810110" frame="border" border="1" rules="all"><caption><b>Table 4 </b>Redis commands disabled in Redis Cluster DCS Redis 5.0 instances</caption><thead align="left"><tr id="dcs-pd-200813002__row135621028511"><th align="left" class="cellrowborder" valign="top" width="32.26%" id="mcps1.3.6.4.2.4.1.1"><p id="dcs-pd-200813002__p456372812119"><a href="https://redis.io/commands#generic" target="_blank" rel="noopener noreferrer">Keys</a></p>
</th>
<th align="left" class="cellrowborder" valign="top" width="28.68%" id="mcps1.3.6.4.2.4.1.2"><p id="dcs-pd-200813002__p956316280111"><a href="https://redis.io/commands#server" target="_blank" rel="noopener noreferrer">Server</a></p>
</th>

2
docs/dcs/umn/dcs-pd-200813003.html
View File

@ -124,7 +124,7 @@
</tr>
<tr id="dcs-pd-200813003__en-us_topic_0269770665_row1227514019276"><td class="cellrowborder" valign="top" width="29.53%" headers="mcps1.3.5.2.3.1.1 "><p id="dcs-pd-200813003__en-us_topic_0269770665_p172758407278">Multi-key commands that do not support cross-slot access</p>
</td>
<td class="cellrowborder" valign="top" width="70.47%" headers="mcps1.3.5.2.3.1.2 "><p id="dcs-pd-200813003__en-us_topic_0269770665_p162756405277">SMOVE, SORT, BITOP, MSETNX, RENAME, RENAMENX, BLPOP, BRPOP, RPOPLPUSH, BRPOPLPUSH, PFMERGE, PFCOUNT</p>
<td class="cellrowborder" valign="top" width="70.47%" headers="mcps1.3.5.2.3.1.2 "><p id="dcs-pd-200813003__en-us_topic_0269770665_p162756405277">SMOVE, SORT, BITOP, MSETNX, RENAME, RENAMENX, BLPOP, BRPOP, RPOPLPUSH, BRPOPLPUSH, PFMERGE, PFCOUNT, BLMOVE, COPY, GEOSEARCHSTORE, LMOVE, ZRANGESTORE</p>
</td>
</tr>
</tbody>

2
docs/dcs/umn/dcs-pd-200813004.html
View File

@ -9,6 +9,8 @@
<div class="section" id="dcs-pd-200813004__section1071724134515"><h4 class="sectiontitle">EVAL and EVALSHA Commands</h4><ul id="dcs-pd-200813004__ul1914511468452"><li id="dcs-pd-200813004__li161451846184514">When the <strong id="dcs-pd-200813004__b88442504575717">EVAL</strong> or <strong id="dcs-pd-200813004__b143284181675717">EVALSHA</strong> command is run, at least one key must be contained in the command parameter. Otherwise, the error message "ERR eval/evalsha numkeys must be bigger than zero in redis cluster mode" is displayed.</li><li id="dcs-pd-200813004__li91451246114513">When the <strong id="dcs-pd-200813004__b6323738075717">EVAL</strong> or <strong id="dcs-pd-200813004__b20252647175717">EVALSHA</strong> command is run, a cluster DCS Redis instance uses the first key to compute slots. Ensure that the keys to be operated in your code are in the same slot. For details, visit <a href="https://redis.io/commands" target="_blank" rel="noopener noreferrer">https://redis.io/commands</a>.</li><li id="dcs-pd-200813004__li17146134684513">For the <strong id="dcs-pd-200813004__b156441818975717">EVAL</strong> command:<ul id="dcs-pd-200813004__ul11146346104517"><li id="dcs-pd-200813004__li12146546194512">You are advised to learn the Lua script features of Redis before running the <strong id="dcs-pd-200813004__b51532644175717">EVAL</strong> command. For details, see <a href="https://redis.io/commands/eval" target="_blank" rel="noopener noreferrer">https://redis.io/commands/eval</a>.</li><li id="dcs-pd-200813004__li8146114619453">The execution timeout time of a Lua script is 5 seconds. Time-consuming statements such as long-time sleep and large loop statements should be avoided.</li><li id="dcs-pd-200813004__li1414684634512">When calling a Lua script, do not use random functions to specify keys. Otherwise, the execution results are inconsistent on the master and standby nodes.</li></ul>
</li></ul>
</div>
<div class="section" id="dcs-pd-200813004__section1883797104416"><h4 class="sectiontitle">Debugging Lua Scripts</h4><p id="dcs-pd-200813004__p1169313094518">When you debug Lua scripts for Proxy Cluster and read/write splitting instances, only the asynchronous non-blocking mode <strong id="dcs-pd-200813004__b101781911104015">--ldb</strong> is supported. The synchronous blocking mode <strong id="dcs-pd-200813004__b0178191118409">--ldb-sync-mode</strong> is not supported. By default, the maximum concurrency on each proxy is <strong id="dcs-pd-200813004__b15586191514015">2</strong>. This restriction does not apply to other instance types.</p>
</div>
<div class="section" id="dcs-pd-200813004__section17333752164515"><h4 class="sectiontitle">Other Restrictions</h4><ul id="dcs-pd-200813004__ul487712135467"><li id="dcs-pd-200813004__li2877113174613">The time limit for executing a Redis command is 15 seconds. To prevent other services from failing, a master/replica switchover will be triggered after the command execution times out.</li></ul>
</div>
</div>

4
docs/dcs/umn/dcs-pd-200916001.html
View File

@ -472,7 +472,7 @@
</div>
<div class="section" id="dcs-pd-200916001__section144182915424"><a name="dcs-pd-200916001__section144182915424"></a><a name="section144182915424"></a><h4 class="sectiontitle">Commands Disabled by DCS for Redis 4.0</h4><p id="dcs-pd-200916001__p2778541611">The following lists commands disabled by DCS for Redis 4.0.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="dcs-pd-200916001__table62148252438" frame="border" border="1" rules="all"><caption><b>Table 3 </b>Redis commands disabled in single-node and master/standby Redis 4.0 instances</caption><thead align="left"><tr id="dcs-pd-200916001__row1821472513435"><th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.6.3.2.3.1.1"><p id="dcs-pd-200916001__p72143256436"><a href="https://redis.io/commands#generic" target="_blank" rel="noopener noreferrer">Keys</a></p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="dcs-pd-200916001__table62148252438" frame="border" border="1" rules="all"><caption><b>Table 3 </b>Redis commands disabled in single-node and master/standby DCS Redis 4.0 instances</caption><thead align="left"><tr id="dcs-pd-200916001__row1821472513435"><th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.6.3.2.3.1.1"><p id="dcs-pd-200916001__p72143256436"><a href="https://redis.io/commands#generic" target="_blank" rel="noopener noreferrer">Keys</a></p>
</th>
<th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.6.3.2.3.1.2"><p id="dcs-pd-200916001__p16214925114310"><a href="https://redis.io/commands#server" target="_blank" rel="noopener noreferrer">Server</a></p>
</th>
@ -532,7 +532,7 @@
</table>
</div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="dcs-pd-200916001__table18562182810110" frame="border" border="1" rules="all"><caption><b>Table 4 </b>Redis commands disabled in Redis Cluster Redis 4.0 instances</caption><thead align="left"><tr id="dcs-pd-200916001__row135621028511"><th align="left" class="cellrowborder" valign="top" width="32.26%" id="mcps1.3.6.4.2.4.1.1"><p id="dcs-pd-200916001__p93878229270"><a href="https://redis.io/commands#generic" target="_blank" rel="noopener noreferrer">Keys</a></p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="dcs-pd-200916001__table18562182810110" frame="border" border="1" rules="all"><caption><b>Table 4 </b>Redis commands disabled in Redis Cluster DCS Redis 4.0 instances</caption><thead align="left"><tr id="dcs-pd-200916001__row135621028511"><th align="left" class="cellrowborder" valign="top" width="32.26%" id="mcps1.3.6.4.2.4.1.1"><p id="dcs-pd-200916001__p93878229270"><a href="https://redis.io/commands#generic" target="_blank" rel="noopener noreferrer">Keys</a></p>
</th>
<th align="left" class="cellrowborder" valign="top" width="28.68%" id="mcps1.3.6.4.2.4.1.2"><p id="dcs-pd-200916001__p193871022192714"><a href="https://redis.io/commands#server" target="_blank" rel="noopener noreferrer">Server</a></p>
</th>

291
docs/dcs/umn/dcs-pd-210209002.html
View File

File diff suppressed because it is too large Load Diff

2
docs/dcs/umn/dcs-ug-0312004.html
View File

@ -3,7 +3,7 @@
<h1 class="topictitle1">Preparing Required Resources</h1>
<div id="body8662426"><p id="dcs-ug-0312004__en-us_topic_0148195347_p1558343104910">To access DCS instances through a Virtual Private Cloud (VPC), create a VPC and configure security groups and subnets for it before using DCS. A VPC provides an isolated virtual network environment which you can configure and manage. Using VPCs enhances cloud resource security and simplifies network deployment.</p>
<p id="dcs-ug-0312004__en-us_topic_0148195347_p126699426357">Once you have created the required resources, you can use them for all DCS instances you subsequently create.</p>
<div class="section" id="dcs-ug-0312004__en-us_topic_0148195347_section1337733315214"><h4 class="sectiontitle">Creating a VPC and Subnet</h4><ol id="dcs-ug-0312004__en-us_topic_0148195347_ol142955211483"><li id="dcs-ug-0312004__li64301019115011"><span>Log in to the management console.</span></li><li id="dcs-ug-0312004__en-us_topic_0148195251_li110442415511"><span>Click <span><img id="dcs-ug-0312004__en-us_topic_0148195251_i0d8b8411c49244f694e4f9ebeef4b3c5" src="en-us_image_0000001214124082.png"></span> in the upper left corner and select a region and a project.</span></li><li id="dcs-ug-0312004__en-us_topic_0148195347_li65541255184813"><span>Click <strong id="dcs-ug-0312004__en-us_topic_0148195347_b206418283210">Service List</strong>, and choose <strong id="dcs-ug-0312004__en-us_topic_0148195347_b4692759995636">Network</strong> &gt; <strong id="dcs-ug-0312004__en-us_topic_0148195347_b31278886101415">Virtual Private Cloud</strong> to launch the VPC console.</span></li><li id="dcs-ug-0312004__en-us_topic_0148195347_li55541355164813"><span>Click <strong id="dcs-ug-0312004__b53700656991326">Apply for VPC</strong>.</span></li><li id="dcs-ug-0312004__li5167122841915"><span>Create a VPC as prompted, retaining the default values unless otherwise required.</span><p><p id="dcs-ug-0312004__p745523410196">For details about how to create a VPC, see <a href="https://docs.otc.t-systems.com/usermanual/vpc/en-us_topic_0013935842.html" target="_blank" rel="noopener noreferrer">Creating a VPC</a>.</p>
<div class="section" id="dcs-ug-0312004__en-us_topic_0148195347_section1337733315214"><h4 class="sectiontitle">Creating a VPC and Subnet</h4><ol id="dcs-ug-0312004__en-us_topic_0148195347_ol142955211483"><li id="dcs-ug-0312004__li64301019115011"><span>Log in to the management console.</span></li><li id="dcs-ug-0312004__en-us_topic_0148195251_li110442415511"><span>Click <span><img id="dcs-ug-0312004__en-us_topic_0148195251_i0d8b8411c49244f694e4f9ebeef4b3c5" src="en-us_image_0000001214124082.png"></span> in the upper left corner and select a region and a project.</span></li><li id="dcs-ug-0312004__en-us_topic_0148195347_li65541255184813"><span>Click <strong id="dcs-ug-0312004__en-us_topic_0148195347_b206418283210">Service List</strong>, and choose <strong id="dcs-ug-0312004__en-us_topic_0148195347_b4692759995636">Network</strong> &gt; <strong id="dcs-ug-0312004__en-us_topic_0148195347_b31278886101415">Virtual Private Cloud</strong> to launch the VPC console.</span></li><li id="dcs-ug-0312004__en-us_topic_0148195347_li55541355164813"><span>Click <strong id="dcs-ug-0312004__b2317104713167">Apply for VPC</strong>.</span></li><li id="dcs-ug-0312004__li5167122841915"><span>Create a VPC as prompted, retaining the default values unless otherwise required.</span><p><p id="dcs-ug-0312004__p745523410196">For details about how to create a VPC, see <a href="https://docs.otc.t-systems.com/usermanual/vpc/en-us_topic_0013935842.html" target="_blank" rel="noopener noreferrer">Creating a VPC</a>.</p>
<p id="dcs-ug-0312004__en-us_topic_0148195347_p179701324173519">After a VPC is created, a subnet is also created in the subnet. If the VPC needs more subnets, go to <a href="#dcs-ug-0312004__li66581623151519">6</a> and <a href="#dcs-ug-0312004__en-us_topic_0148195347_li10954228154518">7</a>. Otherwise, go to <a href="#dcs-ug-0312004__section564574212010">Creating a Security Group</a>.</p>
<div class="note" id="dcs-ug-0312004__note1847553931218"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="dcs-ug-0312004__ul2337169185411"><li id="dcs-ug-0312004__li6395655614">When creating a VPC, <strong id="dcs-ug-0312004__b185947528429">CIDR Block</strong> indicates the IP address range of the VPC. If this parameter is set, the IP addresses of subnets in the VPC must be within the IP address range of the VPC.</li><li id="dcs-ug-0312004__li115125119546">If you create a VPC to provision DCS instances, you do not need to configure the CIDR block for the VPC.</li></ul>
</div></div>

8
docs/dcs/umn/dcs-ug-0312009.html
View File

@ -32,9 +32,9 @@
<p id="dcs-ug-0312009__en-us_topic_0148195315_p4468552185415">If the command output contains <strong id="dcs-ug-0312009__en-us_topic_0148195315_b624017599492">redis</strong>, the phpredis client environment has been set up.</p>
</li></ol>
</p></li><li id="dcs-ug-0312009__en-us_topic_0148195315_li136344144810"><span>Access the DCS instance by using phpredis.</span><p><ol type="a" id="dcs-ug-0312009__en-us_topic_0148195315_ol203521734477"><li id="dcs-ug-0312009__en-us_topic_0148195315_li143523341774">Edit a <strong id="dcs-ug-0312009__en-us_topic_0148195315_b34091359115314">redis.php</strong> file.<pre class="screen" id="dcs-ug-0312009__en-us_topic_0148195315_screen42337418213">&lt;?php
$redis_host = "<em id="dcs-ug-0312009__en-us_topic_0148195315_i666031924">{redis_instance_address}</em>";
$redis_port = <em id="dcs-ug-0312009__en-us_topic_0148195315_i96051916175">6379</em>;
$user_pwd = "<em id="dcs-ug-0312009__en-us_topic_0148195315_i1493710378212">{password}</em>";
$redis_host = "{redis_instance_address}";
$redis_port = {port};
$user_pwd = "{password}";
$redis = new Redis();
if ($redis-&gt;connect($redis_host, $redis_port) == false) {
die($redis-&gt;getLastError());
@ -49,7 +49,7 @@
echo $value;
$redis-&gt;close();
?&gt;</pre>
<p id="dcs-ug-0312009__en-us_topic_0148195315_p96081455513"><em id="dcs-ug-0312009__en-us_topic_0148195315_i152081552192">{redis_instance_address}</em> indicates the IP address/domain name of DCS instance and <strong id="dcs-ug-0312009__en-us_topic_0148195315_b182093556195">6379</strong> is an example port number of DCS instance. For details about how to obtain the IP address/domain name and port, see <a href="#dcs-ug-0312009__en-us_topic_0148195315_li8233164074413">1</a>. Change them as required. <em id="dcs-ug-0312009__en-us_topic_0148195315_i1555133973210">{password}</em> indicates the password used to log in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation. If password-free access is enabled, shield the <strong id="dcs-ug-0312009__en-us_topic_0148195315_b1213628133613">if</strong> statement for password authentication.</p>
<p id="dcs-ug-0312009__en-us_topic_0148195315_p96081455513"><em id="dcs-ug-0312009__en-us_topic_0148195315_i0711211145012">{redis_instance_address}</em> indicates the example IP address/domain name of the DCS instance and <em id="dcs-ug-0312009__en-us_topic_0148195315_i19711711135016">{port}</em> indicates the port number of the DCS instance. For details about how to obtain the IP address/domain name and port, see <a href="#dcs-ug-0312009__en-us_topic_0148195315_li8233164074413">1</a>. Change them as required. <em id="dcs-ug-0312009__en-us_topic_0148195315_i132641725135014">{password}</em> indicates the password used to log in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation. If password-free access is enabled, shield the <strong id="dcs-ug-0312009__en-us_topic_0148195315_b1213628133613">if</strong> statement for password authentication.</p>
</li><li id="dcs-ug-0312009__en-us_topic_0148195315_li13961652072">Run the <strong id="dcs-ug-0312009__en-us_topic_0148195315_b182075219504">php redis.php</strong> command to access the DCS instance.</li></ol>
</p></li></ol>
</div>

4
docs/dcs/umn/dcs-ug-0312010.html
View File

@ -26,7 +26,7 @@ int main(int argc, char **argv) {
redisContext *conn;
redisReply *reply;
if (argc &lt; 3) {
printf("Usage: example <em id="dcs-ug-0312010__en-us_topic_0148195243_i151811705416">{instance_ip_address}</em> 6379 <em id="dcs-ug-0312010__en-us_topic_0148195243_i1411281245416">{password}</em>\n");
printf("Usage: example {instance_ip_address} 6379 {password}\n");
exit(0);
}
const char *hostname = argv[1];
@ -66,7 +66,7 @@ int main(int argc, char **argv) {
<p id="dcs-ug-0312010__en-us_topic_0148195243_p1094812195020">If an error is reported, locate the directory where the <strong id="dcs-ug-0312010__en-us_topic_0148195243_b7579138151">hiredis.h</strong> file is saved and modify the compilation command.</p>
<p id="dcs-ug-0312010__en-us_topic_0148195243_p6781027145015">After the compilation, an executable <strong id="dcs-ug-0312010__en-us_topic_0148195243_b3152616191515">connRedis</strong> file is obtained.</p>
</li><li id="dcs-ug-0312010__en-us_topic_0148195243_li13134113319491">Run the following command to access the chosen DCS Redis instance:<p id="dcs-ug-0312010__en-us_topic_0148195243_p11552173917421"><a name="dcs-ug-0312010__en-us_topic_0148195243_li13134113319491"></a><a name="en-us_topic_0148195243_li13134113319491"></a><strong id="dcs-ug-0312010__en-us_topic_0148195243_b0951032135312">./connRedis</strong> <strong id="dcs-ug-0312010__en-us_topic_0148195243_b19583217534"><em id="dcs-ug-0312010__en-us_topic_0148195243_i1795123212531">{redis_instance_address}</em></strong> <strong id="dcs-ug-0312010__en-us_topic_0148195243_b1059544195310">6379</strong> <strong id="dcs-ug-0312010__en-us_topic_0148195243_b1759514118539"><em id="dcs-ug-0312010__en-us_topic_0148195243_i759515415537">{password}</em></strong></p>
<p id="dcs-ug-0312010__en-us_topic_0148195243_p156153275218"><em id="dcs-ug-0312010__en-us_topic_0148195243_i105314303516">{redis_instance_address}</em> indicates the IP address/domain name of DCS instance and <span class="parmname" id="dcs-ug-0312010__en-us_topic_0148195243_parmname1653111302519"><b>6379</b></span> is an example port number of DCS instance. For details about how to obtain the IP address/domain name and port, see <a href="#dcs-ug-0312010__en-us_topic_0148195243_li1655151054317">1</a>. Change them as required. <em id="dcs-ug-0312010__en-us_topic_0148195243_i6461078717">{password}</em> indicates the password used to log in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.</p>
<p id="dcs-ug-0312010__en-us_topic_0148195243_p156153275218"><em id="dcs-ug-0312010__en-us_topic_0148195243_i213424919573">{redis_instance_address}</em> indicates the IP address/domain name of DCS instance and <span class="parmname" id="dcs-ug-0312010__en-us_topic_0148195243_parmname1113414985714"><b>6379</b></span> is an example port number of DCS instance. For details about how to obtain the IP address/domain name and port, see <a href="#dcs-ug-0312010__en-us_topic_0148195243_li1655151054317">1</a>. Change them as required. <em id="dcs-ug-0312010__en-us_topic_0148195243_i6461078717">{password}</em> indicates the password used to log in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.</p>
<p id="dcs-ug-0312010__en-us_topic_0148195243_p9507135912526">You have successfully accessed the instance if the following command output is displayed:</p>
<pre class="screen" id="dcs-ug-0312010__en-us_topic_0148195243_screen17216114885311">AUTH: OK
SET: OK

4
docs/dcs/umn/dcs-ug-0312011.html
View File

@ -20,7 +20,7 @@
</li></ol>
</li><li id="dcs-ug-0312011__en-us_topic_0148195287_li197821713135417">Use the redis-py client to connect to the instance. In the following steps, commands are executed in CLI mode. (Alternatively, write the commands into a Python script and then execute the script.)<ol class="substepthirdol" id="dcs-ug-0312011__en-us_topic_0148195287_ol157811213195418"><li id="dcs-ug-0312011__en-us_topic_0148195287_li1678121355410">Run the <strong id="dcs-ug-0312011__en-us_topic_0148195287_b14882210122012">python</strong> command to enter the CLI mode. You have entered CLI mode if the following command output is displayed:<div class="fignone" id="dcs-ug-0312011__en-us_topic_0148195287_fig01801119455"><span class="figcap"><b>Figure 2 </b>Entering the CLI mode</span><br><span><img id="dcs-ug-0312011__en-us_topic_0148195287_image21811612454" src="en-us_image_0000001187846598.png"></span></div>
</li><li id="dcs-ug-0312011__en-us_topic_0148195287_li278111135547">Run the following command to access the chosen DCS Redis instance:<pre class="screen" id="dcs-ug-0312011__en-us_topic_0148195287_screen127811013185412">r = redis.StrictRedis(host='XXX.XXX.XXX.XXX', port=6379, password='******');</pre>
<p id="dcs-ug-0312011__en-us_topic_0148195287_p97811713195417"><em id="dcs-ug-0312011__en-us_topic_0148195287_i734731905016">XXX.XXX.XXX.XXX</em> indicates the IP address/domain name of the DCS instance and <span class="parmname" id="dcs-ug-0312011__en-us_topic_0148195287_parmname1734719192503"><b>6379</b></span> is an example port number of the instance. For details about how to obtain the IP address/domain name and port, see <a href="#dcs-ug-0312011__en-us_topic_0148195287_li450593110588">1</a>. Change them as required. <em id="dcs-ug-0312011__en-us_topic_0148195287_i12054692453417">******</em> indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.</p>
<p id="dcs-ug-0312011__en-us_topic_0148195287_p97811713195417"><em id="dcs-ug-0312011__en-us_topic_0148195287_i131179547528">XXX.XXX.XXX.XXX</em> indicates the IP address/domain name of the DCS instance and <span class="parmname" id="dcs-ug-0312011__en-us_topic_0148195287_parmname211725410524"><b>6379</b></span> is an example port number of the instance. For details about how to obtain the IP address/domain name and port, see <a href="#dcs-ug-0312011__en-us_topic_0148195287_li450593110588">1</a>. Change them as required. <em id="dcs-ug-0312011__en-us_topic_0148195287_i12054692453417">******</em> indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.</p>
<p id="dcs-ug-0312011__en-us_topic_0148195287_p978151311545">You have successfully accessed the instance if the following command output is displayed. Enter commands to perform read and write operations on the database.</p>
<div class="fignone" id="dcs-ug-0312011__en-us_topic_0148195287_fig2367133024516"><span class="figcap"><b>Figure 3 </b>Redis connected successfully</span><br><span><img id="dcs-ug-0312011__en-us_topic_0148195287_image12368430124511" src="en-us_image_0000001233126245.png"></span></div>
</li></ol>
@ -30,7 +30,7 @@
</li><li id="dcs-ug-0312011__en-us_topic_0148195287_li5782413155410">Go to the directory where the decompressed redis-py-cluster package is saved, and install redis-py-cluster.<p id="dcs-ug-0312011__en-us_topic_0148195287_p978261315411"><a name="dcs-ug-0312011__en-us_topic_0148195287_li5782413155410"></a><a name="en-us_topic_0148195287_li5782413155410"></a><strong id="dcs-ug-0312011__en-us_topic_0148195287_b5782111314548">python setup.py install</strong></p>
</li></ol>
</li><li id="dcs-ug-0312011__en-us_topic_0148195287_li107821013145417">Access the DCS Redis instance by using redis-py-cluster.<p id="dcs-ug-0312011__en-us_topic_0148195287_p77821713115413"><a name="dcs-ug-0312011__en-us_topic_0148195287_li107821013145417"></a><a name="en-us_topic_0148195287_li107821013145417"></a>In the following steps, commands are executed in CLI mode. (Alternatively, write the commands into a Python script and then execute the script.)</p>
<ol class="substepthirdol" id="dcs-ug-0312011__en-us_topic_0148195287_ol878213139545"><li id="dcs-ug-0312011__en-us_topic_0148195287_li14782213155412">Run the <strong id="dcs-ug-0312011__en-us_topic_0148195287_b7245245">python</strong> command to enter the CLI mode.</li><li id="dcs-ug-0312011__en-us_topic_0148195287_li8782161314544">Run the following command to access the chosen DCS Redis instance. If the instance does not have a password, exclude <strong id="dcs-ug-0312011__en-us_topic_0148195287_b277142714469">password='******'</strong> from the command.<pre class="screen" id="dcs-ug-0312011__en-us_topic_0148195287_screen878218131542">&gt;&gt;&gt; from rediscluster import RedisCluster
<ol class="substepthirdol" id="dcs-ug-0312011__en-us_topic_0148195287_ol878213139545"><li id="dcs-ug-0312011__en-us_topic_0148195287_li14782213155412">Run the <strong id="dcs-ug-0312011__en-us_topic_0148195287_b272007465">python</strong> command to enter the CLI mode.</li><li id="dcs-ug-0312011__en-us_topic_0148195287_li8782161314544">Run the following command to access the chosen DCS Redis instance. If the instance does not have a password, exclude <strong id="dcs-ug-0312011__en-us_topic_0148195287_b277142714469">password='******'</strong> from the command.<pre class="screen" id="dcs-ug-0312011__en-us_topic_0148195287_screen878218131542">&gt;&gt;&gt; from rediscluster import RedisCluster
&gt;&gt;&gt; startup_nodes = [{"host": "192.168.0.143", "port": "6379"},{"host": "192.168.0.144", "port": "6379"},{"host": "192.168.0.145", "port": "6379"},{"host": "192.168.0.146", "port": "6379"}]

8
docs/dcs/umn/dcs-ug-0312012.html
View File

@ -26,7 +26,7 @@ var redis = new Redis({
port: 6379, // Redis port
host: '192.168.0.196', // Redis host
family: 4, // 4 (IPv4) or 6 (IPv6)
password: '<strong id="dcs-ug-0312012__en-us_topic_0148195323_b638213194253">******</strong>',
password: '******',
db: 0
});
redis.set('foo', 'bar');
@ -42,7 +42,7 @@ redis.sadd('set', 1, 3, 5, 7);
redis.sadd('set', [1, 3, 5, 7]);
// All arguments are passed directly to the redis server:
redis.set('key', 100, 'EX', 10);</pre>
<p id="dcs-ug-0312012__en-us_topic_0148195323_p1812329142415"><em id="dcs-ug-0312012__en-us_topic_0148195323_i17175194510533">host</em> indicates the example IP address/domain name of the DCS instance and <em id="dcs-ug-0312012__en-us_topic_0148195323_i1417584545315">port</em> indicates the port number of the DCS instance. For details about how to obtain the IP address/domain name and port, see <a href="#dcs-ug-0312012__en-us_topic_0148195323_li5233248151213">1</a>. Change them as required. <em id="dcs-ug-0312012__en-us_topic_0148195323_i1156036113716">******</em> indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.</p>
<p id="dcs-ug-0312012__en-us_topic_0148195323_p1812329142415"><em id="dcs-ug-0312012__en-us_topic_0148195323_i1675119102411">host</em> indicates the example IP address/domain name of the DCS instance and <em id="dcs-ug-0312012__en-us_topic_0148195323_i1075119104413">port</em> indicates the port number of the DCS instance. For details about how to obtain the IP address/domain name and port, see <a href="#dcs-ug-0312012__en-us_topic_0148195323_li5233248151213">1</a>. Change them as required. <em id="dcs-ug-0312012__en-us_topic_0148195323_i1156036113716">******</em> indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.</p>
</p></li><li id="dcs-ug-0312012__en-us_topic_0148195323_li20350145511811"><span>Run the sample script to access the chosen DCS instance.</span><p><p id="dcs-ug-0312012__en-us_topic_0148195323_p911264710250"><strong id="dcs-ug-0312012__en-us_topic_0148195323_b94441350152515">node ioredisdemo.js</strong></p>
</p></li></ol>
<p id="dcs-ug-0312012__en-us_topic_0148195323_p1987582762715"></p>
@ -66,7 +66,7 @@ var redis = new Redis({
port: 6379, // Redis port
host: '192.168.0.196', // Redis host
family: 4, // 4 (IPv4) or 6 (IPv6)
password: '<strong id="dcs-ug-0312012__en-us_topic_0148195323_b57041419299">******</strong>',
password: '******',
db: 0
});
redis.set('foo', 'bar');
@ -82,7 +82,7 @@ redis.sadd('set', 1, 3, 5, 7);
redis.sadd('set', [1, 3, 5, 7]);
// All arguments are passed directly to the redis server:
redis.set('key', 100, 'EX', 10);</pre>
<p id="dcs-ug-0312012__en-us_topic_0148195323_p89311292712"><em id="dcs-ug-0312012__en-us_topic_0148195323_i2064900155412">host</em> indicates the example IP address/domain name of the DCS instance and <em id="dcs-ug-0312012__en-us_topic_0148195323_i11649506547">port</em> indicates the port number of the DCS instance. For details about how to obtain the IP address/domain name and port, see <a href="#dcs-ug-0312012__en-us_topic_0148195323_li11511175651212">1</a>. Change them as required. <em id="dcs-ug-0312012__en-us_topic_0148195323_i20244152303816">******</em> indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.</p>
<p id="dcs-ug-0312012__en-us_topic_0148195323_p89311292712"><em id="dcs-ug-0312012__en-us_topic_0148195323_i13522637347">host</em> indicates the example IP address/domain name of the DCS instance and <em id="dcs-ug-0312012__en-us_topic_0148195323_i16523237749">port</em> indicates the port number of the DCS instance. For details about how to obtain the IP address/domain name and port, see <a href="#dcs-ug-0312012__en-us_topic_0148195323_li11511175651212">1</a>. Change them as required. <em id="dcs-ug-0312012__en-us_topic_0148195323_i20244152303816">******</em> indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.</p>
</p></li><li id="dcs-ug-0312012__en-us_topic_0148195323_li19108121232714"><span>Run the sample script to access the chosen DCS instance.</span><p><p id="dcs-ug-0312012__en-us_topic_0148195323_p191121512112715"><strong id="dcs-ug-0312012__en-us_topic_0148195323_b15114121202720">node ioredisdemo.js</strong></p>
</p></li></ol>
</div>

4
docs/dcs/umn/dcs-ug-0312013.html
View File

@ -17,7 +17,7 @@ namespace redisdemo
class Program
{
// redis config
private static ConfigurationOptions connDCS = ConfigurationOptions.Parse("<em id="dcs-ug-0312013__en-us_topic_0148195355_i1790854216517"><span style="color:#FF0000;">10.10</span><span style="color:#FF0000;">.38.233:6379</span></em>,password=<em id="dcs-ug-0312013__en-us_topic_0148195355_i16387125412511"><span style="color:#FF0000;">********</span></em>,connectTimeout=2000");
private static ConfigurationOptions connDCS = ConfigurationOptions.Parse("{instance_ip_address}:{port},password=********,connectTimeout=2000");
//the lock for singleton
private static readonly object Locker = new object();
//singleton
@ -50,7 +50,7 @@ namespace redisdemo
}
}
}</pre>
<p id="dcs-ug-0312013__en-us_topic_0148195355_p194285503418"><span style="color:#FF0000;">10.10</span><span style="color:#FF0000;">.38.233:6379</span> contains an example IP address/domain name and port number of the DCS Redis instance. For details about how to obtain the IP address/domain name and port, see <a href="#dcs-ug-0312013__en-us_topic_0148195355_li457118182512">1</a>. Change them as required. <em id="dcs-ug-0312013__en-us_topic_0148195355_i2098714542811">********</em> indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.</p>
<p id="dcs-ug-0312013__en-us_topic_0148195355_p194285503418"><em id="dcs-ug-0312013__en-us_topic_0148195355_i825144384814">{instance_ip_address}</em> and <em id="dcs-ug-0312013__en-us_topic_0148195355_i1556025814489">{port}</em> are the IP address/domain name and port number of the DCS Redis instance. For details about how to obtain the IP address/domain name and port, see <a href="#dcs-ug-0312013__en-us_topic_0148195355_li457118182512">1</a>. Change them as required. <em id="dcs-ug-0312013__en-us_topic_0148195355_i796615013">********</em> indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.</p>
</p></li><li id="dcs-ug-0312013__en-us_topic_0148195355_li117658171892"><span>Run the code. You have successfully accessed the instance if the following command output is displayed:</span><p><pre class="screen" id="dcs-ug-0312013__en-us_topic_0148195355_screen1365752211108">Hello, DCS for Redis!</pre>
<p id="dcs-ug-0312013__en-us_topic_0148195355_p1888616153105">For more information about other commands of StackExchange.Redis, visit <a href="https://stackexchange.github.io/StackExchange.Redis/" target="_blank" rel="noopener noreferrer">StackExchange.Redis</a>.</p>
</p></li></ol>

20
docs/dcs/umn/dcs-ug-0312016.html
View File

@ -77,26 +77,26 @@
</tr>
<tr id="dcs-ug-0312016__row1447352421112"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.5.2.1.2.4.1.1 "><p id="dcs-ug-0312016__p466130191118">Maintenance</p>
</td>
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.5.2.1.2.4.1.2 "><p id="dcs-ug-0312016__p106653018116">Time when maintenance takes place. To modify the time window, click the <span><img id="dcs-ug-0312016__image8940165011141" src="en-us_image_0000001572243777.png"></span> icon.</p>
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.5.2.1.2.4.1.2 "><p id="dcs-ug-0312016__p106653018116">Time when maintenance takes place. To modify the time window, click the <span><img id="dcs-ug-0312016__image1265791212186" src="en-us_image_0000001572243777.png"></span> icon.</p>
</td>
</tr>
<tr id="dcs-ug-0312016__row17220536183920"><td class="cellrowborder" rowspan="3" valign="top" width="15.663366336633663%" headers="mcps1.3.2.2.5.2.1.2.4.1.1 "><p id="dcs-ug-0312016__p824815241408">Connection</p>
<tr id="dcs-ug-0312016__row75414413312"><td class="cellrowborder" rowspan="3" valign="top" width="15.663366336633663%" headers="mcps1.3.2.2.5.2.1.2.4.1.1 "><p id="dcs-ug-0312016__p1853010211831">Connection</p>
</td>
<td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.2.2.5.2.1.2.4.1.2 "><p id="dcs-ug-0312016__p142486242400">Password Protected</p>
<td class="cellrowborder" valign="top" width="18%" headers="mcps1.3.2.2.5.2.1.2.4.1.2 "><p id="dcs-ug-0312016__p12244113112316">Password Protected</p>
</td>
<td class="cellrowborder" valign="top" width="66.33663366336634%" headers="mcps1.3.2.2.5.2.1.2.4.1.3 "><p id="dcs-ug-0312016__p02483244408">Currently, password-protected access and password-free access are supported.</p>
<td class="cellrowborder" valign="top" width="66.33663366336634%" headers="mcps1.3.2.2.5.2.1.2.4.1.3 "><p id="dcs-ug-0312016__p1724419311238">Currently, password-protected access and password-free access are supported.</p>
</td>
</tr>
<tr id="dcs-ug-0312016__row499455913911"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.5.2.1.2.4.1.1 "><p id="dcs-ug-0312016__p102486241408">Connection Address</p>
<tr id="dcs-ug-0312016__row161598131938"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.5.2.1.2.4.1.1 "><p id="dcs-ug-0312016__p1217714392314">Connection Address</p>
</td>
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.5.2.1.2.4.1.2 "><p id="dcs-ug-0312016__p62491124184012">Domain name and port number of the instance. You can click <span><img id="dcs-ug-0312016__image422815514154" src="en-us_image_0000001673542781.png"></span> to change the port.</p>
<div class="note" id="dcs-ug-0312016__note224992411407"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="dcs-ug-0312016__ul1424902418404"><li id="dcs-ug-0312016__li3249724114010">The instance has a domain name address if it was created after DCS has been interconnected with DNS. Instances created before the interconnection only have IP addresses and cannot be changed to domain name access.</li><li id="dcs-ug-0312016__li132491224124017">For a master/standby DCS Redis 4.0/5.0/6.0 instance, <strong id="dcs-ug-0312016__b1563975425617">Connection Address</strong> indicates the domain name and port number of the master node, and <strong id="dcs-ug-0312016__b1063915544566">Read-only Address</strong> indicates the domain name and port number of the standby node. When connecting to such an instance, you can use the domain name and port number of the master node or the standby node. For details, see <a href="CacheMasterSlave.html#CacheMasterSlave__section5805185095215">Architecture of Master/Standby DCS Redis 4.0/5.0/6.0 Instances</a>.</li><li id="dcs-ug-0312016__li1524912412409">You can change the port only for a DCS Redis 4.0/5.0/6.0 instance, but not for a DCS Redis 3.0 instance.</li></ul>
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.5.2.1.2.4.1.2 "><p id="dcs-ug-0312016__p617753917315">Domain name and port number of the instance. You can click <span><img id="dcs-ug-0312016__image31779391935" src="en-us_image_0000001805332909.png"></span> to change the port.</p>
<div class="note" id="dcs-ug-0312016__note1117710396318"><span class="notetitle"> NOTE: </span><div class="notebody"><ul id="dcs-ug-0312016__ul21774393318"><li id="dcs-ug-0312016__li1417763910317">The instance has a domain name address if it was created after DCS has been interconnected with DNS. Instances created before the interconnection only have IP addresses and cannot be changed to domain name access.</li><li id="dcs-ug-0312016__li1717716391139">For a master/standby DCS Redis 4.0 and later instance, <strong id="dcs-ug-0312016__b10189133495318">Connection Address</strong> indicates the domain name and port number of the master node, and <strong id="dcs-ug-0312016__b4190934105312">Read-only Address</strong> indicates the domain name and port number of the standby node. When connecting to such an instance, you can use the domain name and port number of the master node or the standby node. For details, see <a href="CacheMasterSlave.html#CacheMasterSlave__section5805185095215">Architecture of Master/Standby DCS Redis 4.0/5.0/6.0 Instances</a>.</li><li id="dcs-ug-0312016__li17177539536">You can change the port only for a DCS Redis 4.0 and later instance, but not for a DCS Redis 3.0 instance.</li></ul>
</div></div>
</td>
</tr>
<tr id="dcs-ug-0312016__row383010444014"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.5.2.1.2.4.1.1 "><p id="dcs-ug-0312016__p7250172464015">IP Address</p>
<tr id="dcs-ug-0312016__row1554017161334"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.5.2.1.2.4.1.1 "><p id="dcs-ug-0312016__p26492044439">IP Address</p>
</td>
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.5.2.1.2.4.1.2 "><p id="dcs-ug-0312016__p225082424011">IP address and port number of the chosen instance.</p>
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.5.2.1.2.4.1.2 "><p id="dcs-ug-0312016__p1064914441930">IP address and port number of the chosen instance.</p>
</td>
</tr>
<tr id="dcs-ug-0312016__row148811951194416"><td class="cellrowborder" rowspan="4" valign="top" width="15.663366336633663%" headers="mcps1.3.2.2.5.2.1.2.4.1.1 "><p id="dcs-ug-0312016__p198815515446">Network</p>
@ -119,7 +119,7 @@
<tr id="dcs-ug-0312016__row148814519447"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.5.2.1.2.4.1.1 "><p id="dcs-ug-0312016__p20881951144415">Security Group</p>
</td>
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.5.2.1.2.4.1.2 "><p id="dcs-ug-0312016__p18881951194418">Security group that controls access to the DCS instance. To modify the security group, click <span><img id="dcs-ug-0312016__image11197133218508" src="en-us_image_0000001318437462.png"></span>.</p>
<p id="dcs-ug-0312016__p1088118518442">This parameter is displayed only for DCS Redis 3.0 instances. DCS for Redis 4.0/5.0/6.0 are based on VPC Endpoint and do not support security groups. You can click <strong id="dcs-ug-0312016__b86664915818">configure the whitelist</strong> to configure the whitelist.</p>
<p id="dcs-ug-0312016__p1088118518442">This parameter is displayed only for DCS Redis 3.0 instances. DCS for Redis 4.0/5.0/6.0 are based on VPC Endpoint and do not support security groups. You can click <strong id="dcs-ug-0312016__b13653341144511">configure</strong> to configure the whitelist.</p>
</td>
</tr>
</tbody>

2
docs/dcs/umn/dcs-ug-0312019.html
View File

@ -2,7 +2,7 @@
<h1 class="topictitle1">Exporting DCS Instance List</h1>
<div id="body8662426"><p id="dcs-ug-0312019__en-us_topic_0148195274_p9403691116">On the DCS console, you can export DCS instance information in full to an Excel file.</p>
<div class="section" id="dcs-ug-0312019__en-us_topic_0148195274_section1871533122711"><h4 class="sectiontitle">Procedure</h4><ol id="dcs-ug-0312019__en-us_topic_0148195274_ol15486424193825"><li id="dcs-ug-0312019__li1799392835619"><span>Log in to the DCS console.</span></li><li id="dcs-ug-0312019__li15784033165410"><span>Click <span><img id="dcs-ug-0312019__image778483345419" src="en-us_image_0000001194403155.png"></span> in the upper left corner and select a region and a project.</span></li><li id="dcs-ug-0312019__li18411387341"><span>In the navigation pane, choose <strong id="dcs-ug-0312019__b210116613577">Cache Manager</strong>.</span></li><li id="dcs-ug-0312019__en-us_topic_0148195274_li18644454193825"><span>Click <span><img id="dcs-ug-0312019__image654981614564" src="en-us_image_0266235403.png"></span> above the instance list.</span></li></ol>
<div class="section" id="dcs-ug-0312019__en-us_topic_0148195274_section1871533122711"><h4 class="sectiontitle">Procedure</h4><ol id="dcs-ug-0312019__en-us_topic_0148195274_ol15486424193825"><li id="dcs-ug-0312019__li1799392835619"><span>Log in to the DCS console.</span></li><li id="dcs-ug-0312019__li15784033165410"><span>Click <span><img id="dcs-ug-0312019__image778483345419" src="en-us_image_0000001194403155.png"></span> in the upper left corner and select a region and a project.</span></li><li id="dcs-ug-0312019__li18411387341"><span>In the navigation pane, choose <strong id="dcs-ug-0312019__b210116613577">Cache Manager</strong>.</span></li><li id="dcs-ug-0312019__en-us_topic_0148195274_li18644454193825"><span>Click <strong id="dcs-ug-0312019__b17708183913216">Import</strong> above the instance list to export the DCS instance list.</span></li></ol>
</div>
</div>
<div>

6
docs/dcs/umn/dcs-ug-0312037.html
View File

@ -5,7 +5,7 @@
<p id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_p542904425717">Simply download the source Redis backup data and then upload the data to an OBS bucket in the same region as the target DCS Redis instance. After you have created a migration task on the DCS console, DCS will read data from the OBS bucket and data will be migrated to the target instance.</p>
<p id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_p19560545183013">.aof, .rbb, .zip, and .tar.gz files can be uploaded to OBS buckets. You can directly upload .aof and .rdb files or compress them into .zip or .tar.gz files before uploading.</p>
</div>
<div class="section" id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_section393611177"><h4 class="sectiontitle">Prerequisites</h4><ul id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_ul6904185261112"><li id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li883710301127">The OBS bucket must be in the same region as the target DCS Redis instance.</li><li id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li923118413317">The data files to be uploaded must be in the .aof, .rdb, .zip, or .tar.gz format.</li><li id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li64753803210">To migrate data from a single-node or master/standby Redis instance of other cloud vendors, create a backup task and download the backup file.</li><li id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li12471738123211">To migrate data from a cluster Redis instance of other cloud vendors, download all backup files and upload all of them to the OBS bucket. Each backup file contains data for a shard of the instance.</li><li id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li174818383321">Redis Cluster instances only support .rdb files and do not support .aof files.</li></ul>
<div class="section" id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_section393611177"><h4 class="sectiontitle">Prerequisites</h4><ul id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_ul6904185261112"><li id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li883710301127">The OBS bucket must be in the same region as the target DCS Redis instance.</li><li id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li923118413317">The data files to be uploaded must be in .aof, .rdb, .zip, or .tar.gz formats. .zip files must contain .aof or .rdb files.</li><li id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li64753803210">To migrate data from a single-node or master/standby Redis instance of other cloud vendors, create a backup task and download the backup file.</li><li id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li12471738123211">To migrate data from a cluster Redis instance of other cloud vendors, download all backup files and upload all of them to the OBS bucket. Each backup file contains data for a shard of the instance.</li><li id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li174818383321">Redis Cluster instances only support .rdb files and do not support .aof files.</li></ul>
</div>
<div class="section" id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_section1128152020384"><a name="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_section1128152020384"></a><a name="en-us_topic_0179456697_dcs-migration-190703002_section1128152020384"></a><h4 class="sectiontitle">Step 1: Prepare the Target DCS Redis Instance</h4><ul id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_ul727834515383"><li id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li1527810451382">If a DCS Redis instance is not available, create one first. For details, see <a href="dcs-ug-0326008.html">Creating a DCS Redis Instance</a>.</li><li id="dcs-ug-0312037__li42726204220">If a DCS Redis instance is available, you do not need to create a new one. However, you can clear the instance data before the migration.<ul id="dcs-ug-0312037__ul16630325162217"><li id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li5270324091">If the target instance is Redis 4.0 and later, clear the data by referring to <a href="dcs-ug-0312018.html">Clearing DCS Instance Data</a>.</li><li id="dcs-ug-0312037__li1216630112218">If the target instance is a DCS Redis 3.0 instance, run the <strong id="dcs-ug-0312037__b115883217235">FLUSHALL</strong> command to clear data.</li><li id="dcs-ug-0312037__li16806101893415">If the target instance data is not cleared before the migration and the source and target instances contain the same key, the key in the target instance will be overwritten by the key in the source instance after the migration.</li></ul>
</li><li id="dcs-ug-0312037__li1673321154119">Redis is backward compatible. The target instance version must be the same as or later than the source instance version.</li></ul>
@ -20,9 +20,9 @@
</li><li id="dcs-ug-0312037__li11225208162112">Install OBS Browser+.<p id="dcs-ug-0312037__p1022518842111"><a name="dcs-ug-0312037__li11225208162112"></a><a name="li11225208162112"></a>For details, see section "Installing OBS Browser+" in <em id="dcs-ug-0312037__i118557531214">Object Storage Service (OBS) Tools Guide (OBS Browser+)</em>.</p>
</li><li id="dcs-ug-0312037__li201961913103814">Log in to OBS Browser+.<p id="dcs-ug-0312037__p1119621313811"><a name="dcs-ug-0312037__li201961913103814"></a><a name="li201961913103814"></a>For details, see section "Logging In to OBS Browser+" in <em id="dcs-ug-0312037__i104881711215">Object Storage Service (OBS) Tools Guide (OBS Browser+)</em>.</p>
</li><li id="dcs-ug-0312037__li144125145718">Create a bucket.</li><li id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li10948943114817">Upload backup data.</li></ol>
</p></li><li id="dcs-ug-0312037__li8307135965315"><a name="dcs-ug-0312037__li8307135965315"></a><a name="li8307135965315"></a><span>On the OBS console, upload the backup data files to the OBS bucket.</span><p><div class="p" id="dcs-ug-0312037__p73071659115311">Perform the following steps if the backup file size does not exceed 5 GB:<ol type="a" id="dcs-ug-0312037__ol17307059105315"><li id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li11425644112117">In the bucket list, click the name of the created bucket.</li><li id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li6425134472111">In the navigation pane, choose <strong id="dcs-ug-0312037__b2037028687">Objects</strong>.</li><li id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li8425844162114">On the <strong id="dcs-ug-0312037__b2088588249">Objects</strong> tab page, click <strong id="dcs-ug-0312037__b1409091267">Upload Object</strong>.</li><li id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li4601227114516">Upload the objects.<p id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_p2092314104615"><a name="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li4601227114516"></a><a name="en-us_topic_0179456697_dcs-migration-190703002_li4601227114516"></a>To upload objects, drag files or folders to the <strong id="dcs-ug-0312037__b1459915347">Upload Object</strong> area or click <strong id="dcs-ug-0312037__b1648442873">add file</strong>. A maximum of 100 files can be uploaded at a time. The total size cannot exceed 5 GB.</p>
</p></li><li id="dcs-ug-0312037__li8307135965315"><a name="dcs-ug-0312037__li8307135965315"></a><a name="li8307135965315"></a><span>On the OBS console, upload the backup data files to the OBS bucket.</span><p><div class="p" id="dcs-ug-0312037__p73071659115311">Perform the following steps if the backup file size does not exceed 5 GB:<ol type="a" id="dcs-ug-0312037__ol17307059105315"><li id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li11425644112117">In the bucket list, click the name of the created bucket.</li><li id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li6425134472111">In the navigation pane, choose <strong id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_b7335667220">Objects</strong>.</li><li id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li8425844162114">On the <strong id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_b1434535111128">Objects</strong> tab page, click <strong id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_b8346251131216">Upload Object</strong>.</li><li id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li4601227114516">Upload the objects.<p id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_p2092314104615"><a name="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_li4601227114516"></a><a name="en-us_topic_0179456697_dcs-migration-190703002_li4601227114516"></a>To upload objects, drag files or folders to the <strong id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_b1466016717292">Upload Object</strong> area or click <strong id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_b13375203619291">add file</strong>. A maximum of 100 files can be uploaded at a time. The total size cannot exceed 5 GB.</p>
<div class="fignone" id="dcs-ug-0312037__fig184786179256"><span class="figcap"><b>Figure 1 </b>Uploading an object</span><br><span><img id="dcs-ug-0312037__image174788172258" src="en-us_image_0000001634759086.png"></span></div>
</li><li id="dcs-ug-0312037__li29854713516">(Optional) Select <strong id="dcs-ug-0312037__b859379742">KMS encryption</strong> to encrypt the file you want to upload.</li><li id="dcs-ug-0312037__li103071459205315">Click <strong id="dcs-ug-0312037__b2373124572710">Upload</strong>.</li></ol>
</li><li id="dcs-ug-0312037__li29854713516">(Optional) Select <strong id="dcs-ug-0312037__en-us_topic_0179456697_dcs-migration-190703002_b418982912617">KMS encryption</strong> to encrypt the file you want to upload.</li><li id="dcs-ug-0312037__li103071459205315">Click <strong id="dcs-ug-0312037__b2373124572710">Upload</strong>.</li></ol>
</div>
</p></li></ol>
</div>

2
docs/dcs/umn/dcs-ug-0326008.html
View File

@ -31,7 +31,7 @@
<div class="note" id="dcs-ug-0326008__note18162172918129"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="dcs-ug-0326008__ul14162192910120"><li id="dcs-ug-0326008__li11162629121217">On the instance creation page, the default parameter templates are used by default.</li><li id="dcs-ug-0326008__li181621929131217">If you use a custom template, the selected cache engine version and instance type must match those of the template. For details about using custom templates, see <a href="dcs-ug-210622003.html">Creating a Custom Parameter Template</a>.</li></ul>
</div></div>
</p></li><li id="dcs-ug-0326008__li0286162163410"><span>Choose whether to enable <strong id="dcs-ug-0326008__b926321130104046">Auto Backup</strong>.</span><p><p id="dcs-ug-0326008__p155051937173912">This parameter is displayed only when the instance type is master/standby or cluster. For more information on how to configure a backup policy, see <a href="en-us_topic_0079835992.html">Overview</a>.</p>
</p></li><li id="dcs-ug-0326008__li129684814373"><span>Specify the number of instances to create.</span></li><li id="dcs-ug-0326008__li1140718109251"><span>Enter an instance name.</span><p><p id="dcs-ug-0326008__p1292391182512">The value of <strong id="dcs-ug-0326008__b468619155415">Name</strong> contains at least 4 characters. When you create multiple instances at a time, the instances are named in the format of <em id="dcs-ug-0326008__i446519298">custom name</em>-<em id="dcs-ug-0326008__i464784000">n</em>, where <em id="dcs-ug-0326008__i1181994991">n</em> starts from 000 and is incremented by 1. For example, if you create two instances and set <strong id="dcs-ug-0326008__b1309860370">name</strong> to <strong id="dcs-ug-0326008__b1236914245">dcs_demo</strong>, the two instances are respectively named as <strong id="dcs-ug-0326008__b1711167130">dcs_demo-000</strong> and <strong id="dcs-ug-0326008__b1949698889">dcs_demo-001</strong>.</p>
</p></li><li id="dcs-ug-0326008__li129684814373"><span>Specify the number of instances to create.</span></li><li id="dcs-ug-0326008__li1140718109251"><span>Enter an instance name.</span><p><p id="dcs-ug-0326008__p1292391182512">The value of <strong id="dcs-ug-0326008__b468619155415">Name</strong> contains at least 4 characters. When you create multiple instances at a time, the instances are named in the format of <em id="dcs-ug-0326008__i513762292">custom name</em>-<em id="dcs-ug-0326008__i2020788548">n</em>, where <em id="dcs-ug-0326008__i760637260">n</em> starts from 000 and is incremented by 1. For example, if you create two instances and set <strong id="dcs-ug-0326008__b281007785">name</strong> to <strong id="dcs-ug-0326008__b1171302407">dcs_demo</strong>, the two instances are respectively named as <strong id="dcs-ug-0326008__b181063473">dcs_demo-000</strong> and <strong id="dcs-ug-0326008__b547719720">dcs_demo-001</strong>.</p>
</p></li><li id="dcs-ug-0326008__en-us_topic_0148195251_li17647455231"><span>Click <strong id="dcs-ug-0326008__b10377134733720">More Settings</strong> to configure more parameters.</span><p><ol type="a" id="dcs-ug-0326008__en-us_topic_0148195251_ol179711225192412"><li id="dcs-ug-0326008__en-us_topic_0148195251_li62791011023">Enter a description of the instance.</li><li id="dcs-ug-0326008__en-us_topic_0148195251_li818212588436">Rename critical commands.<p id="dcs-ug-0326008__en-us_topic_0148195251_p12671823144417"><a name="dcs-ug-0326008__en-us_topic_0148195251_li818212588436"></a><a name="en-us_topic_0148195251_li818212588436"></a><strong id="dcs-ug-0326008__b186511426557">Command Renaming</strong> is displayed for Redis 4.0 and later. Currently, you can only rename the <strong id="dcs-ug-0326008__b161858514525">COMMAND</strong>, <strong id="dcs-ug-0326008__b61857514526">KEYS</strong>, <strong id="dcs-ug-0326008__b1118517517526">FLUSHDB</strong>, <strong id="dcs-ug-0326008__b1818525145215">FLUSHALL</strong>, <strong id="dcs-ug-0326008__b10185851155219">HGETALL</strong>, <strong id="dcs-ug-0326008__b118525155210">SCAN</strong>, <strong id="dcs-ug-0326008__b1718516515521">HSCAN</strong>, <strong id="dcs-ug-0326008__b1418675112524">SSCAN</strong>, and <strong id="dcs-ug-0326008__b31861351155215">ZSCAN</strong> commands.</p>
</li><li id="dcs-ug-0326008__en-us_topic_0148195251_li14520142518376">Specify the maintenance window.<p id="dcs-ug-0326008__en-us_topic_0148195251_p9703134155218"><a name="dcs-ug-0326008__en-us_topic_0148195251_li14520142518376"></a><a name="en-us_topic_0148195251_li14520142518376"></a>Choose a window for DCS O&amp;M personnel to perform maintenance on your instance. You will be contacted before any maintenance activities are performed.</p>
</li></ol>

13
docs/dcs/umn/dcs-ug-0326009.html
View File

@ -2,14 +2,13 @@
<h1 class="topictitle1">Accessing a DCS Redis Instance Through redis-cli</h1>
<div id="body8662426"><p id="dcs-ug-0326009__en-us_topic_0148195299_p1484772321512">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 <a href="https://redis.io/clients" target="_blank" rel="noopener noreferrer">https://redis.io/clients</a>.</p>
<div class="note" id="dcs-ug-0326009__en-us_topic_0148195299_note1453731713365"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="dcs-ug-0326009__ul8962185915398"><li id="dcs-ug-0326009__li149621059133917">Redis 3.0 does not support port customization and allows only port 6379. For Redis 4.0 and later, you can specify a port or use the default port 6379. The following uses the default port 6379. If you have specified a port, replace 6379 with the actual port.</li><li id="dcs-ug-0326009__li2806183095918"><strong id="dcs-ug-0326009__b72961117192618">When connecting to a Redis Cluster instance, ensure that </strong><strong id="dcs-ug-0326009__b1619020329011">-c</strong><strong id="dcs-ug-0326009__b2029613175269"> is added to the command.</strong> Otherwise, the connection will fail.<ul id="dcs-ug-0326009__ul67372059239"><li id="dcs-ug-0326009__li169104495318">Run the following command to connect to a Redis Cluster instance:<p id="dcs-ug-0326009__p1912912161917"><a name="dcs-ug-0326009__li169104495318"></a><a name="li169104495318"></a>./redis-cli -h<em id="dcs-ug-0326009__i118417013585"> {dcs_instance_address}</em> -p <em id="dcs-ug-0326009__i11594334112">6379</em> -a<em id="dcs-ug-0326009__i156371358588"> {password}</em> <strong id="dcs-ug-0326009__b1149122112415">-c</strong></p>
</li><li id="dcs-ug-0326009__li1628062748">Run the following command to connect to a single-node, master/standby, or Proxy Cluster instance:<p id="dcs-ug-0326009__p191948221115"><a name="dcs-ug-0326009__li1628062748"></a><a name="li1628062748"></a><em id="dcs-ug-0326009__i4147461213">./redis-cli -h</em> <em id="dcs-ug-0326009__i11207131615412">{dcs_instance_address} -p 6379</em> -a<em id="dcs-ug-0326009__i868741111589"> {password}</em></p>
<div class="note" id="dcs-ug-0326009__en-us_topic_0148195299_note1453731713365"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ul id="dcs-ug-0326009__ul8962185915398"><li id="dcs-ug-0326009__li149621059133917">Redis 3.0 does not support port customization and allows only port 6379. For Redis 4.0 and later, you can specify a port or use the default port 6379. The following uses the default port 6379. If you have specified a port, replace 6379 with the actual port.</li><li id="dcs-ug-0326009__li2806183095918"><strong id="dcs-ug-0326009__b72961117192618">When connecting to a Redis Cluster instance, ensure that </strong><strong id="dcs-ug-0326009__b1619020329011">-c</strong><strong id="dcs-ug-0326009__b2029613175269"> is added to the command.</strong> Otherwise, the connection will fail.<ul id="dcs-ug-0326009__ul67372059239"><li id="dcs-ug-0326009__li169104495318">Run the following command to connect to a Redis Cluster instance:<p id="dcs-ug-0326009__p1912912161917"><a name="dcs-ug-0326009__li169104495318"></a><a name="li169104495318"></a>./redis-cli -h <em id="dcs-ug-0326009__i6511348182514">{dcs_instance_address}</em> -p <em id="dcs-ug-0326009__i11594334112">6379</em> -a <em id="dcs-ug-0326009__i9859534152413">{password}</em> <strong id="dcs-ug-0326009__b1149122112415">-c</strong></p>
</li><li id="dcs-ug-0326009__li1628062748">Run the following command to connect to a single-node, master/standby, or Proxy Cluster instance:<p id="dcs-ug-0326009__p191948221115"><a name="dcs-ug-0326009__li1628062748"></a><a name="li1628062748"></a><em id="dcs-ug-0326009__i4147461213">./redis-cli -h</em> <em id="dcs-ug-0326009__i11207131615412">{dcs_instance_address} -p 6379</em> -a <em id="dcs-ug-0326009__i11516104913240">{password}</em></p>
</li></ul>
<p id="dcs-ug-0326009__p148921956417">For details, see <a href="#dcs-ug-0326009__en-us_topic_0148195299_li1511472544119">3</a> and <a href="#dcs-ug-0326009__en-us_topic_0148195299_li126171140194317">4</a>.</p>
</li><li id="dcs-ug-0326009__li179872127317">If SSL is enabled for a single-node or master/standby DCS Redis 6.0 instance, set an SSL certificate path.<p id="dcs-ug-0326009__p1489510020592"><a name="dcs-ug-0326009__li179872127317"></a><a name="li179872127317"></a><em id="dcs-ug-0326009__i198891801252">./redis-cli -h</em> <em id="dcs-ug-0326009__i13889190954">{dcs_instance_address} -p 6379</em> -a<em id="dcs-ug-0326009__i17889505519"> {password}</em> <strong id="dcs-ug-0326009__b7144113615613">--tls --cacert <em id="dcs-ug-0326009__i32144615616">{</em><em id="dcs-ug-0326009__i02141612614">certification file path}</em></strong></p>
</li><li id="dcs-ug-0326009__li785620464118">If SSL is enabled for a Redis Cluster DCS Redis 6.0 instance, set a certificate path.<p id="dcs-ug-0326009__p124915335592"><a name="dcs-ug-0326009__li785620464118"></a><a name="li785620464118"></a>./redis-cli -h<em id="dcs-ug-0326009__i118881801452"> {dcs_instance_address}</em> -p <em id="dcs-ug-0326009__i8344115719107">6379</em> -a<em id="dcs-ug-0326009__i108891001551"> {password}</em> -c <strong id="dcs-ug-0326009__b65038271366">--tls --cacert <em id="dcs-ug-0326009__i2204184319110">{</em><em id="dcs-ug-0326009__i720418431918">certification file path}</em></strong></p>
</li><li id="dcs-ug-0326009__li51841453425">To connect to Redis with SSL encryption, use redis-cli 6.x or later.<p id="dcs-ug-0326009__p18189553523"><a name="dcs-ug-0326009__li51841453425"></a><a name="li51841453425"></a></p>
</li></ul>
</li><li id="dcs-ug-0326009__li51841453425">To connect to Redis with SSL encryption, use redis-cli 6.x or later.</li></ul>
</div></div>
<div class="section" id="dcs-ug-0326009__en-us_topic_0148195299_section1502270695932"><h4 class="sectiontitle">Prerequisites</h4><ul id="dcs-ug-0326009__en-us_topic_0148195299_ul46828691102415"><li id="dcs-ug-0326009__en-us_topic_0148195299_li7215915117">The DCS Redis instance you want to access is in the <strong id="dcs-ug-0326009__en-us_topic_0148195299_b4219617173719">Running</strong> state.</li><li id="dcs-ug-0326009__en-us_topic_0148195299_li132154114111">An ECS has been created. For more information on how to create ECSs, see the <a href="https://docs.otc.t-systems.com/en-us/usermanual/ecs/en-us_topic_0163572588.html" target="_blank" rel="noopener noreferrer">Elastic Cloud Server User Guide</a>.</li><li id="dcs-ug-0326009__en-us_topic_0148195299_li152161914112">If the ECS runs the Linux OS, ensure that the GCC compilation environment has been installed on the ECS.</li></ul>
</div>
@ -25,11 +24,11 @@
</li></ol>
</p></li><li id="dcs-ug-0326009__en-us_topic_0148195299_li1511472544119"><a name="dcs-ug-0326009__en-us_topic_0148195299_li1511472544119"></a><a name="en-us_topic_0148195299_li1511472544119"></a><span>Access a DCS instance of a type other than Redis Cluster.</span><p><p id="dcs-ug-0326009__en-us_topic_0148195299_p10196194418415">Perform the following procedure to access a single-node, master/standby instance.</p>
<p id="dcs-ug-0326009__p112171018503">./redis-cli -h ${dcs_instance_address} -p 6379 -a ${password}</p>
<div class="note" id="dcs-ug-0326009__note1721191325012"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ol type="a" id="dcs-ug-0326009__ol158735372514"><li id="dcs-ug-0326009__li4587753132516">If the instance is password-free, connect it by running the<strong id="dcs-ug-0326009__b1821551022715"> ./redis-cli -h </strong><em id="dcs-ug-0326009__i42159103276">${dcs_instance_address}</em><strong id="dcs-ug-0326009__b6215181017279"> -p 6379</strong> command.</li><li id="dcs-ug-0326009__li125871253192518">If the instance is password-protected, connect it by running the <strong id="dcs-ug-0326009__b5569165119395">./redis-cli -h </strong><em id="dcs-ug-0326009__i1050845013391">${dcs_instance_address}</em><strong id="dcs-ug-0326009__b937895917393"> -p 6379 -a </strong><em id="dcs-ug-0326009__i680915903914">${password}</em> command.</li><li id="dcs-ug-0326009__li11509414718"><em id="dcs-ug-0326009__i59691822105317">{dcs_instance_address}</em> can be the <strong id="dcs-ug-0326009__b1344010129255">Connection Address</strong> (domain name) or <strong id="dcs-ug-0326009__b1530015922414">IP Address</strong>. <a href="dcs-faq-022025.html">Should I Use a Domain Name or an IP Address to Connect to a DCS Redis Instance?</a><p id="dcs-ug-0326009__p2172132910101"><span><img id="dcs-ug-0326009__image1917232913100" src="en-us_image_0000001538860065.png"></span></p>
<div class="note" id="dcs-ug-0326009__note1721191325012"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><ol type="a" id="dcs-ug-0326009__ol158735372514"><li id="dcs-ug-0326009__li4587753132516">If the instance is password-free, connect it by running the<strong id="dcs-ug-0326009__b1821551022715"> ./redis-cli -h </strong><em id="dcs-ug-0326009__i42159103276">${dcs_instance_address}</em><strong id="dcs-ug-0326009__b6215181017279"> -p 6379</strong> command.</li><li id="dcs-ug-0326009__li125871253192518">If the instance is password-protected, connect it by running the <strong id="dcs-ug-0326009__b5569165119395">./redis-cli -h </strong><em id="dcs-ug-0326009__i1050845013391">${dcs_instance_address}</em><strong id="dcs-ug-0326009__b937895917393"> -p 6379 -a </strong><em id="dcs-ug-0326009__i680915903914">${password}</em> command.</li><li id="dcs-ug-0326009__li11509414718"><em id="dcs-ug-0326009__i59691822105317">{dcs_instance_address}</em> can be the <strong id="dcs-ug-0326009__b1344010129255">Connection Address</strong> (domain name) or <strong id="dcs-ug-0326009__b1530015922414">IP Address</strong>. For details, see <a href="dcs-faq-022025.html">Should I Use Domain Name or IP Address to Connect to a Redis Instance?</a>.<p id="dcs-ug-0326009__p2172132910101"><span><img id="dcs-ug-0326009__image1917232913100" src="en-us_image_0000001538860065.png"></span></p>
</li></ol>
</div></div>
</p></li><li id="dcs-ug-0326009__en-us_topic_0148195299_li126171140194317"><a name="dcs-ug-0326009__en-us_topic_0148195299_li126171140194317"></a><a name="en-us_topic_0148195299_li126171140194317"></a><span>Access a DCS instance of the Redis Cluster type.</span><p><p id="dcs-ug-0326009__en-us_topic_0148195299_p106170401437">Perform the following procedure to access a DCS Redis 4.0 or 5.0 instance in Redis Cluster type.</p>
<ol type="a" id="dcs-ug-0326009__en-us_topic_0148195299_ol19617184018436"><li id="dcs-ug-0326009__en-us_topic_0148195299_li461774013434">Run the following commands to access the chosen DCS Redis instance:<p id="dcs-ug-0326009__en-us_topic_0148195299_p1943564413440"><a name="dcs-ug-0326009__en-us_topic_0148195299_li461774013434"></a><a name="en-us_topic_0148195299_li461774013434"></a><strong id="dcs-ug-0326009__en-us_topic_0148195299_b105815143619">./redis-cli -h {dcs_instance_address} -p 6379 -a {password} -c</strong></p>
</p></li><li id="dcs-ug-0326009__en-us_topic_0148195299_li126171140194317"><a name="dcs-ug-0326009__en-us_topic_0148195299_li126171140194317"></a><a name="en-us_topic_0148195299_li126171140194317"></a><span>Access a DCS instance of the Redis Cluster type.</span><p><p id="dcs-ug-0326009__en-us_topic_0148195299_p106170401437">Do as follows to access a Redis Cluster instance:</p>
<ol type="a" id="dcs-ug-0326009__en-us_topic_0148195299_ol19617184018436"><li id="dcs-ug-0326009__en-us_topic_0148195299_li461774013434">Run the following commands to access the chosen DCS Redis instance:<p id="dcs-ug-0326009__en-us_topic_0148195299_p1943564413440"><a name="dcs-ug-0326009__en-us_topic_0148195299_li461774013434"></a><a name="en-us_topic_0148195299_li461774013434"></a><strong id="dcs-ug-0326009__en-us_topic_0148195299_b105815143619">./redis-cli -h <em id="dcs-ug-0326009__i17352264516">{dcs_instance_address}</em> -p 6379 -a <em id="dcs-ug-0326009__i89107302459">{password}</em> -c</strong></p>
<p id="dcs-ug-0326009__en-us_topic_0148195299_p1561884084317"><em id="dcs-ug-0326009__i10720151231517">{dcs_instance_address}</em> indicates the IP address/domain name of the DCS Redis instance, <span class="parmname" id="dcs-ug-0326009__parmname372191211155"><b>6379</b></span> is the port used for accessing the instance, <em id="dcs-ug-0326009__i1272151291519">{password}</em> is the password of the instance, and <strong id="dcs-ug-0326009__b197211712131514">-c</strong> is used for accessing Redis Cluster nodes. The IP address/domain name and port number are obtained in <a href="#dcs-ug-0326009__en-us_topic_0148195299_li5799181918288">1</a>.</p>
<div class="p" id="dcs-ug-0326009__p207814105325">Example:<pre class="screen" id="dcs-ug-0326009__en-us_topic_0148195299_screen121171038171515">root@ecs-redis:~/redis-6.2.13/src# ./redis-cli -h 192.168.0.85 -p 6379 -a ****** -c
192.168.0.85:6379&gt; </pre>

38
docs/dcs/umn/dcs-ug-0326019.html
View File

File diff suppressed because it is too large Load Diff

Some files were not shown because too many files have changed in this diff Show More