Compare commits
1 Commits
main
...
propose-dc
| Author | SHA1 | Date | |
|---|---|---|---|
| 0a82175a27 |
BIN
umn/source/_static/images/en-us_image_0000001505063901.png
Normal file
BIN
umn/source/_static/images/en-us_image_0000001505063901.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 339 B |
BIN
umn/source/_static/images/en-us_image_0266235369.png
Normal file
BIN
umn/source/_static/images/en-us_image_0266235369.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 581 B |
BIN
umn/source/_static/images/en-us_image_0266235377.png
Normal file
BIN
umn/source/_static/images/en-us_image_0266235377.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 366 B |
BIN
umn/source/_static/images/en-us_image_0266235408.png
Normal file
BIN
umn/source/_static/images/en-us_image_0266235408.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 581 B |
BIN
umn/source/_static/images/en-us_image_0266235415.png
Normal file
BIN
umn/source/_static/images/en-us_image_0266235415.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 366 B |
Binary file not shown.
|
Before Width: | Height: | Size: 740 B |
Binary file not shown.
|
Before Width: | Height: | Size: 752 B |
@ -8,6 +8,11 @@ Change History
|
||||
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| Released On | What's New |
|
||||
+===================================+===================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================+
|
||||
| 2023-01-31 | Modified the following content: |
|
||||
| | |
|
||||
| | - Added description about Redis 6.0, such as :ref:`Redis 6.0 Instance Specifications <dcs-pd-0916004>`. |
|
||||
| | - Added :ref:`Configuring SSL <dcs-ug-023129>`. |
|
||||
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| 2022-10-19 | Added the following FAQs: |
|
||||
| | |
|
||||
| | :ref:`Why Does a Key Disappear in Redis? <dcs-faq-210409001>` |
|
||||
@ -24,7 +29,7 @@ Change History
|
||||
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| 2022-08-29 | Modified the following content: |
|
||||
| | |
|
||||
| | Added description about security groups and whitelist configuration in sections :ref:`Creating a DCS Redis Instance <dcs-ug-0326008>`, :ref:`Security Group Configurations <en-us_topic_0090662012>`, :ref:`What Should I Do If an Error Is Returned When I Use the Jedis Connection Pool? <dcs-faq-0730006>`, :ref:`How Do I Troubleshoot Redis Connection Failures? <dcs-faq-0730010>`, and :ref:`Why Aren't Security Groups Configured for DCS Redis 4.0 and 5.0 Instances? <dcs-faq-0730014>` |
|
||||
| | Added description about security groups and whitelist configuration in sections :ref:`Creating a DCS Redis Instance <dcs-ug-0326008>`, :ref:`Security Group Configurations <en-us_topic_0090662012>`, :ref:`What Should I Do If an Error Is Returned When I Use the Jedis Connection Pool? <dcs-faq-0730006>`, :ref:`How Do I Troubleshoot Redis Connection Failures? <dcs-faq-0730010>`, and :ref:`Why Aren't Security Groups Configured for DCS Redis 4.0/5.0/6.0 Instances? <dcs-faq-0730014>` |
|
||||
+-----------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| 2022-08-09 | Modified the following content: |
|
||||
| | |
|
||||
@ -49,7 +54,7 @@ Change History
|
||||
| | - Updated the commands supported and disabled by Web CLI in section :ref:`Web CLI Commands <dcs-pd-190826001>`. |
|
||||
| | - Added the following FAQs: |
|
||||
| | |
|
||||
| | - :ref:`Why Aren't Security Groups Configured for DCS Redis 4.0 and 5.0 Instances? <dcs-faq-0730014>` |
|
||||
| | - :ref:`Why Aren't Security Groups Configured for DCS Redis 4.0/5.0/6.0 Instances? <dcs-faq-0730014>` |
|
||||
| | - :ref:`Can I Obtain the Addresses of the Nodes in a Cluster DCS Redis Instance? <dcs-faq-0730017>` |
|
||||
| | - :ref:`Does DCS for Redis Provide Backend Management Software? <dcs-faq-0730032>` |
|
||||
| | - :ref:`Why Is "Error in execution" Returned When I Access Redis? <dcs-faq-210223001>` |
|
||||
@ -89,7 +94,7 @@ Change History
|
||||
| | - Modified description about the process for creating instances and added description about creating DCS Redis 4.0 and 5.0 instances in section :ref:`Creating a DCS Redis Instance <dcs-ug-0326008>`. |
|
||||
| | - Added the description about the sold-out tip for the AZ parameter in section :ref:`Creating a DCS Redis Instance <dcs-ug-0326008>`. |
|
||||
| | - Modified descriptions in sections :ref:`Accessing a DCS Redis Instance Through redis-cli <dcs-ug-0326009>` and :ref:`Jedis <dcs-ug-0713005>`. |
|
||||
| | - Added section :ref:`Accessing a DCS Redis 4.0 or 5.0 Instance on the Console <dcs-ug-0312008>`. |
|
||||
| | - Added section :ref:`Accessing a DCS Redis 4.0/5.0/6.0 Instance on the Console <dcs-ug-0312008>`. |
|
||||
| | - Added description about DCS Redis 4.0 and 5.0 instances in section :ref:`Viewing Details of a DCS Instance <dcs-ug-0312016>`. |
|
||||
| | - Optimized the classification of operations in chapter :ref:`Operation Guide <dcs-ug-0326010>`. |
|
||||
| | - Added notes on changing the DCS instance specifications in section :ref:`Modifying DCS Instance Specifications <dcs-ug-0326011>`. |
|
||||
|
||||
@ -29,7 +29,7 @@ How Do I Troubleshoot Redis Connection Failures?
|
||||
|
||||
For details, see :ref:`Security Group Configurations <en-us_topic_0090662012>`.
|
||||
|
||||
- For a DCS Redis 4.0 or 5.0 instance, check the whitelist configuration.
|
||||
- For a DCS Redis 4.0/5.0/6.0 instance, check the whitelist configuration.
|
||||
|
||||
If the instance has a whitelist, ensure that the client IP address is included in the whitelist. Otherwise, the connection will fail.
|
||||
|
||||
|
||||
@ -5,10 +5,10 @@
|
||||
Security Group Configurations
|
||||
=============================
|
||||
|
||||
DCS Redis 3.0/4.0/5.0 instances are deployed in different modes. Therefore, the access control method varies.
|
||||
DCS helps you control access to your DCS instances in the following ways, depending on the deployment mode:
|
||||
|
||||
- To control access to DCS Redis 3.0 instances, you can use security groups. Whitelists are not supported. Security group operations are described in this section.
|
||||
- To control access to DCS Redis 4.0/5.0 instances, you can use whitelists. Security groups are not supported. Whitelist operations are described in :ref:`Managing IP Address Whitelist <dcs-ug-190812001>`.
|
||||
- To control access to DCS Redis 4.0/5.0/6.0 instances, you can use whitelists. Security groups are not supported. Whitelist operations are described in :ref:`Managing IP Address Whitelist <dcs-ug-190812001>`.
|
||||
|
||||
This section describes how to configure a security group for accessing a DCS instance **within a VPC**.
|
||||
|
||||
|
||||
@ -11,6 +11,6 @@ Can I Export Backup Data of DCS Redis Instances to RDB Files Using the Console?
|
||||
|
||||
**redis-cli -h {redis_address} -p 6379 [-a password] --rdb {output.rdb}**
|
||||
|
||||
- Redis 4.0 and 5.0
|
||||
- Redis 4.0/5.0
|
||||
|
||||
Yes. Backup data of a DCS Redis 4.0 or 5.0 instance is exported from the console to RDB files. You cannot use redis-cli to export such data to RDB files.
|
||||
Yes. DCS Redis 4.0/5.0/6.0 instances support AOF and RDB persistence. You can back up data to RDB and AOF files on the console and download the files.
|
||||
|
||||
@ -7,32 +7,23 @@ Are Services Interrupted During Specification Modification?
|
||||
|
||||
You are advised to change the instance specifications during off-peak hours because specification modification has the following impacts:
|
||||
|
||||
- **Impact of instance type changes:**
|
||||
|
||||
- From single-node to master/standby for a DCS Redis 3.0 instance:
|
||||
|
||||
The instance cannot be connected for several seconds and remains read-only for about 1 minute.
|
||||
|
||||
- From master/standby to Proxy Cluster for a DCS Redis 3.0 instance:
|
||||
|
||||
The instance cannot be connected and remains read-only for 5 to 30 minutes.
|
||||
|
||||
- **Impact of capacity expansion and reduction:**
|
||||
- **Impact of scaling:**
|
||||
|
||||
- Single-node and master/standby
|
||||
|
||||
The DCS Redis 3.0, 4.0, or 5.0 instance cannot be connected for several seconds and remains read-only for about 1 minute.
|
||||
- A DCS Redis 4.0/5.0/6.0 instance will be disconnected for several seconds and remain read-only for about 1 minute.
|
||||
- A DCS Redis 3.0 instance will be disconnected and remain read-only for 5 to 30 minutes.
|
||||
- For scaling up, only the memory of the instance is expanded. The CPU processing capability is not improved.
|
||||
- Data of single-node instances may be lost because they do not support data persistence. After scaling, check whether the data is complete and import data if required.
|
||||
- Backup records of master/standby instances cannot be used after scaling down.
|
||||
|
||||
For capacity expansion, only the memory of the instance is expanded. The CPU processing capability is not improved.
|
||||
- Cluster
|
||||
|
||||
Data of single-node instances may not be retained because they do not support data persistence. After the scaling, check whether the data is complete and import data if required.
|
||||
|
||||
- Proxy Cluster
|
||||
|
||||
The instance can be connected, but the CPU will be occupied and the latency will increase during data migration. During capacity expansion, new Redis Server nodes are added, and data is automatically balanced to the new nodes.
|
||||
|
||||
- Redis Cluster
|
||||
|
||||
The instance can be connected, but the CPU usage and latency will increase during data migration. During capacity expansion, new Redis Server nodes are added, and data is automatically balanced to the new nodes.
|
||||
|
||||
- Backup records created before the capacity change cannot be restored.
|
||||
- If the shard quantity is not decreased, the instance can always be connected, but the CPU usage will increase, compromising performance by up to 20%, and the latency will increase during data migration.
|
||||
- During scaling up, new Redis Server nodes are added, and data is automatically balanced to the new nodes.
|
||||
- Nodes will be deleted if the shard quantity decreases. To prevent disconnection, ensure that the deleted nodes are not directly referenced in your application.
|
||||
- Ensure that the used memory of each node is less than 70% of the maximum memory per node of the new flavor. Otherwise, you cannot perform the scale-in.
|
||||
- If the memory becomes full during scaling due to a large amount of data being written, scaling will fail. Modify specifications during off-peak hours.
|
||||
- Scaling involves data migration. The latency for accessing the key being migrated increases. For a Redis Cluster instance, ensure that the client can properly process the **MOVED** and **ASK** commands. Otherwise, requests will fail.
|
||||
- Before scaling, perform cache analysis to ensure that no big keys (>= 512 MB) exist in the instance. Otherwise, scaling may fail.
|
||||
- Backup records created before scaling cannot be restored.
|
||||
|
||||
@ -2,9 +2,9 @@
|
||||
|
||||
.. _dcs-faq-0730043:
|
||||
|
||||
Can DCS Redis Instances Be Upgraded, for Example, from Redis 3.0 to Redis 4.0 or 5.0?
|
||||
=====================================================================================
|
||||
Can DCS Redis Instances Be Upgraded, for Example, from Redis 4.0 to 5.0?
|
||||
========================================================================
|
||||
|
||||
No. Different Redis versions use different underlying architectures. The Redis version used by a DCS instance cannot be changed once the instance is created. However, you will be informed of any defects or problems found in Redis.
|
||||
No. Different Redis versions use different underlying architectures. The Redis version used by a DCS instance cannot be changed once the instance is created. For example, you cannot change a DCS Redis 4.0 instance to Redis 5.0. However, you will be informed of any defects or problems found in Redis.
|
||||
|
||||
If your service requires the features of higher Redis versions, create a DCS Redis instance of a higher version and then migrate data from the original instance to the new one. For details on how to migrate data, see :ref:`Migrating Data with DCS <dcs-ug-0312035>`.
|
||||
@ -5,7 +5,7 @@
|
||||
Instance Scaling and Upgrade
|
||||
============================
|
||||
|
||||
- :ref:`Can DCS Redis Instances Be Upgraded, for Example, from Redis 3.0 to Redis 4.0 or 5.0? <dcs-faq-0730043>`
|
||||
- :ref:`Can DCS Redis Instances Be Upgraded, for Example, from Redis 4.0 to 5.0? <dcs-faq-0730043>`
|
||||
- :ref:`Are Services Interrupted If Maintenance is Performed During the Maintenance Time Window? <dcs-faq-0730044>`
|
||||
- :ref:`Are Instance Resources Affected During Specification Modification? <dcs-faq-0730045>`
|
||||
- :ref:`Are Services Interrupted During Specification Modification? <dcs-faq-0730047>`
|
||||
@ -15,7 +15,7 @@ Instance Scaling and Upgrade
|
||||
:maxdepth: 1
|
||||
:hidden:
|
||||
|
||||
can_dcs_redis_instances_be_upgraded_for_example_from_redis_3.0_to_redis_4.0_or_5.0
|
||||
can_dcs_redis_instances_be_upgraded_for_example_from_redis_4.0_to_5.0
|
||||
are_services_interrupted_if_maintenance_is_performed_during_the_maintenance_time_window
|
||||
are_instance_resources_affected_during_specification_modification
|
||||
are_services_interrupted_during_specification_modification
|
||||
|
||||
@ -5,4 +5,8 @@
|
||||
Why Is the Rejected Connections Metric Displayed?
|
||||
=================================================
|
||||
|
||||
If the **Rejected Connections** metric is displayed, check if the number of connected clients exceeds the maximum allowed number of connections of the instances. To check the maximum allowed number of connections, go to the **Parameters** tab page of the instance and check the value of the **maxclients** parameter.
|
||||
If the **Rejected Connections** metric is displayed, check if the number of connected clients exceeds the maximum allowed number of connections of the instances.
|
||||
|
||||
To check the maximum allowed number of connections, go to the **Parameters** tab page of the instance and check the value of the **maxclients** parameter. (Proxy Cluster instances do not have this parameter. You can view the maximum number of connections on the instance creation page.)
|
||||
|
||||
To check the current number of connections, go to the **Performance Monitoring** tab page of the instance and check the **Connected Clients** metric.
|
||||
|
||||
@ -15,14 +15,14 @@ How Do I Clear Redis Data?
|
||||
|
||||
Run the **FLUSHDB** command to clear the data in the currently selected DB.
|
||||
|
||||
- Redis 4.0 and 5.0
|
||||
- Redis 4.0/5.0/6.0
|
||||
|
||||
To clear data of a DCS Redis 4.0 or 5.0 instance, you can run the **FLUSHDB** or **FLUSHALL** command in redis-cli, use the data clearing function on the DCS console, or run the **FLUSHDB** command on Web CLI.
|
||||
To clear data of a DCS Redis 4.0/5.0/6.0 instance, you can run the **FLUSHDB** or **FLUSHALL** command in redis-cli, use the data clearing function on the DCS console, or run the **FLUSHDB** command on Web CLI.
|
||||
|
||||
To clear data of a Redis Cluster instance, run the **FLUSHDB** or **FLUSHALL** command on every shard of the instance. Otherwise, data may not be completely cleared.
|
||||
|
||||
.. note::
|
||||
|
||||
- Currently, only DCS Redis 4.0 and 5.0 instances support data clearing by using the DCS console and by running the **FLUSHDB** command on Web CLI.
|
||||
- Currently, only DCS Redis 4.0 and later instances support data clearing by using the DCS console and by running the **FLUSHDB** command on Web CLI.
|
||||
- When you run the **FLUSHDB** command on Web CLI, only one shard is cleared at a time. If there are multiple shards, connect to and run the **FLUSHDB** command on each master node.
|
||||
- Redis Cluster data cannot be cleared by using Web CLI.
|
||||
|
||||
@ -5,14 +5,14 @@
|
||||
Can I Customize or Change the Port for Accessing a DCS Instance?
|
||||
================================================================
|
||||
|
||||
You cannot customize or change the port for accessing a DCS Redis 3.0 instance. You can customize and change the port for accessing a DCS Redis 4.0 or 5.0 instance.
|
||||
You cannot customize or change the port for accessing a DCS Redis 3.0 instance. You can customize and change the port for accessing a DCS Redis 4.0 or later instance.
|
||||
|
||||
- Redis 3.0
|
||||
|
||||
Use port 6379 for intra-VPC access.
|
||||
|
||||
- Redis 4.0 and Redis 5.0
|
||||
- Redis 4.0 and later
|
||||
|
||||
You can specify a port (ranging from 1 to 65535) or use the default port (6379) for accessing a DCS Redis 4.0 or 5.0 instance. If no port is specified, the default port will be used.
|
||||
You can specify a port (ranging from 1 to 65535) or use the default port (6379) for accessing an instance. If no port is specified, the default port will be used.
|
||||
|
||||
If the instance and the client use different security groups, you must configure access rules for the security groups, allowing access through the specified port. For details, see :ref:`Security Group Configurations <en-us_topic_0090662012>`.
|
||||
|
||||
@ -7,7 +7,7 @@ Can I Obtain the Addresses of the Nodes in a Cluster DCS Redis Instance?
|
||||
|
||||
Cluster DCS Redis 3.0 instances (Proxy Cluster type) are used in the same way that you use single-node or master/standby instances. You do not need to know the backend node addresses.
|
||||
|
||||
For a cluster DCS Redis 4.0 or 5.0 instance (Redis Cluster type), run the **CLUSTER NODES** command to obtain node addresses:
|
||||
For a cluster DCS Redis 4.0/5.0/ instance (Redis Cluster type), run the **CLUSTER NODES** command to obtain node addresses:
|
||||
|
||||
**redis-cli -h {redis_address} -p {redis_port} -a {redis_password} cluster nodes**
|
||||
|
||||
|
||||
@ -5,6 +5,6 @@
|
||||
Does DCS for Redis Support Sentinel?
|
||||
====================================
|
||||
|
||||
Yes. Redis Sentinel is supported by DCS for Redis 4.0 and 5.0 and is enabled by default. Sentinel constantly checks if master and replica nodes are running properly. If the master is not running properly, Sentinel starts a failover process and promotes a replica to master.
|
||||
Cluster instances and master/standby DCS Redis 4.0/5.0/6.0 instances support Sentinels. Sentinels monitor the running status of both the master and standby nodes of a master/standby instance and each shard of a cluster instance. If the master node becomes faulty, a failover will be performed.
|
||||
|
||||
However, DCS for Redis 3.0 does not support Redis Sentinel. Instead, it uses keepalive to monitor master and replica nodes and to manage failovers.
|
||||
|
||||
@ -7,7 +7,7 @@ Redis Usage
|
||||
|
||||
- :ref:`Why Is CPU Usage of a DCS Redis Instance 100%? <dcs-faq-0730012>`
|
||||
- :ref:`Can I Change the VPC and Subnet for a DCS Redis Instance? <dcs-faq-0730013>`
|
||||
- :ref:`Why Aren't Security Groups Configured for DCS Redis 4.0 and 5.0 Instances? <dcs-faq-0730014>`
|
||||
- :ref:`Why Aren't Security Groups Configured for DCS Redis 4.0/5.0/6.0 Instances? <dcs-faq-0730014>`
|
||||
- :ref:`Do DCS Redis Instances Limit the Size of a Key or Value? <dcs-faq-0730015>`
|
||||
- :ref:`Can I Obtain the Addresses of the Nodes in a Cluster DCS Redis Instance? <dcs-faq-0730017>`
|
||||
- :ref:`Why Is Available Memory of a DCS Redis 3.0 Instance Smaller Than Instance Cache Size? <dcs-faq-0730018>`
|
||||
@ -35,7 +35,7 @@ Redis Usage
|
||||
|
||||
why_is_cpu_usage_of_a_dcs_redis_instance_100pct
|
||||
can_i_change_the_vpc_and_subnet_for_a_dcs_redis_instance
|
||||
why_arent_security_groups_configured_for_dcs_redis_4.0_and_5.0_instances
|
||||
why_arent_security_groups_configured_for_dcs_redis_4.0_5.0_6.0_instances
|
||||
do_dcs_redis_instances_limit_the_size_of_a_key_or_value
|
||||
can_i_obtain_the_addresses_of_the_nodes_in_a_cluster_dcs_redis_instance
|
||||
why_is_available_memory_of_a_dcs_redis_3.0_instance_smaller_than_instance_cache_size
|
||||
|
||||
@ -0,0 +1,12 @@
|
||||
:original_name: dcs-faq-0730014.html
|
||||
|
||||
.. _dcs-faq-0730014:
|
||||
|
||||
Why Aren't Security Groups Configured for DCS Redis 4.0/5.0/6.0 Instances?
|
||||
==========================================================================
|
||||
|
||||
Currently, DCS Redis 4.0/5.0/6.0 instances use VPC endpoints and do not support security groups. You can configure whitelists instead. For details, see :ref:`Managing IP Address Whitelist <dcs-ug-190812001>`.
|
||||
|
||||
To allow access only from specific IP addresses to a DCS Redis instance, add the IP addresses to the instance whitelist.
|
||||
|
||||
If no whitelists are added to the instance whitelist or the whitelist function is disabled, all IP addresses that can communicate with the VPC can access the instance.
|
||||
@ -1,12 +0,0 @@
|
||||
:original_name: dcs-faq-0730014.html
|
||||
|
||||
.. _dcs-faq-0730014:
|
||||
|
||||
Why Aren't Security Groups Configured for DCS Redis 4.0 and 5.0 Instances?
|
||||
==========================================================================
|
||||
|
||||
Currently, DCS Redis 4.0 and Redis 5.0 instances use VPC endpoints and do not support security groups. You can configure whitelists instead. For details, see :ref:`Managing IP Address Whitelist <dcs-ug-190812001>`.
|
||||
|
||||
To allow access only from specific IP addresses to a DCS Redis 4.0 or 5.0 instance, add the IP addresses to the instance whitelist.
|
||||
|
||||
If no whitelists are added to the instance whitelist or the whitelist function is disabled, all IP addresses that can communicate with the VPC can access the instance.
|
||||
@ -48,7 +48,7 @@ Procedure
|
||||
|
||||
a. Install Python and redis-py.
|
||||
|
||||
#. If the system does not provide Python, run the following **yum** command to install it.
|
||||
#. If the system does not provide Python, run the **yum** command to install it.
|
||||
|
||||
#. Run the following command to download and decompress the redis-py package:
|
||||
|
||||
@ -116,15 +116,15 @@ Procedure
|
||||
|
||||
#. Run the **python** command to enter the CLI mode.
|
||||
|
||||
#. Run the following command to access the chosen DCS Redis instance:
|
||||
#. Run the following command to access the chosen DCS Redis instance. If the instance does not have a password, exclude **password='******'** from the command.
|
||||
|
||||
.. code-block::
|
||||
|
||||
>>> from rediscluster import RedisCluster
|
||||
|
||||
>>> startup_nodes = [{"host": "192.168.0.143", "port": "6379"}]
|
||||
>>> startup_nodes = [{"host": "192.168.0.143", "port": "6379"},{"host": "192.168.0.144", "port": "6379"},{"host": "192.168.0.145", "port": "6379"},{"host": "192.168.0.146", "port": "6379"}]
|
||||
|
||||
>>> rc = RedisCluster(startup_nodes=startup_nodes, decode_responses=True)
|
||||
>>> rc = RedisCluster(startup_nodes=startup_nodes, decode_responses=True, password='******')
|
||||
|
||||
>>> rc.set("foo", "bar")
|
||||
True
|
||||
|
||||
@ -2,10 +2,10 @@
|
||||
|
||||
.. _dcs-ug-0312008:
|
||||
|
||||
Accessing a DCS Redis 4.0 or 5.0 Instance on the Console
|
||||
========================================================
|
||||
Accessing a DCS Redis 4.0/5.0/6.0 Instance on the Console
|
||||
=========================================================
|
||||
|
||||
Access a DCS Redis instance through Web CLI. This function is supported only by DCS Redis 4.0 and 5.0 instances, and not by DCS Redis 3.0 instances.
|
||||
Access a DCS Redis instance through Web CLI. This function is supported only by DCS Redis 4.0 and later instances, and not by DCS Redis 3.0 instances.
|
||||
|
||||
.. note::
|
||||
|
||||
@ -16,7 +16,7 @@ Access a DCS Redis instance through Web CLI. This function is supported only by
|
||||
Prerequisites
|
||||
-------------
|
||||
|
||||
The DCS Redis 4.0 or 5.0 instance you want to access through Web CLI is in the **Running** state.
|
||||
The instance is in the **Running** state.
|
||||
|
||||
Procedure
|
||||
---------
|
||||
@ -9,13 +9,13 @@ Access a DCS Redis instance through redis-cli on an ECS in the same VPC. For mor
|
||||
|
||||
.. note::
|
||||
|
||||
- Redis 3.0 does not support port customization and allows only port 6379. For Redis 4.0 and 5.0, you can specify a port or use the default port 6379. The following uses the default port 6379. If you have specified a port, replace 6379 with the actual port.
|
||||
- Redis 3.0 does not support port customization and allows only port 6379. For Redis 4.0 and later, you can specify a port or use the default port 6379. The following uses the default port 6379. If you have specified a port, replace 6379 with the actual port.
|
||||
|
||||
- **When connecting to a Redis Cluster instance, ensure that** **-c** **is added to the command.** Otherwise, the connection will fail.
|
||||
|
||||
- Run the following command to connect to a Redis Cluster instance:
|
||||
|
||||
./redis-cli -h *{dcs_instance_address}* -p 6379 -a *{password}* **-c**
|
||||
./redis-cli -h *{dcs_instance_address}* -p *6379* -a *{password}* **-c**
|
||||
|
||||
- Run the following command to connect to a single-node, master/standby, or Proxy Cluster instance:
|
||||
|
||||
@ -23,6 +23,16 @@ Access a DCS Redis instance through redis-cli on an ECS in the same VPC. For mor
|
||||
|
||||
For details, see :ref:`3 <dcs-ug-0326009__en-us_topic_0148195299_li1511472544119>` and :ref:`4 <dcs-ug-0326009__en-us_topic_0148195299_li126171140194317>`.
|
||||
|
||||
- If SSL is enabled for a DCS Redis 6.0 instance, set an SSL certificate path.
|
||||
|
||||
- Run the following command to connect to a Redis Cluster instance:
|
||||
|
||||
./redis-cli -h *{dcs_instance_address}* -p *6379* -a *{password}* -c **--tls --cacert {certification file path}**
|
||||
|
||||
- Run the following command to connect to a single-node, master/standby, or Proxy Cluster instance:
|
||||
|
||||
*./redis-cli -h* *{dcs_instance_address} -p 6379* -a *{password}* **--tls --cacert {certification file path}**
|
||||
|
||||
Prerequisites
|
||||
-------------
|
||||
|
||||
@ -65,7 +75,7 @@ Procedure (Linux)
|
||||
|
||||
Access a DCS instance of a type other than Redis Cluster.
|
||||
|
||||
Perform the following procedure to access a DCS Redis 3.0 instance, or a single-node or master/standby DCS Redis 4.0 or 5.0 instance.
|
||||
Perform the following procedure to access a single-node, master/standby instance.
|
||||
|
||||
**./redis-cli -h** *${instance IP}* **-p 6379 -a** *${password}*
|
||||
|
||||
|
||||
@ -7,7 +7,7 @@ Accessing an Instance
|
||||
|
||||
- :ref:`Accessing a DCS Redis Instance Through redis-cli <dcs-ug-0326009>`
|
||||
- :ref:`Access in Different Languages <dcs-ug-0512002>`
|
||||
- :ref:`Accessing a DCS Redis 4.0 or 5.0 Instance on the Console <dcs-ug-0312008>`
|
||||
- :ref:`Accessing a DCS Redis 4.0/5.0/6.0 Instance on the Console <dcs-ug-0312008>`
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
@ -15,4 +15,4 @@ Accessing an Instance
|
||||
|
||||
accessing_a_dcs_redis_instance_through_redis-cli
|
||||
access_in_different_languages/index
|
||||
accessing_a_dcs_redis_4.0_or_5.0_instance_on_the_console
|
||||
accessing_a_dcs_redis_4.0_5.0_6.0_instance_on_the_console
|
||||
|
||||
@ -31,7 +31,7 @@ Creating a DCS Redis Instance
|
||||
|
||||
b. **Version**:
|
||||
|
||||
Currently, 3.0, 4.0, and 5.0 versions are supported.
|
||||
Currently, versions 3.0/4.0/5.0/6.0 are supported.
|
||||
|
||||
.. note::
|
||||
|
||||
@ -44,7 +44,7 @@ Creating a DCS Redis Instance
|
||||
|
||||
e. Set **Replicas**. The default value is **2** (including the master).
|
||||
|
||||
This parameter is displayed only when you select Redis 4.0 or Redis 5.0 and the instance type is master/standby or Redis Cluster.
|
||||
This parameter is displayed only when you select Redis 4.0/5.0/6.0 and the instance type is master/standby or Redis Cluster.
|
||||
|
||||
f. Select an AZ.
|
||||
|
||||
@ -67,13 +67,13 @@ Creating a DCS Redis Instance
|
||||
|
||||
You can choose to obtain an automatically assigned IP address or manually specify an IP address that is available in the selected subnet.
|
||||
|
||||
For a DCS Redis 4.0 or 5.0 instance, you can specify a port numbering in the range from 1 to 65535. If no port is specified, the default port 6379 will be used. For a DCS Redis 3.0 instance, the port cannot be customized. Port 6379 will be used.
|
||||
For a DCS Redis 4.0 or later instance, you can specify a port numbering in the range from 1 to 65535. If no port is specified, the default port 6379 will be used. For a DCS Redis 3.0 instance, the port cannot be customized. Port 6379 will be used.
|
||||
|
||||
b. Select a security group.
|
||||
|
||||
A security group is a set of rules that control access to ECSs. It provides access policies for mutually trusted ECSs with the same security protection requirements in the same VPC.
|
||||
|
||||
This parameter is displayed only for DCS Redis 3.0 instances. DCS Redis 4.0 and 5.0 instances are based on VPC endpoints and do not support security groups. To control access to a DCS Redis 4.0 or 5.0 instance, configure a whitelist after instance creation. For details, see :ref:`Managing IP Address Whitelist <dcs-ug-190812001>`.
|
||||
This parameter is displayed only for DCS Redis 3.0 instances. DCS Redis 4.0/5.0/6.0 instances are based on VPC endpoints and do not support security groups. To control access to a DCS Redis 4.0/5.0/6.0 instance, configure a whitelist after instance creation. For details, see :ref:`Managing IP Address Whitelist <dcs-ug-190812001>`.
|
||||
|
||||
#. Set the instance password.
|
||||
|
||||
@ -106,7 +106,7 @@ Creating a DCS Redis Instance
|
||||
|
||||
c. Rename critical commands.
|
||||
|
||||
**Command Renaming** is displayed for Redis 4.0 and 5.0. Currently, you can only rename the **COMMAND**, **KEYS**, **FLUSHDB**, **FLUSHALL**, and **HGETALL** commands.
|
||||
**Command Renaming** is displayed for Redis 4.0 and later. Currently, you can only rename the **COMMAND**, **KEYS**, **FLUSHDB**, and **FLUSHALL** commands.
|
||||
|
||||
d. Specify the maintenance window.
|
||||
|
||||
@ -120,12 +120,7 @@ Creating a DCS Redis Instance
|
||||
|
||||
#. Return to the **Cache Manager** page to view and manage your DCS instances.
|
||||
|
||||
a. Creating a single-node or master/standby DCS Redis 3.0 instance takes 5 to 15 minutes. Creating a cluster DCS Redis 3.0 instance takes 30 minutes.
|
||||
|
||||
.. note::
|
||||
|
||||
DCS Redis 4.0 and 5.0 instances are containerized and can be created within seconds.
|
||||
|
||||
a. Creating a single-node or master/standby DCS Redis 3.0 instance takes 5 to 15 minutes. Creating a cluster DCS Redis 3.0 instance takes 30 minutes.DCS Redis 4.0 and later instances are containerized and can be created within seconds.
|
||||
b. After a DCS instance has been successfully created, it enters the **Running** state by default.
|
||||
|
||||
.. note::
|
||||
|
||||
@ -34,52 +34,52 @@ Procedure
|
||||
|
||||
.. table:: **Table 1** Parameters on the Basic Information page of a DCS instance
|
||||
|
||||
+-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| Section | Parameter | Description |
|
||||
+=======================+============================+========================================================================================================================================================+
|
||||
| Instance Details | Name | Name of the chosen instance. To modify the instance name, click the |image2| icon. |
|
||||
+-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Status | State of the chosen instance. |
|
||||
+-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | ID | ID of the chosen instance. |
|
||||
+-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Cache Engine | Cache engine and cache engine version used by the DCS instance. For example, Redis 3.0. |
|
||||
+-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Instance Type | Type of the selected instance. Currently, supported types include single-node, master/standby, Proxy Cluster, and Redis Cluster. |
|
||||
+-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Cache Size | Specification of the chosen instance. |
|
||||
+-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Used/Available Memory (MB) | The used memory space and maximum available memory space of the chosen instance. |
|
||||
| | | |
|
||||
| | | The used memory space includes: |
|
||||
| | | |
|
||||
| | | - Size of data stored on the DCS instance |
|
||||
| | | - Size of Redis-server buffers (including client buffer and repl-backlog) and internal data structures |
|
||||
+-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | CPU | CPU of the DCS instance. |
|
||||
+-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Created | Time at which the chosen instance started to be created. |
|
||||
+-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Run | Time at which the instance was created. |
|
||||
+-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Maintenance | Time range for any scheduled maintenance activities on cache nodes of this DCS instance. To modify the time window, click the |image3| icon. |
|
||||
+-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Description | Description of the chosen DCS instance. To modify the description, click the |image4| icon. |
|
||||
+-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| Connection | Password Protected | Currently, password-protected access and password-free access are supported. |
|
||||
+-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | IP Address | IP address and port number of the chosen instance. |
|
||||
+-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| Network | AZ | Availability zone in which the cache node running the selected DCS instance resides. |
|
||||
+-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | VPC | VPC in which the chosen instance resides. |
|
||||
+-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Subnet | Subnet in which the chosen instance resides. |
|
||||
+-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Security Group | Security group that controls access to the chosen instance. To modify the security group, click the |image5| icon. |
|
||||
| | | |
|
||||
| | | This parameter is displayed only for DCS Redis 3.0 instances. DCS for Redis 4.0 and 5.0 are based on VPC endpoints and do not support security groups. |
|
||||
+-----------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
+-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| Section | Parameter | Description |
|
||||
+=======================+============================+===================================================================================================================================================+
|
||||
| Instance Details | Name | Name of the chosen instance. To modify the instance name, click the |image2| icon. |
|
||||
+-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Status | State of the chosen instance. |
|
||||
+-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | ID | ID of the chosen instance. |
|
||||
+-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Cache Engine | Cache engine and cache engine version used by the DCS instance. For example, Redis 3.0. |
|
||||
+-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Instance Type | Type of the selected instance. Currently, supported types include single-node, master/standby, Proxy Cluster, and Redis Cluster. |
|
||||
+-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Cache Size | Specification of the chosen instance. |
|
||||
+-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Used/Available Memory (MB) | The used memory space and maximum available memory space of the chosen instance. |
|
||||
| | | |
|
||||
| | | The used memory space includes: |
|
||||
| | | |
|
||||
| | | - Size of data stored on the DCS instance |
|
||||
| | | - Size of Redis-server buffers (including client buffer and repl-backlog) and internal data structures |
|
||||
+-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | CPU | CPU of the DCS instance. |
|
||||
+-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Created | Time at which the chosen instance started to be created. |
|
||||
+-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Run | Time at which the instance was created. |
|
||||
+-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Maintenance | Time range for any scheduled maintenance activities on cache nodes of this DCS instance. To modify the time window, click the |image3| icon. |
|
||||
+-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Description | Description of the chosen DCS instance. To modify the description, click the |image4| icon. |
|
||||
+-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| Connection | Password Protected | Currently, password-protected access and password-free access are supported. |
|
||||
+-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | IP Address | IP address and port number of the chosen instance. |
|
||||
+-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| Network | AZ | Availability zone in which the cache node running the selected DCS instance resides. |
|
||||
+-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | VPC | VPC in which the chosen instance resides. |
|
||||
+-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Subnet | Subnet in which the chosen instance resides. |
|
||||
+-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
| | Security Group | Security group that controls access to the chosen instance. To modify the security group, click the |image5| icon. |
|
||||
| | | |
|
||||
| | | This parameter is displayed only for DCS Redis 3.0 instances. Other Redis versions are based on VPC endpoints and do not support security groups. |
|
||||
+-----------------------+----------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
|
||||
.. |image1| image:: /_static/images/en-us_image_0000001194522893.png
|
||||
.. |image2| image:: /_static/images/en-us_image_0266235362.png
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -31,7 +31,7 @@ Procedure
|
||||
|
||||
#. Select a backup file format.
|
||||
|
||||
Only DCS Redis 4.0 and 5.0 instances support backup file format selection.
|
||||
Only DCS Redis 4.0 and later instances support backup file format selection.
|
||||
|
||||
#. In the **Create Backup** dialog box, click **OK**.
|
||||
|
||||
|
||||
@ -60,7 +60,7 @@ Additional Information About Data Backup
|
||||
|
||||
It is advisable to back up instance data during off-peak periods.
|
||||
|
||||
- Storage and pricing of backup files
|
||||
- Storage of backup files
|
||||
|
||||
Backup files are stored to OBS.
|
||||
|
||||
|
||||
@ -17,7 +17,7 @@ By performing big key analysis and hot key analysis, you will have a picture of
|
||||
|
||||
**Notes on hot key analysis:**
|
||||
|
||||
- Only DCS Redis 4.0 and 5.0 instances support hot key analysis, and the **maxmemory-policy** parameter of the instances must be set to **allkeys-lfu** or **volatile-lfu**.
|
||||
- Only DCS Redis 4.0/5.0/6.0 instances support hot key analysis, and the **maxmemory-policy** parameter of the instances must be set to **allkeys-lfu** or **volatile-lfu**.
|
||||
- During hot key analysis, all keys will be traversed. The larger the number of keys, the longer the analysis takes.
|
||||
- Perform hot key analysis shortly after peak hours to ensure the accuracy of the analysis results.
|
||||
- The hot key analysis is performed on the master node of each instance and will reduce the instance access performance by up to 10%.
|
||||
@ -38,7 +38,7 @@ Big Key Analysis Procedure
|
||||
|
||||
#. Click the name of a DCS Redis instance.
|
||||
|
||||
#. Click the **Cache Analysis** tab.
|
||||
#. Choose **Cache Analysis** .
|
||||
|
||||
#. On the **Big Key Analysis** tab page, manually perform big key analysis or schedule daily automatic analysis.
|
||||
|
||||
@ -61,13 +61,13 @@ Hot Key Analysis Procedure
|
||||
|
||||
#. Click the name of a DCS Redis instance.
|
||||
|
||||
#. Click the **Cache Analysis** tab.
|
||||
#. Choose **Cache Analysis** .
|
||||
|
||||
#. On the **Hot Key Analysis** tab page, manually perform hot key analysis or schedule daily automatic analysis.
|
||||
|
||||
.. note::
|
||||
|
||||
The default value of the **maxmemory-policy** parameter of a Redis 4.0 or 5.0 instance is **noeviction**. To perform hot key analysis, set this parameter to **allkeys-lfu** or **volatile-lfu**. If this parameter has already been set to **allkeys-lfu** or **volatile-lfu**, perform hot key analysis right away.
|
||||
If hot key analysis cannot be performed, set **maxmemory-policy** to **allkeys-lfu** or **volatile-lfu**. If this parameter has already been set to **allkeys-lfu** or **volatile-lfu**, perform hot key analysis right away.
|
||||
|
||||
#. After an analysis task completes, click **View** to view the analysis results.
|
||||
|
||||
|
||||
@ -0,0 +1,30 @@
|
||||
:original_name: dcs-ug-023129.html
|
||||
|
||||
.. _dcs-ug-023129:
|
||||
|
||||
Configuring SSL
|
||||
===============
|
||||
|
||||
DCS Redis 6.0 instances support SSL encryption to ensure data transmission security. This function is not available for other instance versions.
|
||||
|
||||
Procedure
|
||||
---------
|
||||
|
||||
#. Log in to the DCS console.
|
||||
#. Click |image1| in the upper left corner of the management console and select the region where your instance is located.
|
||||
#. In the navigation pane, choose **Cache Manager**.
|
||||
#. On the **Cache Manager** page, click a DCS instance.
|
||||
#. In the navigation pane, choose **SSL**.
|
||||
#. Click |image2| next to **SSL Certificate** to enable or disable SSL.
|
||||
|
||||
.. important::
|
||||
|
||||
- This will restart the instance and disconnect it for a few seconds. Wait until off-peak hours and ensure that your application can re-connect.
|
||||
- The restart cannot be undone. For single-node DCS instances and other instances where AOF persistence is disabled (**appendonly** is set to **no**), data will be cleared and ongoing backup tasks will be stopped. Exercise caution when performing this operation.
|
||||
|
||||
#. Click **Download Certificate** to download the SSL certificate.
|
||||
#. Decompress the SSL certificate and upload the decompressed **ca.crt** file to the server where the Redis client is located.
|
||||
#. Add the path of the **ca.crt** file to the command for connecting to the instance. If you use redis-cli to connect to an instance, refer to :ref:`Accessing a DCS Redis Instance Through redis-cli <dcs-ug-0326009>`.
|
||||
|
||||
.. |image1| image:: /_static/images/en-us_image_0148195246.png
|
||||
.. |image2| image:: /_static/images/en-us_image_0000001505063901.png
|
||||
@ -16,6 +16,7 @@ Managing DCS Instances
|
||||
- :ref:`Managing IP Address Whitelist <dcs-ug-190812001>`
|
||||
- :ref:`Viewing Redis Slow Logs <dcs-ug-190926001>`
|
||||
- :ref:`Viewing Redis Run Logs <dcs-ug-1009001>`
|
||||
- :ref:`Configuring SSL <dcs-ug-023129>`
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 1
|
||||
@ -32,3 +33,4 @@ Managing DCS Instances
|
||||
managing_ip_address_whitelist
|
||||
viewing_redis_slow_logs
|
||||
viewing_redis_run_logs
|
||||
configuring_ssl
|
||||
|
||||
@ -7,10 +7,10 @@ Managing IP Address Whitelist
|
||||
|
||||
DCS helps you control access to your DCS instances in the following ways, depending on the deployment mode:
|
||||
|
||||
- To control access to Redis 3.0 instances, you can use security groups. Whitelists are not supported. For details about how to configure a security group, see :ref:`Security Group Configurations <en-us_topic_0090662012>`.
|
||||
- To control access to Redis 4.0 and 5.0 instances, you can use whitelists. Security groups are not supported.
|
||||
- To control access to DCS Redis 3.0 instances, you can use security groups. Whitelists are not supported. For details about how to configure a security group, see :ref:`Security Group Configurations <en-us_topic_0090662012>`.
|
||||
- To control access to DCS Redis 4.0/5.0/6.0 instances, you can use whitelists. Security groups are not supported.
|
||||
|
||||
The following describes how to manage whitelists of a Redis 4.0 or 5.0 instance to allow access only from whitelisted IP addresses. If no whitelists are added for the instance or the whitelist function is disabled, all IP addresses that can communicate with the VPC can access the instance.
|
||||
The following describes how to manage whitelists of a Redis 4.0/5.0/6.0 instance to allow access only from whitelisted IP addresses. If no whitelists are added for the instance or the whitelist function is disabled, all IP addresses that can communicate with the VPC can access the instance.
|
||||
|
||||
Creating a Whitelist Group
|
||||
--------------------------
|
||||
|
||||
@ -5,7 +5,7 @@
|
||||
Managing Shards and Replicas
|
||||
============================
|
||||
|
||||
This section describes how to query the shards and replicas of a DCS Redis 4.0 or 5.0 instance and how to manually promote a replica to master.
|
||||
This section describes how to query the shards and replicas of a DCS Redis 4.0/5.0/6.0 instance and how to manually promote a replica to master.
|
||||
|
||||
Currently, **this function is supported only by Redis Cluster DCS Redis 4.0 or 5.0 instances.**
|
||||
|
||||
@ -32,9 +32,10 @@ Promoting a Replica to Master
|
||||
|
||||
**Figure 1** Lists of shards and replicas
|
||||
|
||||
7. Click **Promote to Master** in the row containing another replica which is in the "Replica" role.
|
||||
7. For a cluster instance, you can promote a replica in a shard to be master.
|
||||
|
||||
8. Click **Yes**.
|
||||
a. Click **Promote to Master** in the row containing another replica which is in the "Replica" role.
|
||||
b. Click **Yes**.
|
||||
|
||||
.. |image1| image:: /_static/images/en-us_image_0000001241411631.png
|
||||
.. |image2| image:: /_static/images/en-us_image_0000001241691605.png
|
||||
|
||||
@ -40,6 +40,8 @@ Procedure
|
||||
| Parameter | Description | Value Range | Default Value |
|
||||
+===============================================+=================================================================================================================================================================================================================================================================================================================================+==================================================+==================================================+
|
||||
| timeout | The maximum amount of time (in seconds) a connection between a client and the DCS instance can be allowed to remain idle before the connection is terminated. A setting of **0** means that this function is disabled. | 0-7200 seconds | 0 |
|
||||
| | | | |
|
||||
| | Proxy Cluster instances do not have this parameter. | | |
|
||||
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
|
||||
| appendfsync | Controls how often fsync() transfers cached data to the disk. Note that some OSs will perform a complete data transfer but some others only make a "best-effort" attempt. | - no | everysec |
|
||||
| | | - always | |
|
||||
@ -85,8 +87,11 @@ Procedure
|
||||
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
|
||||
| master-read-only | Sets the instance to be read-only. All write operations will fail. | - yes | no |
|
||||
| | | - no | |
|
||||
| | Proxy Cluster instances do not have this parameter. | | |
|
||||
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
|
||||
| maxclients | The maximum number of clients allowed to be concurrently connected to a DCS instance. | Depends on the instance type and specifications. | Depends on the instance type and specifications. |
|
||||
| | | | |
|
||||
| | Proxy Cluster instances do not have this parameter. | | |
|
||||
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
|
||||
| proto-max-bulk-len | Maximum size of a single element request (in bytes). | 1,048,576-536,870,912 | 536,870,912 |
|
||||
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
|
||||
@ -139,6 +144,8 @@ Procedure
|
||||
| | **A**: an alias for "g$lshzxe" | | |
|
||||
| | | | |
|
||||
| | The parameter value must contain either **K** or **E**. **A** cannot be used together with any of the characters in "g$lshzxe". For example, the value **Kl** means that Redis will notify Pub/Sub clients about keyspace events and list commands. The value **AKE** means Redis will notify Pub/Sub clients about all events. | | |
|
||||
| | | | |
|
||||
| | Proxy Cluster instances do not have this parameter. | | |
|
||||
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
|
||||
| slowlog-log-slower-than | Redis records queries that exceed a specified execution time. | 0-1,000,000 | 10,000 |
|
||||
| | | | |
|
||||
@ -157,6 +164,8 @@ Procedure
|
||||
- **A** is an alias for "g$lshzxe" and cannot be used together with any of the characters in "g$lshzxe".
|
||||
- For example, the value **Kl** means that Redis will notify Pub/Sub clients about keyspace events and list commands. The value **AKE** means Redis will notify Pub/Sub clients about all events.
|
||||
|
||||
d. Configurable parameters and their values vary depending on the instance type.
|
||||
|
||||
#. After you have finished setting the parameters, click **Save**.
|
||||
|
||||
#. Click **Yes** to confirm the modification.
|
||||
|
||||
@ -31,5 +31,5 @@ Procedure
|
||||
|
||||
.. |image1| image:: /_static/images/en-us_image_0000001148443456.png
|
||||
.. |image2| image:: /_static/images/en-us_image_0266235581.jpg
|
||||
.. |image3| image:: /_static/images/en-us_image_0266235565.jpg
|
||||
.. |image4| image:: /_static/images/en-us_image_0266235461.jpg
|
||||
.. |image3| image:: /_static/images/en-us_image_0266235415.png
|
||||
.. |image4| image:: /_static/images/en-us_image_0266235408.png
|
||||
|
||||
@ -7,7 +7,7 @@ Modifying the Security Group
|
||||
|
||||
On the DCS console, after creating a DCS instance, you can modify the security group of the DCS instance on the instance's **Basic Information** page.
|
||||
|
||||
You can modify the security groups of DCS Redis 3.0 instances but cannot modify those of DCS Redis 4.0 or 5.0 instances.
|
||||
You can modify the security groups of DCS Redis 3.0 instances but cannot modify those of DCS Redis 4.0/5.0/6.0 instances.
|
||||
|
||||
Prerequisites
|
||||
-------------
|
||||
@ -37,5 +37,5 @@ Procedure
|
||||
|
||||
.. |image1| image:: /_static/images/en-us_image_0000001194403153.png
|
||||
.. |image2| image:: /_static/images/en-us_image_0266235582.png
|
||||
.. |image3| image:: /_static/images/en-us_image_0266235565.jpg
|
||||
.. |image4| image:: /_static/images/en-us_image_0266235461.jpg
|
||||
.. |image3| image:: /_static/images/en-us_image_0266235377.png
|
||||
.. |image4| image:: /_static/images/en-us_image_0266235369.png
|
||||
|
||||
@ -35,7 +35,7 @@ Step 1: Prepare the Target DCS Redis Instance
|
||||
- If the target instance is Redis 4.0 or 5.0, clear the data by referring to :ref:`Clearing DCS Instance Data <dcs-ug-0312018>`.
|
||||
- If the target instance is a DCS Redis 3.0 instance, run the **FLUSHALL** command to clear data.
|
||||
|
||||
You can use a DCS Redis 3.0, 4.0, or 5.0 instance as the target instance.
|
||||
You can use a DCS Redis 3.0/4.0/5.0 instance as the target instance.
|
||||
|
||||
Step 2: Create an OBS Bucket and Upload Backup Files
|
||||
----------------------------------------------------
|
||||
|
||||
@ -35,7 +35,7 @@ Step 2: Prepare the Target DCS Redis Instance
|
||||
- If the target instance is Redis 4.0 or 5.0, clear the data by referring to :ref:`Clearing DCS Instance Data <dcs-ug-0312018>`.
|
||||
- If the target instance is a DCS Redis 3.0 instance, run the **FLUSHALL** command to clear data.
|
||||
|
||||
You can use a DCS Redis 3.0, 4.0, or 5.0 instance as the target instance.
|
||||
You can use a DCS Redis 3.0/4.0/5.0 instance as the target instance.
|
||||
|
||||
Step 3: Create a Migration Task
|
||||
-------------------------------
|
||||
|
||||
@ -5,7 +5,7 @@
|
||||
Clearing DCS Instance Data
|
||||
==========================
|
||||
|
||||
On the DCS console, you can clear data only for DCS Redis 4.0 and 5.0 instances.
|
||||
You can clear data of DCS Redis 4.0 and later instances on the console.
|
||||
|
||||
**Clearing instance data cannot be undone and cleared data cannot be recovered. Exercise caution when performing this operation.**
|
||||
|
||||
@ -15,7 +15,7 @@ Procedure
|
||||
#. Log in to the DCS console.
|
||||
#. Click |image1| in the upper left corner and select a region and a project.
|
||||
#. In the navigation pane, choose **Cache Manager**.
|
||||
#. Select one or more DCS2.0 instances to clear.
|
||||
#. Select one or more DCS instances.
|
||||
#. Click **Clear data** above the instance list.
|
||||
#. In the displayed dialog box, click **Yes**.
|
||||
|
||||
|
||||
@ -5,7 +5,7 @@
|
||||
Command Renaming
|
||||
================
|
||||
|
||||
After creating a DCS Redis 4.0 or 5.0 instance, you can rename the following critical commands: **COMMAND**, **KEYS**, **FLUSHDB**, **FLUSHALL**, and **HGETALL**.
|
||||
After creating a DCS Redis 4.0 or later instance, you can rename the following critical commands: Currently, you can only rename the **COMMAND**, **KEYS**, **FLUSHDB**, and **FLUSHALL** commands.
|
||||
|
||||
Procedure
|
||||
---------
|
||||
|
||||
@ -16,8 +16,6 @@ Procedure
|
||||
|
||||
#. In the navigation pane, choose **Cache Manager**.
|
||||
|
||||
#. Click the search bar. In the displayed drop-down list, select the filter criteria to query the desired DCS instances.
|
||||
|
||||
#. Click |image2| above the instance list.
|
||||
|
||||
Click the export result displayed in the lower left corner of the page.
|
||||
|
||||
@ -26,6 +26,7 @@ Scaling
|
||||
Redis 3.0 Scaling up/down Scaling up/down N/A Scaling up
|
||||
Redis 4.0 Scaling up/down Scaling up/down Scaling up N/A
|
||||
Redis 5.0 Scaling up/down Scaling up/down Scaling up N/A
|
||||
Redis 6.0 Scaling up/down Scaling up/down N/A N/A
|
||||
============ =============== =============== ============= =============
|
||||
|
||||
.. note::
|
||||
@ -36,11 +37,11 @@ Scaling
|
||||
|
||||
- Single-node and master/standby
|
||||
|
||||
- A DCS Redis 4.0 or 5.0 instance will be disconnected for several seconds and remain read-only for about 1 minute.
|
||||
- A DCS Redis 4.0/5.0/6.0 instance will be disconnected for several seconds and remain read-only for about 1 minute.
|
||||
- A DCS Redis 3.0 instance will be disconnected and remain read-only for 5 to 30 minutes.
|
||||
- For scaling up, only the memory of the instance is expanded. The CPU processing capability is not improved.
|
||||
- Data of single-node instances may be lost because they do not support data persistence. After scaling, check whether the data is complete and import data if required.
|
||||
- Backup records of master/standby instances cannot be restored after scaling down.
|
||||
- Backup records of master/standby instances cannot be used after scaling down.
|
||||
|
||||
- Cluster
|
||||
|
||||
|
||||
@ -33,7 +33,7 @@ Procedure
|
||||
|
||||
#. In the displayed dialog box, click **Yes**.
|
||||
|
||||
It takes 1 to 30 minutes to restart DCS instances. After DCS instances are restarted, their status changes to **Running**.
|
||||
It takes 10 seconds to 30 minutes to restart DCS instances. After DCS instances are restarted, their status changes to **Running**.
|
||||
|
||||
.. note::
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ There are two ways to access DCS:
|
||||
|
||||
- Using the management console
|
||||
|
||||
The DCS provides a web-based management console. To launch the DCS console, create an account on the management console and log in, and then choose **Database** > **Distributed Cache Service** on the homepage. On the DCS console, you can create, restart, and delete DCS instances, and change their passwords.
|
||||
The DCS provides a web-based management console. To launch the DCS console, create an account on the management console and log in, and then choose **Application** > **Distributed Cache Service** on the homepage. On the DCS console, you can create, restart, and delete DCS instances, and change their passwords.
|
||||
|
||||
- Using APIs
|
||||
|
||||
|
||||
@ -8,6 +8,7 @@ Command Compatibility
|
||||
- :ref:`Redis 3.0 Commands <dcs-pd-200713005>`
|
||||
- :ref:`Redis 4.0 Commands <dcs-pd-200916001>`
|
||||
- :ref:`Redis 5.0 Commands <dcs-pd-200813002>`
|
||||
- :ref:`Redis 6.0 Commands <dcs-pd-210209002>`
|
||||
- :ref:`Web CLI Commands <dcs-pd-190826001>`
|
||||
- :ref:`Command Restrictions for Cluster Instances <dcs-pd-200813003>`
|
||||
- :ref:`Other Command Usage Restrictions <dcs-pd-200813004>`
|
||||
@ -19,6 +20,7 @@ Command Compatibility
|
||||
redis_3.0_commands
|
||||
redis_4.0_commands
|
||||
redis_5.0_commands
|
||||
redis_6.0_commands
|
||||
web_cli_commands
|
||||
command_restrictions_for_cluster_instances
|
||||
other_command_usage_restrictions
|
||||
|
||||
@ -96,7 +96,7 @@ Commands Supported by DCS for Redis 4.0
|
||||
+---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+
|
||||
| ``-`` | PUNSUBSCRIBE | UNWATCH | QUIT | SCRIPT FLUSH | GEODIST |
|
||||
+---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+
|
||||
| ``-`` | SUBSCRIBE | WATCH | SELECT | SCRIPT KILL | GEORADIUS |
|
||||
| ``-`` | SUBSCRIBE | WATCH | SELECT (not supported by Redis Cluster instances) | SCRIPT KILL | GEORADIUS |
|
||||
+---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+
|
||||
| ``-`` | UNSUBSCRIBE | ``-`` | ``-`` | SCRIPT LOAD | GEORADIUSBYMEMBER |
|
||||
+---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+
|
||||
|
||||
@ -94,7 +94,7 @@ Commands Supported by DCS for Redis 5.0
|
||||
+---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+
|
||||
| ``-`` | PUNSUBSCRIBE | UNWATCH | QUIT | SCRIPT FLUSH | GEODIST | XDEL |
|
||||
+---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+
|
||||
| ``-`` | SUBSCRIBE | WATCH | SELECT | SCRIPT KILL | GEORADIUS | XGROUP |
|
||||
| ``-`` | SUBSCRIBE | WATCH | SELECT (not supported by Redis Cluster instances) | SCRIPT KILL | GEORADIUS | XGROUP |
|
||||
+---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+
|
||||
| ``-`` | UNSUBSCRIBE | ``-`` | ``-`` | SCRIPT LOAD | GEORADIUSBYMEMBER | XINFO |
|
||||
+---------------------------------------------------------+------------------------------------------------+-----------------------------------------------------------+-------------------------------------------------------+-----------------------------------------------------+-----------------------------------------+-----------------------------------------------+
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user