From 70ca474258565887abe9132977042ef4f66fba96 Mon Sep 17 00:00:00 2001 From: chenjunjie Date: Tue, 25 Mar 2025 10:52:26 +0000 Subject: [PATCH] DCS UMN 20250314 version Reviewed-by: Liudmila Denisova Co-authored-by: chenjunjie Co-committed-by: chenjunjie --- docs/dcs/umn/ALL_META.TXT.json | 2 +- docs/dcs/umn/CLASS.TXT.json | 2 +- docs/dcs/umn/CacheCluster.html | 6 +- docs/dcs/umn/dcs-pd-0220606.html | 2 +- docs/dcs/umn/dcs-pd-0916002.html | 10 +- docs/dcs/umn/dcs-pd-0916004.html | 1507 +++++++++++++++++++----- docs/dcs/umn/dcs-pd-190826001.html | 69 +- docs/dcs/umn/dcs-pd-191224001.html | 4 +- docs/dcs/umn/dcs-pd-210209002.html | 1715 +++++++++++++++++++++++++++- docs/dcs/umn/dcs-ug-0312008.html | 2 +- docs/dcs/umn/dcs-ug-0312040.html | 2 +- docs/dcs/umn/dcs-ug-0326008.html | 2 +- docs/dcs/umn/dcs-ug-1009001.html | 4 +- docs/dcs/umn/dcs-ug-211105002.html | 14 +- 14 files changed, 3040 insertions(+), 301 deletions(-) diff --git a/docs/dcs/umn/ALL_META.TXT.json b/docs/dcs/umn/ALL_META.TXT.json index c5953c9e1..bf8073b77 100644 --- a/docs/dcs/umn/ALL_META.TXT.json +++ b/docs/dcs/umn/ALL_META.TXT.json @@ -175,7 +175,7 @@ "node_id":"dcs-pd-0220606.xml", "product_code":"dcs", "code":"9", - "des":"This section describes read/write splitting DCS Redis 4.0/5.0 instances. Read/write splitting is implemented on the server side by default. Proxies distinguish between re", + "des":"This section describes read/write splitting DCS Redis 4.0/5.0/6.0 instances. Read/write splitting is implemented on the server side by default. Proxies distinguish betwee", "doc_type":"usermanual", "kw":"Read/Write Splitting Redis,DCS Instance Types,User Guide", "search_title":"", diff --git a/docs/dcs/umn/CLASS.TXT.json b/docs/dcs/umn/CLASS.TXT.json index ca12b72f3..44556be28 100644 --- a/docs/dcs/umn/CLASS.TXT.json +++ b/docs/dcs/umn/CLASS.TXT.json @@ -72,7 +72,7 @@ "code":"8" }, { - "desc":"This section describes read/write splitting DCS Redis 4.0/5.0 instances. Read/write splitting is implemented on the server side by default. Proxies distinguish between re", + "desc":"This section describes read/write splitting DCS Redis 4.0/5.0/6.0 instances. Read/write splitting is implemented on the server side by default. Proxies distinguish betwee", "product_code":"dcs", "title":"Read/Write Splitting Redis", "uri":"dcs-pd-0220606.html", diff --git a/docs/dcs/umn/CacheCluster.html b/docs/dcs/umn/CacheCluster.html index 0f4a60db9..50bd04aa2 100644 --- a/docs/dcs/umn/CacheCluster.html +++ b/docs/dcs/umn/CacheCluster.html @@ -5,11 +5,11 @@
  • The client is decoupled from the cloud service.
  • They support millions of concurrent requests, equivalent to Redis Cluster instances.
  • A wide range of memory specifications adapt to different scenarios.
  • A Proxy Cluster instance can be connected in the same way that a single-node or master/standby instance is connected, without any special settings on the client. You can use the IP address of the instance, and do not need to know or use the proxy or shard addresses.
-

Proxy Cluster DCS Redis 4.0/5.0 Instances

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

+

Proxy Cluster DCS Redis 4.0/5.0/6.0 Instances

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

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

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

-
- - @@ -850,9 +850,9 @@ - - diff --git a/docs/dcs/umn/dcs-pd-0916004.html b/docs/dcs/umn/dcs-pd-0916004.html index 29f547836..1e547eb44 100644 --- a/docs/dcs/umn/dcs-pd-0916004.html +++ b/docs/dcs/umn/dcs-pd-0916004.html @@ -3,183 +3,182 @@

Redis 6.0 and 7.0 Instance Specifications

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

The following metrics are related to the instance specifications:

-
  • Used memory: You can check the memory usage of an instance by viewing the Memory Usage and Used Memory metrics.
  • Maximum connections: The maximum number of connections allowed is the maximum number of clients that can be connected to an instance. To check the number of connections to an instance, view the Connected Clients metric.
  • QPS represents queries per second, which is the number of commands processed per second.
  • Bandwidth: You can view the Flow Control Times metric to check whether the bandwidth has exceeded the limit.
-

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

-

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

DCS for Redis 6.0 supports single-node, master/standby, Proxy Cluster, Redis Cluster, and read/write splitting instances. DCS for Redis 7.0 supports single-node, master/standby, and Redis Cluster instances.

Single-Node

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

Total Memory

+
@@ -157,7 +157,7 @@
Table 1 Specifications of Proxy Cluster DCS Redis 4.0/5.0/6.0 instances

Total Memory

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

Architecture description:

  • VPC

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

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

    diff --git a/docs/dcs/umn/dcs-pd-0220606.html b/docs/dcs/umn/dcs-pd-0220606.html index 3cf773713..198f70df5 100644 --- a/docs/dcs/umn/dcs-pd-0220606.html +++ b/docs/dcs/umn/dcs-pd-0220606.html @@ -1,7 +1,7 @@

    Read/Write Splitting Redis

    -

    This section describes read/write splitting DCS Redis 4.0/5.0 instances. Read/write splitting is implemented on the server side by default. Proxies distinguish between read requests and write requests, and forward write requests to the master node and read requests to the standby node.

    +

    This section describes read/write splitting DCS Redis 4.0/5.0/6.0 instances. Read/write splitting is implemented on the server side by default. Proxies distinguish between read requests and write requests, and forward write requests to the master node and read requests to the standby node.

    Read/write splitting is suitable for scenarios with high read concurrency and few write requests, aiming to improve the performance of high concurrency and reducing O&M costs.

    When using read/write splitting instances, note the following:
    1. Read requests are sent to replicas. There is a delay when data is synchronized from the master to the replicas.

      If your services are sensitive to the delay, do not use read/write splitting instances. Instead, use master/standby or cluster instances.

    2. Read/write splitting is suitable when there are more read requests than write requests. If there are a lot of write requests, the master and replicas may be disconnected, or the data synchronization between them may fail after the disconnection. As a result, the read performance deteriorates.

      If your services are write-heavy, use master/standby or cluster instances.

      diff --git a/docs/dcs/umn/dcs-pd-0916002.html b/docs/dcs/umn/dcs-pd-0916002.html index 832afdbbb..a7b2cd408 100644 --- a/docs/dcs/umn/dcs-pd-0916002.html +++ b/docs/dcs/umn/dcs-pd-0916002.html @@ -3,7 +3,7 @@

      Redis 4.0 and 5.0 Instance Specifications

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

      The following metrics are related to the instance specifications:

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

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

        +
        • Used memory: You can check the memory usage of an instance by viewing the Memory Usage and Used Memory metrics.
        • Maximum connections: The maximum number of connections allowed is the maximum number of clients that can be connected to an instance. This metric is implemented by the maxclients parameter (unavailable for read/write splitting instances). To modify this parameter, go to the Instance Configuration > Parameters page on the console. To check the number of connections to an instance, view the Connected Clients metric.
        • QPS represents queries per second, which is the number of commands processed per second.
        • Bandwidth: You can view the Flow Control Times metric to check whether the bandwidth has exceeded the limit.

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

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

redis.proxy.xu1.large.768

1024

+

1,024

1024

+

1,024

500,000/500,000

redis.cluster.xu1.large.r2.768

1024

+

1,024

1024

+

1,024

128
Table 1 Specifications of single-node DCS Redis 6.0/7.0 instances

Total Memory

+
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -187,179 +186,179 @@

Master/Standby

-
Table 1 Specifications of single-node DCS Redis 6.0/7.0 instances

Total Memory

(GB)

Available Memory

+

Available Memory

(GB)

Max. Connections (Default/Limit)

+

Max. Connections (Default/Limit)

(Count)

Assured/Maximum Bandwidth

+

Assured/Maximum Bandwidth

(Mbit/s)

Reference Performance

+

Reference Performance

(QPS)

Specification Code (spec_code in the API)

+

Specification Code (spec_code in the API)

0.125

+

0.125

0.125

+

0.125

10,000/10,000

+

10,000/10,000

40/40

+

40/40

80,000

+

80,000

redis.single.xu1.tiny.128

+

redis.single.xu1.tiny.128

0.25

+

0.25

0.25

+

0.25

10,000/10,000

+

10,000/10,000

80/80

+

80/80

80,000

+

80,000

redis.single.xu1.tiny.256

+

redis.single.xu1.tiny.256

0.5

+

0.5

0.5

+

0.5

10,000/10,000

+

10,000/10,000

80/80

+

80/80

80,000

+

80,000

redis.single.xu1.tiny.512

+

redis.single.xu1.tiny.512

1

+

1

1

+

1

10,000/50,000

+

10,000/50,000

80/80

+

80/80

80,000

+

80,000

redis.single.xu1.large.1

+

redis.single.xu1.large.1

2

+

2

2

+

2

10,000/50,000

+

10,000/50,000

128/128

+

128/128

80,000

+

80,000

redis.single.xu1.large.2

+

redis.single.xu1.large.2

4

+

4

4

+

4

10,000/50,000

+

10,000/50,000

192/192

+

192/192

80,000

+

80,000

redis.single.xu1.large.4

+

redis.single.xu1.large.4

8

+

8

8

+

8

10,000/50,000

+

10,000/50,000

192/192

+

192/192

100,000

+

100,000

redis.single.xu1.large.8

+

redis.single.xu1.large.8

16

+

16

16

+

16

10,000/50,000

+

10,000/50,000

256/256

+

256/256

100,000

+

100,000

redis.single.xu1.large.16

+

redis.single.xu1.large.16

24

+

24

24

+

24

10,000/50,000

+

10,000/50,000

256/256

+

256/256

100,000

+

100,000

redis.single.xu1.large.24

+

redis.single.xu1.large.24

32

+

32

32

+

32

10,000/50,000

+

10,000/50,000

256/256

+

256/256

100,000

+

100,000

redis.single.xu1.large.32

+

redis.single.xu1.large.32

48

+

48

48

+

48

10,000/50,000

+

10,000/50,000

256/256

+

256/256

100,000

+

100,000

redis.single.xu1.large.48

+

redis.single.xu1.large.48

64

+

64

64

+

64

10,000/50,000

+

10,000/50,000

384/384

+

384/384

100,000

+

100,000

redis.single.xu1.large.64

+

redis.single.xu1.large.64
Table 2 Specifications of master/standby DCS Redis 6.0/7.0 instances

Total Memory

+
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -375,250 +374,1216 @@ -
Table 2 Specifications of master/standby DCS Redis 6.0/7.0 instances

Total Memory

(GB)

Available Memory

+

Available Memory

(GB)

Max. Connections (Default/Limit)

+

Max. Connections (Default/Limit)

(Count)

Assured/Maximum Bandwidth

+

Assured/Maximum Bandwidth

(Mbit/s)

Reference Performance

+

Reference Performance

(QPS)

Specification Code (spec_code in the API)

+

Specification Code (spec_code in the API)

0.125

+

0.125

0.125

+

0.125

10,000/10,000

+

10,000/10,000

40/40

+

40/40

80,000

+

80,000

redis.ha.xu1.tiny.r2.128

+

redis.ha.xu1.tiny.r2.128

0.25

+

0.25

0.25

+

0.25

10,000/10,000

+

10,000/10,000

80/80

+

80/80

80,000

+

80,000

redis.ha.xu1.tiny.r2.256

+

redis.ha.xu1.tiny.r2.256

0.5

+

0.5

0.5

+

0.5

10,000/10,000

+

10,000/10,000

80/80

+

80/80

80,000

+

80,000

redis.ha.xu1.tiny.r2.512

+

redis.ha.xu1.tiny.r2.512

1

+

1

1

+

1

10,000/50,000

+

10,000/50,000

80/80

+

80/80

80,000

+

80,000

redis.ha.xu1.large.r2.1

+

redis.ha.xu1.large.r2.1

2

+

2

2

+

2

10,000/50,000

+

10,000/50,000

128/128

+

128/128

80,000

+

80,000

redis.ha.xu1.large.r2.2

+

redis.ha.xu1.large.r2.2

4

+

4

4

+

4

10,000/50,000

+

10,000/50,000

192/192

+

192/192

80,000

+

80,000

redis.ha.xu1.large.r2.4

+

redis.ha.xu1.large.r2.4

8

+

8

8

+

8

10,000/50,000

+

10,000/50,000

192/192

+

192/192

100,000

+

100,000

redis.ha.xu1.large.r2.8

+

redis.ha.xu1.large.r2.8

16

+

16

16

+

16

10,000/50,000

+

10,000/50,000

256/256

+

256/256

100,000

+

100,000

redis.ha.xu1.large.r2.16

+

redis.ha.xu1.large.r2.16

24

+

24

24

+

24

10,000/50,000

+

10,000/50,000

256/256

+

256/256

100,000

+

100,000

redis.ha.xu1.large.r2.24

+

redis.ha.xu1.large.r2.24

32

+

32

32

+

32

10,000/50,000

+

10,000/50,000

256/256

+

256/256

100,000

+

100,000

redis.ha.xu1.large.r2.32

+

redis.ha.xu1.large.r2.32

48

+

48

48

+

48

10,000/50,000

+

10,000/50,000

256/256

+

256/256

100,000

+

100,000

redis.ha.xu1.large.r2.48

+

redis.ha.xu1.large.r2.48

64

+

64

64

+

64

10,000/50,000

+

10,000/50,000

384/384

+

384/384

100,000

+

100,000

redis.ha.xu1.large.r2.64

+

redis.ha.xu1.large.r2.64
- @@ -734,7 +797,7 @@ - diff --git a/docs/dcs/umn/dcs-pd-191224001.html b/docs/dcs/umn/dcs-pd-191224001.html index 816dfc73d..92173734b 100644 --- a/docs/dcs/umn/dcs-pd-191224001.html +++ b/docs/dcs/umn/dcs-pd-191224001.html @@ -15,9 +15,9 @@ - - diff --git a/docs/dcs/umn/dcs-pd-210209002.html b/docs/dcs/umn/dcs-pd-210209002.html index 6feaf87f1..7d55608f2 100644 --- a/docs/dcs/umn/dcs-pd-210209002.html +++ b/docs/dcs/umn/dcs-pd-210209002.html @@ -7,7 +7,7 @@

Commands Supported by DCS for Redis 6.0

For details about the command syntax, visit the Redis official website. For example, to view details about the SCAN command, enter SCAN in the search box on this page.

-
Table 3 Specifications of Redis Cluster DCS Redis 6.0/7.0 instances

Total Memory

+
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + +
Table 3 Specifications of Redis Cluster DCS Redis 6.0/7.0 instances

Total Memory

(GB)

Available Memory

+

Available Memory

(GB)

Shards (Master Nodes)

+

Shards (Master Nodes)

Max. Connections (Default/Limit)

+

Max. Connections (Default/Limit)

(Count)

Assured/Maximum Bandwidth

+

Assured/Maximum Bandwidth

(Mbit/s)

Reference Performance

+

Reference Performance

(QPS)

Specification Code (spec_code in the API)

+

Specification Code (spec_code in the API)

4

+

4

4

+

4

3

+

3

30,000/150,000

+

30,000/150,000

2,304/2,304

+

2,304/2,304

240,000

+

240,000

redis.cluster.xu1.large.r2.4

+

redis.cluster.xu1.large.r2.4

8

+

8

8

+

8

3

+

3

30,000/150,000

+

30,000/150,000

2,304/2,304

+

2,304/2,304

240,000

+

240,000

redis.cluster.xu1.large.r2.8

+

redis.cluster.xu1.large.r2.8

16

+

16

16

+

16

3

+

3

30,000/150,000

+

30,000/150,000

2,304/2,304

+

2,304/2,304

240,000

+

240,000

redis.cluster.xu1.large.r2.16

+

redis.cluster.xu1.large.r2.16

24

+

24

24

+

24

3

+

3

30,000/150,000

+

30,000/150,000

2,304/2,304

+

2,304/2,304

300,000

+

300,000

redis.cluster.xu1.large.r2.24

+

redis.cluster.xu1.large.r2.24

32

+

32

32

+

32

3

+

3

30,000/150,000

+

30,000/150,000

2,304/2,304

+

2,304/2,304

300,000

+

300,000

redis.cluster.xu1.large.r2.32

+

redis.cluster.xu1.large.r2.32

48

+

48

48

+

48

6

+

6

60,000/300,000

+

60,000/300,000

4,608/4,608

+

4,608/4,608

> 300,000

+

> 300,000

redis.cluster.xu1.large.r2.48

+

redis.cluster.xu1.large.r2.48

64

+

64

64

+

64

8

+

8

80,000/400,000

+

80,000/400,000

6,144/6,144

+

6,144/6,144

500,000

+

500,000

redis.cluster.xu1.large.r2.64

+

redis.cluster.xu1.large.r2.64

96

+

96

96

+

96

12

+

12

120,000/600,000

+

120,000/600,000

9,216/9,216

+

9,216/9,216

> 500,000

+

> 500,000

redis.cluster.xu1.large.r2.96

+

redis.cluster.xu1.large.r2.96

128

+

128

128

+

128

16

+

16

160,000/800,000

+

160,000/800,000

12,288/12,288

+

12,288/12,288

1,000,000

+

1,000,000

redis.cluster.xu1.large.r2.128

+

redis.cluster.xu1.large.r2.128

192

+

192

192

+

192

24

+

24

240,000/1,200,000

+

240,000/1,200,000

18,432/18,432

+

18,432/18,432

> 1,000,000

+

> 1,000,000

redis.cluster.xu1.large.r2.192

+

redis.cluster.xu1.large.r2.192

256

+

256

256

+

256

32

+

32

320,000/1,600,000

+

320,000/1,600,000

24,576/24,576

+

24,576/24,576

> 2,000,000

+

> 2,000,000

redis.cluster.xu1.large.r2.256

+

redis.cluster.xu1.large.r2.256

384

+

384

384

+

384

48

+

48

480,000/2,400,000

+

480,000/2,400,000

36,864/36,864

+

36,864/36,864

> 2,000,000

+

> 2,000,000

redis.cluster.xu1.large.r2.384

+

redis.cluster.xu1.large.r2.384

512

+

512

512

+

512

64

+

64

640,000/3,200,000

+

640,000/3,200,000

49,152/49,152

+

49,152/49,152

> 2,000,000

+

> 2,000,000

redis.cluster.xu1.large.r2.512

+

redis.cluster.xu1.large.r2.512

768

+

768

768

+

768

96

+

96

960,000/4,800,000

+

960,000/4,800,000

73,728/73,728

+

73,728/73,728

> 2,000,000

+

> 2,000,000

redis.cluster.xu1.large.r2.768

+

redis.cluster.xu1.large.r2.768

1024

+

1,024

1024

+

1,024

128

+

128

1,280,000/6,400,000

+

1,280,000/6,400,000

98,304/98,304

+

98,304/98,304

> 2,000,000

+

> 2,000,000

redis.cluster.xu1.large.r2.1024

+

redis.cluster.xu1.large.r2.1024

+
+
+ +

Proxy Cluster

Table 4 lists the specifications supported by Proxy Cluster instances.

+

Proxy Cluster instances do not support replica quantity customization. Each shard has two replicas by default. For details about the default number of shards, see Table 1. When creating an instance, you can customize the size of a single shard.

+
  • The following table lists only the Proxy Cluster instance specifications with default shards. If you customize shards, see the maximum number of connections, assured/maximum bandwidth, and product specification code (flavor) in the Instance Specification table on the Create DCS Instance page of the DCS console.
  • The maximum connections of a cluster is for the entire instance, and not for a single shard. Maximum connections per shard = Maximum connections of an instance/Number of shards.
  • The maximum bandwidth and assured bandwidth of a cluster is for the entire instance, and not for a single shard. The relationship between the instance bandwidth and the bandwidth per shard is as follows:
    • Instance bandwidth = Bandwidth per shard × Number of shards
    • For a cluster instance, if the memory per shard is 1 GB, the bandwidth per shard is 384 Mbit/s. If the memory per shard is greater than 1 GB, the bandwidth per shard is 768 Mbit/s.
    • The upper limit of the bandwidth of a Proxy Cluster instance is 10,000 Mbit/s. That is, even if the bandwidth per shard multiplied by the number of shards is greater than 10,000 Mbit/s, the bandwidth of the instance is still 10,000 Mbit/s.
    +
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 4 Specifications of Proxy Cluster DCS Redis 6.0 instances

Specification

+

(GB)

+

Available Memory

+

(GB)

+

Shards (Master Nodes)

+

Max. Connections (Default/Limit)

+

(Count)

+

Assured/Maximum Bandwidth

+

(Mbit/s)

+

Reference Performance

+

(QPS)

+

Specification Code (spec_code in the API)

+

4

+

4

+

3

+

20,000/20,000

+

2,304/2,304

+

240,000

+

redis.proxy.xu1.large.4

+

8

+

8

+

3

+

30,000/30,000

+

2,304/2,304

+

240,000

+

redis.proxy.xu1.large.8

+

16

+

16

+

3

+

30,000/30,000

+

2,304/2,304

+

240,000

+

redis.proxy.xu1.large.16

+

24

+

24

+

3

+

30,000/30,000

+

2,304/2,304

+

240,000

+

redis.proxy.xu1.large.24

+

32

+

32

+

3

+

30,000/30,000

+

2,304/2,304

+

240,000

+

redis.proxy.xu1.large.32

+

48

+

48

+

6

+

60,000/60,000

+

4,608/4,608

+

480,000

+

redis.proxy.xu1.large.48

+

64

+

64

+

8

+

80,000/80,000

+

6,144/6,144

+

640,000

+

redis.proxy.xu1.large.64

+

96

+

96

+

12

+

120,000/120,000

+

9,216/9,216

+

960,000

+

redis.proxy.xu1.large.96

+

128

+

128

+

16

+

160,000/160,000

+

10,000/10,000

+

1,280,000

+

redis.proxy.xu1.large.128

+

192

+

192

+

24

+

200,000/240,000

+

10,000/10,000

+

1,920,000

+

redis.proxy.xu1.large.192

+

256

+

256

+

32

+

200,000/320,000

+

10,000/10,000

+

> 2,000,000

+

redis.proxy.xu1.large.256

+

384

+

384

+

48

+

200,000/480,000

+

10,000/10,000

+

> 2,000,000

+

redis.proxy.xu1.large.384

+

512

+

512

+

64

+

200,000/500,000

+

10,000/10,000

+

> 2,000,000

+

redis.proxy.xu1.large.512

+

768

+

768

+

96

+

200,000/500,000

+

10,000/10,000

+

> 2,000,000

+

redis.proxy.xu1.large.768

+

1,024

+

1,024

+

128

+

200,000/500,000

+

10,000/10,000

+

> 2,000,000

+

redis.proxy.xu1.large.1024

+

2,048

+

2,048

+

128

+

200,000/500,000

+

10,000/10,000

+

> 2,000,000

+

redis.proxy.xu1.large.2048

+
+
+
+

Read/Write Splitting

  • For details about the specifications of read/write splitting instances, see Table 5.
  • The maximum connections of a read/write splitting DCS Redis instance cannot be modified.
  • Bandwidth limit per Redis server (MB/s) = Total bandwidth limit (MB/s)/Number of replicas (masters included)
  • Reference performance (QPS) per node = Reference performance (QPS)/Number of replicas (masters included)
  • Constraints:
    1. Read requests are sent to replicas. There is a delay when data is synchronized from the master to the replicas.

      If your services are sensitive to the delay, do not use read/write splitting instances. Instead, use master/standby or cluster instances.

      +
    2. Read/Write splitting is suitable when there are more read requests than write requests. If there are a lot of write requests, the master and replicas may be disconnected, or the data synchronization between them may fail after the disconnection. As a result, the read performance deteriorates.

      If your services are write-heavy, use master/standby or cluster instances.

      +
    3. When a replica is faulty, it takes some time to synchronize all data from the master. During the synchronization, the replica is out of service, and the read performance of the instance deteriorates.

      Instances with less than 32 GB of memory are recommended. The smaller the memory, the faster the full synchronization and the smaller the impact of interruption.

      +
    +
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/dcs/umn/dcs-pd-190826001.html b/docs/dcs/umn/dcs-pd-190826001.html index 4286df613..5bb9f132d 100644 --- a/docs/dcs/umn/dcs-pd-190826001.html +++ b/docs/dcs/umn/dcs-pd-190826001.html @@ -572,7 +572,7 @@ - @@ -680,6 +680,69 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 5 Read/Write splitting DCS Redis 6.0 instance specifications

Specification

+

Available Memory (GB)

+

Replicas (Including Masters)

+

Max. Connections (Default/Limit)

+

Bandwidth Limit (MB/s)

+

Bandwidth Limit per Redis Server (MB/s)

+

Reference Performance (QPS)

+

Reference Performance per Node (QPS)

+

Specification Code (spec_code in the API)

+

1

+

1

+

2

+

20,000

+

96

+

48

+

160,000

+

80,000

+

redis.ha.xu1.large.p2.1

+

1

+

1

+

3

+

30,000

+

144

+

48

+

240,000

+

80,000

+

redis.ha.xu1.large.p3.1

+

1

+

1

+

4

+

40,000

+

192

+

48

+

320,000

+

80,000

+

redis.ha.xu1.large.p4.1

+

1

+

1

+

5

+

50,000

+

240

+

48

+

400,000

+

80,000

+

redis.ha.xu1.large.p5.1

+

1

+

1

+

6

+

60,000

+

288

+

48

+

480,000

+

80,000

+

redis.ha.xu1.large.p6.1

+

2

+

2

+

2

+

20,000

+

96

+

48

+

160,000

+

80,000

+

redis.ha.xu1.large.p2.2

+

2

+

2

+

3

+

30,000

+

144

+

48

+

240,000

+

80,000

+

redis.ha.xu1.large.p3.2

+

2

+

2

+

4

+

40,000

+

192

+

48

+

320,000

+

80,000

+

redis.ha.xu1.large.p4.2

+

2

+

2

+

5

+

50,000

+

240

+

48

+

400,000

+

80,000

+

redis.ha.xu1.large.p5.2

+

2

+

2

+

6

+

60,000

+

288

+

48

+

480,000

+

80,000

+

redis.ha.xu1.large.p6.2

+

4

+

4

+

2

+

20,000

+

96

+

48

+

160,000

+

80,000

+

redis.ha.xu1.large.p2.4

+

4

+

4

+

3

+

30,000

+

144

+

48

+

240,000

+

80,000

+

redis.ha.xu1.large.p3.4

+

4

+

4

+

4

+

40,000

+

192

+

48

+

320,000

+

80,000

+

redis.ha.xu1.large.p4.4

+

4

+

4

+

5

+

50,000

+

240

+

48

+

400,000

+

80,000

+

redis.ha.xu1.large.p5.4

+

4

+

4

+

6

+

60,000

+

288

+

48

+

480,000

+

80,000

+

redis.ha.xu1.large.p6.4

+

8

+

8

+

2

+

20,000

+

192

+

96

+

160,000

+

80,000

+

redis.ha.xu1.large.p2.8

+

8

+

8

+

3

+

30,000

+

288

+

96

+

240,000

+

80,000

+

redis.ha.xu1.large.p3.8

+

8

+

8

+

4

+

40,000

+

384

+

96

+

320,000

+

80,000

+

redis.ha.xu1.large.p4.8

+

8

+

8

+

5

+

50,000

+

480

+

96

+

400,000

+

80,000

+

redis.ha.xu1.large.p5.8

+

8

+

8

+

6

+

60,000

+

576

+

96

+

480,000

+

80,000

+

redis.ha.xu1.large.p6.8

+

16

+

16

+

2

+

20,000

+

192

+

96

+

160,000

+

80,000

+

redis.ha.xu1.large.p2.16

+

16

+

16

+

3

+

30,000

+

288

+

96

+

240,000

+

80,000

+

redis.ha.xu1.large.p3.16

+

16

+

16

+

4

+

40,000

+

384

+

96

+

320,000

+

80,000

+

redis.ha.xu1.large.p4.16

+

16

+

16

+

5

+

50,000

+

480

+

96

+

400,000

+

80,000

+

redis.ha.xu1.large.p5.16

+

16

+

16

+

6

+

60,000

+

576

+

96

+

480,000

+

80,000

+

redis.ha.xu1.large.p6.16

+

32

+

32

+

2

+

20,000

+

192

+

96

+

160,000

+

80,000

+

redis.ha.xu1.large.p2.32

+

32

+

32

+

3

+

30,000

+

288

+

96

+

240,000

+

80,000

+

redis.ha.xu1.large.p3.32

+

32

+

32

+

4

+

40,000

+

384

+

96

+

320,000

+

80,000

+

redis.ha.xu1.large.p4.32

+

32

+

32

+

5

+

50,000

+

480

+

96

+

400,000

+

80,000

+

redis.ha.xu1.large.p5.32

+

32

+

32

+

6

+

60,000

+

576

+

96

+

480,000

+

80,000

+

redis.ha.xu1.large.p6.32

+

64

+

64

+

2

+

20,000

+

192

+

96

+

160,000

+

80,000

+

redis.ha.xu1.large.p2.64

+

64

+

64

+

3

+

30,000

+

288

+

96

+

240,000

+

80,000

+

redis.ha.xu1.large.p3.64

+

64

+

64

+

4

+

40,000

+

384

+

96

+

320,000

+

80,000

+

redis.ha.xu1.large.p4.64

+

64

+

64

+

5

+

50,000

+

480

+

96

+

400,000

+

80,000

+

redis.ha.xu1.large.p5.64

+

64

+

64

+

6

+

60,000

+

576

+

96

+

480,000

+

80,000

+

redis.ha.xu1.large.p6.64

CLUSTER DELSLOTS

-

+

WAITAOF

CONFIG REWRITE

-

-

+

COMMAND COUNT

+

-

+

-

+

-

+

COMMAND DOCS

+

-

+

-

+

-

+

COMMAND GETKEYS

+

-

+

-

+

-

+

COMMAND GETKEYSANDFLAGS

+

-

+

-

+

-

+

COMMAND INFO

+

-

+

-

+

-

+

COMMAND LIST

+

-

+

-

+

-

+

RESTORE-ASKING

+

-

+

-

+
@@ -725,7 +788,7 @@

-

-

+

ZREM

-

-

-

+

ZUNION

-

Redis version compatibility

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

+

Single-node and master/standby: Redis 4.0/5.0/6.0/7.0. Read/Write splitting: Redis 4.0/5.0/6.0.

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

+

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

Redis 4.0/5.0/6.0/7.0 You can select a version when creating an instance.
Table 1 Commands supported by DCS Redis 6.0 instances (1)

Generic (Key)

+
@@ -462,7 +462,7 @@
Table 1 Commands supported by single-node, master/standby, and Redis Cluster DCS Redis 6.0 instances (1)

Generic (Key)

String

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

HyperLoglog

+
@@ -736,9 +736,1456 @@
Table 2 Commands supported by single-node, master/standby, and Redis Cluster DCS Redis 6.0 instances (2)

HyperLoglog

Pub/Sub
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 3 Commands supported by Proxy Cluster DCS Redis 6.0 instances (1)

Generic (Key)

+

String

+

Hash

+

List

+

Set

+

Sorted Set

+

Server

+

DEL

+

APPEND

+

HDEL

+

BLPOP

+

SADD

+

ZADD

+

FLUSHALL

+

(FLUSHALL SYNC not supported.)

+

DUMP

+

BITCOUNT

+

HEXISTS

+

BRPOP

+

SCARD

+

ZCARD

+

FLUSHDB

+

EXISTS

+

BITOP

+

HGET

+

BRPOPLRUSH

+

SDIFF

+

ZCOUNT

+

DBSIZE

+

EXPIRE

+

BITPOS

+

HGETALL

+

LINDEX

+

SDIFFSTORE

+

ZINCRBY

+

TIME

+

MOVE

+

DECR

+

HINCRBY

+

LINSERT

+

SINTER

+

ZRANGE

+

INFO

+

PERSIST

+

DECRBY

+

HINCRBYFLOAT

+

LLEN

+

SINTERSTORE

+

ZRANGEBYSCORE

+

ROLE

+

PTTL

+

GET

+

HKEYS

+

LPOP

+

SISMEMBER

+

ZRANK

+

MEMORY

+

RENAME

+

GETRANGE

+

HMGET

+

LPUSHX

+

SMEMBERS

+

ZREMRANGEBYRANK

+

COMMAND

+

RENAMENX

+

GETSET

+

HMSET

+

LRANGE

+

SMOVE

+

ZREMRANGEBYCORE

+

COMMAND COUNT

+

RESTORE

+

INCR

+

HSET

+

LREM

+

SPOP

+

ZREVRANGE

+

COMMAND GETKEYS

+

SORT

+

INCRBY

+

HSETNX

+

LSET

+

SRANDMEMBER

+

ZREVRANGEBYSCORE

+

COMMAND INFO

+

TTL

+

INCRBYFLOAT

+

HVALS

+

LTRIM

+

SREM

+

ZREVRANK

+

CONFIG GET

+

TYPE

+

MGET

+

HSCAN

+

RPOP

+

SUNION

+

ZSCORE

+

CONFIG RESETSTAT

+

SCAN

+

MSET

+

HSTRLEN

+

RPOPLPUSH

+

SUNIONSTORE

+

ZUNIONSTORE

+

CONFIG REWRITE

+

OBJECT

+

MSETNX

+

HLEN

+

RPUSH

+

SSCAN

+

ZINTERSTORE

+

CONFIG SET

+

PEXPIRE

+

PSETEX

+

HKEYS

+

RPUSHX

+

SMISMEMBER

+

ZSCAN

+

-

+

PEXPIREAT

+

SET

+

HRANDFIELD

+

LPUSH

+

-

+

ZRANGEBYLEX

+

-

+

EXPIREAT

+

SETBIT

+

-

+

BLMOVE

+

-

+

ZLEXCOUNT

+

-

+

KEYS

+

SETEX

+

-

+

LMOVE

+

-

+

ZREMRANGEBYSCORE

+

-

+

UNLINK

+

SETNX

+

-

+

LPOS

+

-

+

ZREM

+

-

+

TOUCH

+

SETRANGE

+

-

+

-

+

-

+

ZREMRANGEBYLEX

+

-

+

RANDOMKEY

+

STRLEN

+

-

+

-

+

-

+

ZPOPMAX

+

-

+

COPY

+

BITFIELD

+

-

+

-

+

-

+

ZPOPMIN

+

-

+

-

+

GETBIT

+

-

+

-

+

-

+

BZPOPMAX

+

-

+

-

+

BITFIELD_RO

+

-

+

-

+

-

+

BZPOPMIN

+

-

+

-

+

GETDEL

+

-

+

-

+

-

+

ZREVRANGEBYLEX

+

-

+

-

+

GETEX

+

-

+

-

+

-

+

ZDIFF

+

-

+

-

+

-

+

-

+

-

+

-

+

ZDIFFSTORE

+

-

+

-

+

-

+

-

+

-

+

-

+

ZINTER

+

-

+

-

+

-

+

-

+

-

+

-

+

ZMSCORE

+

-

+

-

+

-

+

-

+

-

+

-

+

ZRANDMEMBER

+

-

+

-

+

-

+

-

+

-

+

-

+

ZRANGESTORE

+

-

+

-

+

-

+

-

+

-

+

-

+

ZUNION

+

-

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 4 Commands supported by Proxy Cluster DCS Redis 6.0 instances (2)

HyperLoglog

+

Pub/Sub

+

Transactions

+

Connection

+

Scripting

+

Geo

+

Cluster

+

PFADD

+

PSUBSCRIBE

+

DISCARD

+

AUTH

+

EVAL

+

GEOADD

+

CLUSTER INFO

+

PFCOUNT

+

PUBLISH

+

EXEC

+

ECHO

+

EVALSHA

+

GEOHASH

+

CLUSTER NODES

+

PFMERGE

+

PUBSUB

+

MULTI

+

PING

+

SCRIPT EXISTS

+

GEOPOS

+

CLUSTER SLOTS

+

-

+

PUNSUBSCRIBE

+

UNWATCH

+

QUIT

+

SCRIPT FLUSH

+

GEODIST

+

CLUSTER ADDSLOTS

+

-

+

SUBSCRIBE

+

WATCH

+

SELECT

+

SCRIPT KILL

+

GEORADIUS

+

ASKING

+

-

+

UNSUBSCRIBE

+

-

+

CLIENT KILL

+

SCRIPT LOAD

+

GEORADIUSBYMEMBER

+

READONLY

+

-

+

-

+

-

+

CLIENT LIST

+

SCRIPT DEBUG YES|SYNC|NO

+

GEOSEARCH

+

READWRITE

+

-

+

-

+

-

+

CLIENT GETNAME

+

-

+

GEOSEARCHSTORE

+

-

+

-

+

-

+

-

+

CLIENT SETNAME

+

-

+

-

+

-

+

-

+

-

+

-

+

HELLO

+

-

+

-

+

-

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 5 Commands supported by read/write splitting DCS Redis 6.0 instances (1)

Generic (Key)

+

String

+

Hash

+

List

+

Set

+

Sorted Set

+

Server

+

DEL

+

APPEND

+

HDEL

+

BLPOP

+

SADD

+

ZADD

+

FLUSHALL

+

(FLUSHALL SYNC not supported.)

+

DUMP

+

BITCOUNT

+

HEXISTS

+

BRPOP

+

SCARD

+

ZCARD

+

FLUSHDB

+

EXISTS

+

BITOP

+

HGET

+

BRPOPLRUSH

+

SDIFF

+

ZCOUNT

+

DBSIZE

+

EXPIRE

+

BITPOS

+

HGETALL

+

LINDEX

+

SDIFFSTORE

+

ZINCRBY

+

TIME

+

MOVE

+

DECR

+

HINCRBY

+

LINSERT

+

SINTER

+

ZRANGE

+

INFO

+

PERSIST

+

DECRBY

+

HINCRBYFLOAT

+

LLEN

+

SINTERSTORE

+

ZRANGEBYSCORE

+

MONITOR

+

PTTL

+

GET

+

HKEYS

+

LPOP

+

SISMEMBER

+

ZRANK

+

SLOWLOG

+

RANDOMKEY

+

GETRANGE

+

HMGET

+

LPUSHX

+

SMEMBERS

+

ZREMRANGEBYRANK

+

ROLE

+

RENAME

+

GETSET

+

HMSET

+

LRANGE

+

SMOVE

+

ZREMRANGEBYCORE

+

SWAPDB

+

RENAMENX

+

INCR

+

HSET

+

LREM

+

SPOP

+

ZREVRANGE

+

MEMORY

+

RESTORE

+

INCRBY

+

HSETNX

+

LSET

+

SRANDMEMBER

+

ZREVRANGEBYSCORE

+

COMMAND

+

SORT

+

INCRBYFLOAT

+

HVALS

+

LTRIM

+

SREM

+

ZREVRANK

+

COMMAND COUNT

+

TTL

+

MGET

+

HSCAN

+

RPOP

+

SUNION

+

ZSCORE

+

COMMAND GETKEYS

+

TYPE

+

MSET

+

HSTRLEN

+

RPOPLPUSH

+

SUNIONSTORE

+

ZUNIONSTORE

+

COMMAND INFO

+

SCAN

+

MSETNX

+

HLEN

+

RPUSH

+

SSCAN

+

ZINTERSTORE

+

CONFIG GET

+

OBJECT

+

PSETEX

+

HRANDFIELD

+

RPUSHX

+

SMISMEMBER

+

ZSCAN

+

CONFIG RESETSTAT

+

PEXPIRE

+

SET

+

-

+

LPUSH

+

-

+

ZRANGEBYLEX

+

CONFIG REWRITE

+

PEXPIREAT

+

SETBIT

+

-

+

BLMOVE

+

-

+

ZLEXCOUNT

+

CONFIG SET

+

EXPIREAT

+

SETEX

+

-

+

LMOVE

+

-

+

ZREMRANGEBYSCORE

+

-

+

KEYS

+

SETNX

+

-

+

LPOS

+

-

+

ZREM

+

-

+

UNLINK

+

SETRANGE

+

-

+

-

+

-

+

ZREMRANGEBYLEX

+

-

+

TOUCH

+

STRLEN

+

-

+

-

+

-

+

BZPOPMAX

+

-

+

COPY

+

BITFIELD

+

-

+

-

+

-

+

BZPOPMIN

+

-

+

-

+

GETBIT

+

-

+

-

+

-

+

ZPOPMAX

+

-

+

-

+

BITFIELD_RO

+

-

+

-

+

-

+

ZPOPMIN

+

-

+

-

+

GETDEL

+

-

+

-

+

-

+

ZREVRANGEBYLEX

+

-

+

-

+

GETEX

+

-

+

-

+

-

+

ZDIFF

+

-

+

-

+

-

+

-

+

-

+

-

+

ZDIFFSTORE

+

-

+

-

+

-

+

-

+

-

+

-

+

ZINTER

+

-

+

-

+

-

+

-

+

-

+

-

+

ZMSCORE

+

-

+

-

+

-

+

-

+

-

+

-

+

ZRANDMEMBER

+

-

+

-

+

-

+

-

+

-

+

-

+

ZRANGESTORE

+

-

+

-

+

-

+

-

+

-

+

-

+

ZUNION

+

-

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 6 Commands supported by read/write splitting DCS Redis 6.0 instances (2)

HyperLoglog

+

Pub/Sub

+

Transactions

+

Connection

+

Scripting

+

Geo

+

Stream

+

PFADD

+

PSUBSCRIBE

+

DISCARD

+

AUTH

+

EVAL

+

GEOADD

+

XAUTOCLAIM

+

PFCOUNT

+

PUBLISH

+

EXEC

+

ECHO

+

EVALSHA

+

GEOHASH

+

XGROUP CREATECONSUMER

+

PFMERGE

+

PUBSUB

+

MULTI

+

PING

+

SCRIPT EXISTS

+

GEOPOS

+

XACK

+

-

+

PUNSUBSCRIBE

+

UNWATCH

+

QUIT

+

SCRIPT FLUSH

+

GEODIST

+

XADD

+

-

+

SUBSCRIBE

+

WATCH

+

SELECT

+

SCRIPT KILL

+

GEORADIUS

+

XCLAIM

+

-

+

UNSUBSCRIBE

+

-

+

CLIENT KILL

+

SCRIPT LOAD

+

GEORADIUSBYMEMBER

+

XDEL

+

-

+

-

+

-

+

CLIENT LIST

+

SCRIPT DEBUG YES|SYNC|NO

+

GEOSEARCH

+

XGROUP

+

-

+

-

+

-

+

CLIENT GETNAME

+

-

+

GEOSEARCHSTORE

+

XINFO

+

-

+

-

+

-

+

CLIENT SETNAME

+

-

+

-

+

XLEN

+

-

+

-

+

-

+

HELLO

+

-

+

-

+

XPENDING

+

-

+

-

+

-

+

-

+

-

+

-

+

XRANGE

+

-

+

-

+

-

+

-

+

-

+

-

+

XREAD

+

-

+

-

+

-

+

-

+

-

+

-

+

XREADGROUP

+

-

+

-

+

-

+

-

+

-

+

-

+

XREVRANGE

+

-

+

-

+

-

+

-

+

-

+

-

+

XTRIM

+
+

Commands Disabled by DCS for Redis 6.0

-
- - - - -
Table 3 Commands disabled by DCS Redis 6.0 instances

Generic (Key)

+
@@ -840,6 +2287,268 @@
Table 7 Commands disabled by single-node, master/standby, and Redis Cluster DCS Redis 6.0 instances

Generic (Key)

Server
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 8 Commands disabled in Proxy Cluster DCS Redis 6.0 instances

Generic (Key)

+

Server

+

Connection

+

MIGRATE

+

BGREWRITEAOF

+

CLIENT CACHING

+

MOVE

+

BGSAVE

+

CLIENT GETREDIR

+

WAIT

+

CLIENT commands

+

CLIENT INFO

+

-

+

DEBUG OBJECT

+

CLIENT TRACKING

+

-

+

DEBUG SEGFAULT

+

CLIENT TRACKINGINFO

+

-

+

LASTSAVE

+

CLIENT UNPAUSE

+

-

+

PSYNC

+

RESET

+

-

+

SAVE

+

-

+

-

+

SHUTDOWN

+

-

+

-

+

SLAVEOF

+

-

+

-

+

LATENCY commands

+

-

+

-

+

MODULE commands

+

-

+

-

+

LOLWUT

+

-

+

-

+

SWAPDB

+

-

+

-

+

REPLICAOF

+

-

+

-

+

SYNC

+

-

+

-

+

ACL

+

-

+

-

+

FAILOVER

+

-

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 9 Commands disabled in read/write splitting DCS Redis 6.0 instances

Generic

+

Server

+

Connection

+

MIGRATE

+

BGREWRITEAOF

+

CLIENT CACHING

+

WAIT

+

BGSAVE

+

CLIENT GETREDIR

+

-

+

DEBUG OBJECT

+

CLIENT INFO

+

-

+

DEBUG SEGFAULT

+

CLIENT TRACKING

+

-

+

LASTSAVE

+

CLIENT TRACKINGINFO

+

-

+

LOLWUT

+

CLIENT UNPAUSE

+

-

+

MODULE LIST/LOAD/UNLOAD

+

RESET

+

-

+

PSYNC

+

-

+

-

+

REPLICAOF

+

-

+

-

+

SAVE

+

-

+

-

+

SHUTDOWN [NOSAVE|SAVE]

+

-

+

-

+

SLAVEOF

+

-

+

-

+

SWAPDB

+

-

+

-

+

SYNC

+

-

+

-

+

ACL

+

-

+

-

+

FAILOVER

+

-

+
+
diff --git a/docs/dcs/umn/dcs-ug-0312008.html b/docs/dcs/umn/dcs-ug-0312008.html index 557ba0e01..7059d3853 100644 --- a/docs/dcs/umn/dcs-ug-0312008.html +++ b/docs/dcs/umn/dcs-ug-0312008.html @@ -7,7 +7,7 @@

Prerequisites

The instance is in the Running state.

Procedure

  1. Log in to the DCS console.
  2. Click in the upper left corner and select a region and a project.
  3. In the navigation pane, choose Cache Manager.
  4. In the row containing the desired instance, choose More > Connect to Redis to go to the Web CLI login page.

    -

  5. Enter the password of the DCS instance. On Web CLI, select the current Redis database, enter a Redis command in the command box, and press Enter.

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

    +

  6. Enter the password of the DCS instance. On Web CLI, select the current Redis database, enter a Redis command in the command box, and press Enter.

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

diff --git a/docs/dcs/umn/dcs-ug-0312040.html b/docs/dcs/umn/dcs-ug-0312040.html index 3fede0f9c..a7fa9e754 100644 --- a/docs/dcs/umn/dcs-ug-0312040.html +++ b/docs/dcs/umn/dcs-ug-0312040.html @@ -6,7 +6,7 @@

Prerequisites

At least one DCS instance has been created.

-

Procedure

  1. Log in to the DCS console.
  2. Click in the upper left corner and select a region and a project.
  3. In the navigation pane, choose Cache Manager.
  4. Choose More > Change Password in the same row as the chosen instance.
  5. In the displayed dialog box, set Old Password, New Password, and Confirm Password.

    After 5 consecutive incorrect password attempts, the account for accessing the chosen DCS instance will be locked for 5 minutes. Passwords cannot be changed during the lockout period.

    +

    Procedure

    1. Log in to the DCS console.
    2. Click in the upper left corner and select a region and a project.
    3. In the navigation pane, choose Cache Manager.
    4. Choose More > Change Password in the same row as the chosen instance.
    5. In the displayed dialog box, set Old Password, New Password, and Confirm Password.

      After 5 consecutive incorrect password attempts, the account for accessing the chosen DCS instance will be locked for 5 minutes. Passwords cannot be changed during the lockout period. You can continue other operations.

      The password must meet the following requirements:

      • Cannot be left blank.
      • The new password cannot be the same as the old password.
      • Can contain 8 to 32 characters.
      • Must contain at least three of the following character types:
        • Lowercase letters
        • Uppercase letters
        • Digits
        • Special characters (`~!@#$^&*()-_=+\|{},<.>/?)
      diff --git a/docs/dcs/umn/dcs-ug-0326008.html b/docs/dcs/umn/dcs-ug-0326008.html index 574442192..b9df76900 100644 --- a/docs/dcs/umn/dcs-ug-0326008.html +++ b/docs/dcs/umn/dcs-ug-0326008.html @@ -32,7 +32,7 @@
      • On the instance creation page, the default parameter templates are used by default.
      • If you use a custom template, the selected cache engine version and instance type must match those of the template. For details about using custom templates, see Creating a Custom Parameter Template.

    6. Choose whether to enable Auto Backup.

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

      -

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

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

      +

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

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

    11. Click More Settings to configure more parameters.

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

        Command Renaming is displayed for Redis 4.0 and later. Currently, you can only rename the COMMAND, KEYS, FLUSHDB, FLUSHALL, HGETALL, SCAN, HSCAN, SSCAN, and ZSCAN commands. For Proxy Cluster instances, you can also rename the DBSIZE and DBSTATS commands.

      3. Specify the maintenance window.

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

      diff --git a/docs/dcs/umn/dcs-ug-1009001.html b/docs/dcs/umn/dcs-ug-1009001.html index 28e3d1fe2..b6b90cb09 100644 --- a/docs/dcs/umn/dcs-ug-1009001.html +++ b/docs/dcs/umn/dcs-ug-1009001.html @@ -5,7 +5,9 @@

      This function is supported by DCS Redis 4.0 instances and later.

      Procedure

      1. Log in to the DCS console.
      2. Click in the upper left corner and select a region and a project.
      3. In the navigation pane, choose Cache Manager.
      4. Click the name of a DCS instance.
      5. Click Run Logs.
      6. Click Create Log File.

        For a master/standby, read/write splitting, or cluster instance, logs will be collected from the specified shard and replica. If the instance is the single-node type, logs of the only node of the instance will be collected.

        Select the collection period and click OK.

        -

      7. After the log file is successfully collected, click Download to download it.
      +

    12. After the log file is successfully collected, click Download to download it.

      • Log files are retained for seven days. Download them if necessary.
      • The Redis kernel generates few logs, so your selected period may contain no log.
      +
      +

    diff --git a/docs/dcs/umn/dcs-ug-211105002.html b/docs/dcs/umn/dcs-ug-211105002.html index 12c8f7362..f2931b20b 100644 --- a/docs/dcs/umn/dcs-ug-211105002.html +++ b/docs/dcs/umn/dcs-ug-211105002.html @@ -3,8 +3,8 @@

    Connecting to Redis on Lettuce (Java)

    This section describes how to access a Redis instance on Lettuce. For more information about how to use other Redis clients, visit the Redis official website.

    Spring Data Redis is already integrated with Jedis and Lettuce for Spring Boot projects. In addition, Spring Boot 1.x is integrated with Jedis, and Spring Boot 2.x with Lettuce. Therefore, you do not need to import Lettuce in Spring Boot 2.x and later projects.

    -

    Springboot 2.3.12.RELEASE or later is required. Lettuce 6.3.0.RELEASE or later is required.

    -
    +

    Notes and Constraints

    Springboot 2.3.12.RELEASE or later is required. Lettuce 6.3.0.RELEASE or later is required.

    +

    Prerequisites

    Pom Configuration

    <!-- Enable Spring Data Redis, Lettuce-supported SDK is integrated by default -->
@@ -898,23 +898,23 @@ public LettuceClientConfiguration clientConfiguration() {

softMinEvictableIdleTimeMillis

1800000

+

-1

Duration after which idle connections are evicted. If the idle duration is greater than this value and the maximum number of idle connections is reached, idle connections are directly evicted.

+

Duration (in milliseconds) after which idle connections are evicted. If the idle duration is greater than this value and the maximum number of idle connections is reached, idle connections are directly evicted. Recommended value: 1800000.

minEvictableIdleTimeMillis

60000

+

1800000

An eviction policy, set to –1 (suggested) to disable it. Use softminEvictableIdleTimeMillis instead.

timeBetweenEvictionRunsMillis

60000

+

-1

Eviction interval, in milliseconds.

+

Eviction interval, in milliseconds. Recommended value: 60000