ahmet.yildirim/distributed-cache-service
1
0
Fork 0
forked from docs/distributed-cache-service
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update content

Browse Source
This commit is contained in:
OpenTelekomCloud Proposal Bot 2022-10-31 13:09:05 +00:00 committed by Artem Goncharov
parent 47ba3fbbdf
commit a801aab463
29 changed files with 185 additions and 211 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
umn/source/auditing/viewing_traces_on_the_cts_console.rst
View File

@ -47,7 +47,6 @@ Procedure
.. figure:: /_static/images/en-us_image_0266235352.png .. figure:: /_static/images/en-us_image_0266235352.png
:alt: **Figure 1** Expanding trace details :alt: **Figure 1** Expanding trace details
**Figure 1** Expanding trace details **Figure 1** Expanding trace details
#. Click **View Trace** in the **Operation** column. In the dialog box shown in :ref:`Figure 2 <dcs-ug-0312047__en-us_topic_0148195282_fig6764226461>`, the trace structure details are displayed. #. Click **View Trace** in the **Operation** column. In the dialog box shown in :ref:`Figure 2 <dcs-ug-0312047__en-us_topic_0148195282_fig6764226461>`, the trace structure details are displayed.
@ -57,7 +56,6 @@ Procedure
.. figure:: /_static/images/en-us_image_0266235315.png .. figure:: /_static/images/en-us_image_0266235315.png
:alt: **Figure 2** Viewing traces :alt: **Figure 2** Viewing traces
**Figure 2** Viewing traces **Figure 2** Viewing traces
.. |image1| image:: /_static/images/en-us_image_0266235405.png .. |image1| image:: /_static/images/en-us_image_0266235405.png

1
umn/source/faqs/client_and_network_connection/how_do_i_access_a_dcs_redis_instance_through_redis_desktop_manager.rst
View File

@ -17,7 +17,6 @@ You can access a DCS Redis instance through the Redis Desktop Manager within a V
.. figure:: /_static/images/en-us_image_0266315618.png .. figure:: /_static/images/en-us_image_0266315618.png
:alt: **Figure 1** Accessing a DCS Redis instance through Redis Desktop Manager over the intranet :alt: **Figure 1** Accessing a DCS Redis instance through Redis Desktop Manager over the intranet
**Figure 1** Accessing a DCS Redis instance through Redis Desktop Manager over the intranet **Figure 1** Accessing a DCS Redis instance through Redis Desktop Manager over the intranet
.. note:: .. note::

2
umn/source/faqs/client_and_network_connection/security_group_configurations.rst
View File

@ -36,7 +36,6 @@ In addition, you must configure correct rules for the security groups of both th
.. figure:: /_static/images/en-us_image_0277697231.png .. figure:: /_static/images/en-us_image_0277697231.png
:alt: **Figure 1** Security group rules allowing the ECS to access the DCS instance :alt: **Figure 1** Security group rules allowing the ECS to access the DCS instance
**Figure 1** Security group rules allowing the ECS to access the DCS instance **Figure 1** Security group rules allowing the ECS to access the DCS instance
#. Configuring security group for the DCS instance. #. Configuring security group for the DCS instance.
@ -47,7 +46,6 @@ In addition, you must configure correct rules for the security groups of both th
.. figure:: /_static/images/en-us_image_0277697263.png .. figure:: /_static/images/en-us_image_0277697263.png
:alt: **Figure 2** Security group rules making the DCS instance accessible to the ECS :alt: **Figure 2** Security group rules making the DCS instance accessible to the ECS
**Figure 2** Security group rules making the DCS instance accessible to the ECS **Figure 2** Security group rules making the DCS instance accessible to the ECS
.. important:: .. important::

1
umn/source/faqs/client_and_network_connection/what_if_err_unsupported_config_subcommand_is_displayed_in_springcloud.rst
View File

@ -11,7 +11,6 @@ By using DCS Redis instances, Spring Session can implement session sharing. When
.. figure:: /_static/images/en-us_image_0266315619.png .. figure:: /_static/images/en-us_image_0266315619.png
:alt: **Figure 1** Spring Cloud error information :alt: **Figure 1** Spring Cloud error information
**Figure 1** Spring Cloud error information **Figure 1** Spring Cloud error information
For security purposes, DCS does not support the **CONFIG** command initiated by a client. You need to perform the following steps: For security purposes, DCS does not support the **CONFIG** command initiated by a client. You need to perform the following steps:

2
umn/source/faqs/redis_usage/does_dcs_for_redis_support_multiple_databases.rst
View File

@ -5,6 +5,6 @@
Does DCS for Redis Support Multiple Databases? Does DCS for Redis Support Multiple Databases?
============================================== ==============================================
Both single-node and master/standby DCS Redis instances support multiple databases. By default, single-node and master/standby DCS instances can read and write data in 256 databases (databases numbering 0–255). Both single-node and master/standby DCS Redis instances support multiple databases. By default, single-node and master/standby DCS instances can read and write data in 256 databases (databases numbering 0-255).
Cluster DCS instances do not support data read/write in multiple databases. Cluster DCS instances do not support data read/write in multiple databases.

3
umn/source/getting_started/accessing_an_instance/access_in_different_languages/c#.rst
View File

@ -42,7 +42,6 @@ Procedure
.. figure:: /_static/images/en-us_image_0148195318.png .. figure:: /_static/images/en-us_image_0148195318.png
:alt: **Figure 1** Accessing the NuGet package manager console :alt: **Figure 1** Accessing the NuGet package manager console
**Figure 1** Accessing the NuGet package manager console **Figure 1** Accessing the NuGet package manager console
#. Write the following code, and use the String Set and Get methods to test the connection. #. Write the following code, and use the String Set and Get methods to test the connection.
@ -91,7 +90,7 @@ Procedure
} }
} }
*10.10.38.233:6379* contains an example IP address/domain name and port number of the DCS Redis instance. For details about how to obtain the IP address/domain name and port, see :ref:`1 <dcs-ug-0312013__en-us_topic_0148195355_li457118182512>`. Change the IP address/domain name and port as required. *\*******\** indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation. *10.10.38.233:6379* contains an example IP address/domain name and port number of the DCS Redis instance. For details about how to obtain the IP address/domain name and port, see :ref:`1 <dcs-ug-0312013__en-us_topic_0148195355_li457118182512>`. Change the IP address/domain name and port as required. ``********`` indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.
#. Run the code. You have successfully accessed the instance if the following command output is displayed: #. Run the code. You have successfully accessed the instance if the following command output is displayed:

5
umn/source/getting_started/accessing_an_instance/access_in_different_languages/clients_in_python.rst
View File

@ -66,7 +66,6 @@ Procedure
.. figure:: /_static/images/en-us_image_0000001188005622.png .. figure:: /_static/images/en-us_image_0000001188005622.png
:alt: **Figure 1** Running the python command :alt: **Figure 1** Running the python command
**Figure 1** Running the python command **Figure 1** Running the python command
b. Use the redis-py client to connect to the instance. In the following steps, commands are executed in CLI mode. (Alternatively, write the commands into a Python script and then execute the script.) b. Use the redis-py client to connect to the instance. In the following steps, commands are executed in CLI mode. (Alternatively, write the commands into a Python script and then execute the script.)
@ -77,7 +76,6 @@ Procedure
.. figure:: /_static/images/en-us_image_0000001187846598.png .. figure:: /_static/images/en-us_image_0000001187846598.png
:alt: **Figure 2** Entering the CLI mode :alt: **Figure 2** Entering the CLI mode
**Figure 2** Entering the CLI mode **Figure 2** Entering 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:
@ -86,7 +84,7 @@ Procedure
r = redis.StrictRedis(host='XXX.XXX.XXX.XXX', port=6379, password='******'); r = redis.StrictRedis(host='XXX.XXX.XXX.XXX', port=6379, password='******');
*XXX.XXX.XXX.XXX* indicates the IP address/domain name of the DCS instance and **6379** is an example port number of the instance. For details about how to obtain the IP address/domain name and port, see :ref:`1 <dcs-ug-0312011__en-us_topic_0148195287_li450593110588>`. Change the IP address/domain name and port as required. *\*****\** indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation. *XXX.XXX.XXX.XXX* indicates the IP address/domain name of the DCS instance and **6379** is an example port number of the instance. For details about how to obtain the IP address/domain name and port, see :ref:`1 <dcs-ug-0312011__en-us_topic_0148195287_li450593110588>`. Change the IP address/domain name and port as required. ``******`` indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.
You have successfully accessed the instance if the following command output is displayed. Enter commands to perform read and write operations on the database. You have successfully accessed the instance if the following command output is displayed. Enter commands to perform read and write operations on the database.
@ -94,7 +92,6 @@ Procedure
.. figure:: /_static/images/en-us_image_0000001233126245.png .. figure:: /_static/images/en-us_image_0000001233126245.png
:alt: **Figure 3** Redis connected successfully :alt: **Figure 3** Redis connected successfully
**Figure 3** Redis connected successfully **Figure 3** Redis connected successfully
- If the instance is a Redis Cluster instance: - If the instance is a Redis Cluster instance:

2
umn/source/getting_started/accessing_an_instance/access_in_different_languages/go-redis.rst
View File

@ -77,7 +77,7 @@ Procedure
fmt.Println(val1) fmt.Println(val1)
} }
*host:port* are the IP address/domain name and port number of the DCS Redis instance. For details about how to obtain the IP address/domain name and port, see :ref:`1 <dcs-ug-211105001__en-us_topic_0000001174913212_li457118182512>`. Change the IP address/domain name and port as required. *\*******\** indicates the password used to log in to the DCS Redis instance. This password is defined during DCS Redis instance creation. *host:port* are the IP address/domain name and port number of the DCS Redis instance. For details about how to obtain the IP address/domain name and port, see :ref:`1 <dcs-ug-211105001__en-us_topic_0000001174913212_li457118182512>`. Change the IP address/domain name and port as required. ``********`` indicates the password used to log in to the DCS Redis instance. This password is defined during DCS Redis instance creation.
#. Run the **go build -o test main.go** command to package the code into an executable file, for example, **test**. #. Run the **go build -o test main.go** command to package the code into an executable file, for example, **test**.

4
umn/source/getting_started/accessing_an_instance/access_in_different_languages/node.js.rst
View File

@ -89,7 +89,7 @@ Procedure
// All arguments are passed directly to the redis server: // All arguments are passed directly to the redis server:
redis.set('key', 100, 'EX', 10); redis.set('key', 100, 'EX', 10);
*host* indicates the example IP address/domain name of DCS instance and *port* indicates the port number of DCS instance. For details about how to obtain the IP address/domain name and port, see :ref:`1 <dcs-ug-0312012__en-us_topic_0148195323_li5233248151213>`. Change the IP address/domain name and port as required. *\*****\** indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation. *host* indicates the example IP address/domain name of DCS instance and *port* indicates the port number of DCS instance. For details about how to obtain the IP address/domain name and port, see :ref:`1 <dcs-ug-0312012__en-us_topic_0148195323_li5233248151213>`. Change the IP address/domain name and port as required. ``******`` indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.
#. Run the sample script to access the chosen DCS instance. #. Run the sample script to access the chosen DCS instance.
@ -163,7 +163,7 @@ Procedure
// All arguments are passed directly to the redis server: // All arguments are passed directly to the redis server:
redis.set('key', 100, 'EX', 10); redis.set('key', 100, 'EX', 10);
*host* indicates the example IP address/domain name of DCS instance and *port* indicates the port number of DCS instance. For details about how to obtain the IP address/domain name and port, see :ref:`1 <dcs-ug-0312012__en-us_topic_0148195323_li11511175651212>`. Change the IP address/domain name and port as required. *\*****\** indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation. *host* indicates the example IP address/domain name of DCS instance and *port* indicates the port number of DCS instance. For details about how to obtain the IP address/domain name and port, see :ref:`1 <dcs-ug-0312012__en-us_topic_0148195323_li11511175651212>`. Change the IP address/domain name and port as required. ``******`` indicates the password used for logging in to the chosen DCS Redis instance. This password is defined during DCS Redis instance creation.
#. Run the sample script to access the chosen DCS instance. #. Run the sample script to access the chosen DCS instance.

2
umn/source/getting_started/creating_an_instance/creating_a_dcs_redis_instance.rst
View File

@ -92,7 +92,7 @@ Creating a DCS Redis Instance
- Lowercase letters - Lowercase letters
- Uppercase letters - Uppercase letters
- Digits - Digits
- special characters (:literal:`\`~!@#$^&*()-_=+\|{}:,<.>/?`) - special characters (:literal:`\`~!@#$^&*()-_=+\\|{}:,<.>/?`)
#. Click **More Settings** to display more configurations, including auto backup. #. Click **More Settings** to display more configurations, including auto backup.

10
umn/source/monitoring/configuring_alarm_rules_for_critical_metrics.rst
View File

@ -15,25 +15,25 @@ Alarm Policies for DCS Redis Instances
+-------------------+--------------+-----------------------------------------------+----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-------------------+--------------+-----------------------------------------------+----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Metric | Normal Range | Alarm Policy | Approach Upper Limit | Handling Suggestion | | Metric | Normal Range | Alarm Policy | Approach Upper Limit | Handling Suggestion |
+===================+==============+===============================================+======================+==============================================================================================================================================================================+ +===================+==============+===============================================+======================+==============================================================================================================================================================================+
| CPU Usage | 0–100 | Alarm threshold: 70 | No | Consider capacity expansion based on the service analysis. | | CPU Usage | 0-100 | Alarm threshold: 70 | No | Consider capacity expansion based on the service analysis. |
| | | | | | | | | | | |
| | | Number of consecutive periods: 2 | | The CPU capacity of a single-node or master/standby instance cannot be expanded. If you need larger capacity, use a cluster instance instead. | | | | Number of consecutive periods: 2 | | The CPU capacity of a single-node or master/standby instance cannot be expanded. If you need larger capacity, use a cluster instance instead. |
| | | | | | | | | | | |
| | | Alarm severity: Major | | | | | | Alarm severity: Major | | |
+-------------------+--------------+-----------------------------------------------+----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-------------------+--------------+-----------------------------------------------+----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Memory Usage | 0–100 | Alarm threshold: 70 | No | Expand the capacity of the instance. | | Memory Usage | 0-100 | Alarm threshold: 70 | No | Expand the capacity of the instance. |
| | | | | | | | | | | |
| | | Number of consecutive periods: 2 | | | | | | Number of consecutive periods: 2 | | |
| | | | | | | | | | | |
| | | Alarm severity: Major | | | | | | Alarm severity: Major | | |
+-------------------+--------------+-----------------------------------------------+----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-------------------+--------------+-----------------------------------------------+----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Connected Clients | 0–10,000 | Alarm threshold: 8000 | No | Optimize the connection pool in the service code to prevent the number of connections from exceeding the maximum limit. | | Connected Clients | 0-10,000 | Alarm threshold: 8000 | No | Optimize the connection pool in the service code to prevent the number of connections from exceeding the maximum limit. |
| | | | | | | | | | | |
| | | Number of consecutive periods: 2 | | For single-node and master/standby instances, the maximum number of connections allowed is 10,000. You can adjust the threshold based on service requirements. | | | | Number of consecutive periods: 2 | | For single-node and master/standby instances, the maximum number of connections allowed is 10,000. You can adjust the threshold based on service requirements. |
| | | | | | | | | | | |
| | | Alarm severity: Major | | | | | | Alarm severity: Major | | |
+-------------------+--------------+-----------------------------------------------+----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-------------------+--------------+-----------------------------------------------+----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| New Connections | 0–10,000 | Alarm threshold: 10,000 | - | Check whether **connect** is used and whether the client connection is abnormal. Use persistent connections ("pconnect" in Redis terminology) to ensure performance. | | New Connections | 0-10,000 | Alarm threshold: 10,000 | - | Check whether **connect** is used and whether the client connection is abnormal. Use persistent connections ("pconnect" in Redis terminology) to ensure performance. |
| | | | | | | | | | | |
| (Count/min) | | Number of consecutive periods: 2 | | | | (Count/min) | | Number of consecutive periods: 2 | | |
| | | | | | | | | | | |
@ -69,7 +69,6 @@ In the following example, an alarm rule is set for the **CPU Usage** metric.
.. figure:: /_static/images/en-us_image_0270432745.png .. figure:: /_static/images/en-us_image_0270432745.png
:alt: **Figure 1** Viewing instance metrics :alt: **Figure 1** Viewing instance metrics
**Figure 1** Viewing instance metrics **Figure 1** Viewing instance metrics
#. Locate the **CPU Usage** metric. Hover over the metric and click |image2| to create an alarm rule for the metric. #. Locate the **CPU Usage** metric. Hover over the metric and click |image2| to create an alarm rule for the metric.
@ -86,7 +85,6 @@ In the following example, an alarm rule is set for the **CPU Usage** metric.
.. figure:: /_static/images/en-us_image_0000001321666164.png .. figure:: /_static/images/en-us_image_0000001321666164.png
:alt: **Figure 2** Setting the alarm content :alt: **Figure 2** Setting the alarm content
**Figure 2** Setting the alarm content **Figure 2** Setting the alarm content
b. Set the alarm notification configurations. If you enable **Alarm Notification**, set the validity period, notification object, and trigger condition. b. Set the alarm notification configurations. If you enable **Alarm Notification**, set the validity period, notification object, and trigger condition.

262
umn/source/monitoring/dcs_metrics.rst
View File

File diff suppressed because it is too large Load Diff

2
umn/source/operation_guide/backing_up_and_restoring_dcs_instances/configuring_a_backup_policy.rst
View File

@ -35,7 +35,7 @@ Procedure
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Retention Period (days) | The number of days that automatically backed up data is retained. | | Retention Period (days) | The number of days that automatically backed up data is retained. |
| | | | | |
| | Backup data will be permanently deleted at the end of retention period and cannot be restored. Value range: 1–7. | | | Backup data will be permanently deleted at the end of retention period and cannot be restored. Value range: 1-7. |
+-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +-----------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Start Time | Time at which automatic backup starts. Value: the full hour between 00:00 to 23:00 | | Start Time | Time at which automatic backup starts. Value: the full hour between 00:00 to 23:00 |
| | | | | |

1
umn/source/operation_guide/managing_dcs_instances/managing_shards_and_replicas.rst
View File

@ -30,7 +30,6 @@ Promoting a Replica to Master
.. figure:: /_static/images/en-us_image_0000001322339434.png .. figure:: /_static/images/en-us_image_0000001322339434.png
:alt: **Figure 1** Lists of shards and replicas :alt: **Figure 1** Lists of shards and replicas
**Figure 1** Lists of shards and replicas **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. Click **Promote to Master** in the row containing another replica which is in the "Replica" role.

30
umn/source/operation_guide/managing_dcs_instances/modifying_configuration_parameters.rst
View File

@ -39,7 +39,7 @@ Procedure
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
| Parameter | Description | Value Range | Default Value | | 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 | | 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 |
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
| 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 | | 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 | | | | | - always | |
@ -57,7 +57,7 @@ Procedure
| | | | | | | | | |
| | no: disabled | | | | | no: disabled | | |
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
| client-output-buffer-limit-slave-soft-seconds | Number of seconds that the output buffer remains above **client-output-buffer-slave-soft-limit** before the client is disconnected. | 0–60 | 60 | | client-output-buffer-limit-slave-soft-seconds | Number of seconds that the output buffer remains above **client-output-buffer-slave-soft-limit** before the client is disconnected. | 0-60 | 60 |
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
| client-output-buffer-slave-hard-limit | Hard limit (in bytes) on the output buffer of replica clients. Once the output buffer exceeds the hard limit, the client is immediately disconnected. | Depends on the instance type and specifications. | Depends on the instance type and specifications. | | client-output-buffer-slave-hard-limit | Hard limit (in bytes) on the output buffer of replica clients. Once the output buffer exceeds the hard limit, the client is immediately disconnected. | Depends on the instance type and specifications. | Depends on the instance type and specifications. |
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
@ -81,32 +81,32 @@ Procedure
| | | | | | | | | |
| | **allkeys-lfu**: Evict keys by trying to remove the LFU keys first. | | | | | **allkeys-lfu**: Evict keys by trying to remove the LFU keys first. | | |
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
| lua-time-limit | Maximum time allowed for executing a Lua script (in milliseconds). | 100–5000 | 5,000 | | lua-time-limit | Maximum time allowed for executing a Lua script (in milliseconds). | 100-5000 | 5,000 |
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
| master-read-only | Sets the instance to be read-only. All write operations will fail. | - yes | no | | master-read-only | Sets the instance to be read-only. All write operations will fail. | - yes | no |
| | | - no | | | | | - no | |
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
| 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. | | 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. |
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
| proto-max-bulk-len | Maximum size of a single element request (in bytes). | 1,048,576–536,870,912 | 536,870,912 | | proto-max-bulk-len | Maximum size of a single element request (in bytes). | 1,048,576-536,870,912 | 536,870,912 |
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
| repl-backlog-size | The replication backlog size (bytes). The backlog is a buffer that accumulates replica data when replicas are disconnected from the master. When a replica reconnects, a partial synchronization is performed to synchronize the data that was missed while replicas were disconnected. | 16,384–1,073,741,824 | 1,048,576 | | repl-backlog-size | The replication backlog size (bytes). The backlog is a buffer that accumulates replica data when replicas are disconnected from the master. When a replica reconnects, a partial synchronization is performed to synchronize the data that was missed while replicas were disconnected. | 16,384-1,073,741,824 | 1,048,576 |
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
| repl-backlog-ttl | The amount of time, in seconds, before the backlog buffer is released, starting from the last a replica was disconnected. The value **0** indicates that the backlog is never released. | 0–604,800 | 3,600 | | repl-backlog-ttl | The amount of time, in seconds, before the backlog buffer is released, starting from the last a replica was disconnected. The value **0** indicates that the backlog is never released. | 0-604,800 | 3,600 |
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
| repl-timeout | Replication timeout (in seconds). | 30–3,600 | 60 | | repl-timeout | Replication timeout (in seconds). | 30-3,600 | 60 |
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
| hash-max-ziplist-entries | Hashes are encoded using a memory efficient data structure when the number of entries in hashes is less than the value of this parameter. | 1–10,000 | 512 | | hash-max-ziplist-entries | Hashes are encoded using a memory efficient data structure when the number of entries in hashes is less than the value of this parameter. | 1-10,000 | 512 |
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
| hash-max-ziplist-value | Hashes are encoded using a memory efficient data structure when the biggest entry in hashes does not exceed the length threshold indicated by this parameter. | 1–10,000 | 64 | | hash-max-ziplist-value | Hashes are encoded using a memory efficient data structure when the biggest entry in hashes does not exceed the length threshold indicated by this parameter. | 1-10,000 | 64 |
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
| set-max-intset-entries | When a set is composed of just strings that happen to be integers in radix 10 in the range of 64 bit signed integers, sets are encoded using a memory efficient data structure. | 1–10,000 | 512 | | set-max-intset-entries | When a set is composed of just strings that happen to be integers in radix 10 in the range of 64 bit signed integers, sets are encoded using a memory efficient data structure. | 1-10,000 | 512 |
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
| zset-max-ziplist-entries | Sorted sets are encoded using a memory efficient data structure when the number of entries in sorted sets is less than the value of this parameter. | 1–10,000 | 128 | | zset-max-ziplist-entries | Sorted sets are encoded using a memory efficient data structure when the number of entries in sorted sets is less than the value of this parameter. | 1-10,000 | 128 |
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
| zset-max-ziplist-value | Sorted sets are encoded using a memory efficient data structure when the biggest entry in sorted sets does not exceed the length threshold indicated by this parameter. | 1–10,000 | 64 | | zset-max-ziplist-value | Sorted sets are encoded using a memory efficient data structure when the biggest entry in sorted sets does not exceed the length threshold indicated by this parameter. | 1-10,000 | 64 |
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
| latency-monitor-threshold | Threshold time in latency monitoring. Unit: millisecond. | 0–86,400,000 ms | 0 | | latency-monitor-threshold | Threshold time in latency monitoring. Unit: millisecond. | 0-86,400,000 ms | 0 |
| | | | | | | | | |
| | Set to **0**: Latency monitoring is disabled. | | | | | Set to **0**: Latency monitoring is disabled. | | |
| | | | | | | | | |
@ -140,11 +140,11 @@ Procedure
| | | | | | | | | |
| | 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. | | | | | 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. | | |
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
| slowlog-log-slower-than | Redis records queries that exceed a specified execution time. | 0–1,000,000 | 10,000 | | slowlog-log-slower-than | Redis records queries that exceed a specified execution time. | 0-1,000,000 | 10,000 |
| | | | | | | | | |
| | **slowlog-log-slower-than** is the maximum time allowed, in microseconds, for command execution. If this threshold is exceeded, Redis will record the query. | | | | | **slowlog-log-slower-than** is the maximum time allowed, in microseconds, for command execution. If this threshold is exceeded, Redis will record the query. | | |
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
| slowlog-max-len | The maximum allowed number of slow queries that can be logged. Slow query log consumes memory, but you can reclaim this memory by running the **SLOWLOG RESET** command. | 0–1000 | 128 | | slowlog-max-len | The maximum allowed number of slow queries that can be logged. Slow query log consumes memory, but you can reclaim this memory by running the **SLOWLOG RESET** command. | 0-1000 | 128 |
+-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+ +-----------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+--------------------------------------------------+
.. note:: .. note::

1
umn/source/operation_guide/managing_dcs_instances/viewing_redis_slow_logs.rst
View File

@ -43,7 +43,6 @@ Viewing Slow Logs on the Console
.. figure:: /_static/images/en-us_image_0281049655.png .. figure:: /_static/images/en-us_image_0281049655.png
:alt: **Figure 1** Slow query log of an instance :alt: **Figure 1** Slow query log of an instance
**Figure 1** Slow query log of an instance **Figure 1** Slow query log of an instance
.. |image1| image:: /_static/images/en-us_image_0000001194523041.png .. |image1| image:: /_static/images/en-us_image_0000001194523041.png

2
umn/source/operation_guide/managing_passwords/changing_instance_passwords.rst
View File

@ -41,7 +41,7 @@ Procedure
- Lowercase letters - Lowercase letters
- Uppercase letters - Uppercase letters
- Digits - Digits
- special characters (:literal:`\`~!@#$^&*()-_=+\|{}:,<.>/?`) - special characters (:literal:`\`~!@#$^&*()-_=+\\|{}:,<.>/?`)
#. In the **Change Password** dialog box, click **OK** to confirm the password change. #. In the **Change Password** dialog box, click **OK** to confirm the password change.

2
umn/source/operation_guide/managing_passwords/dcs_instance_passwords.rst
View File

@ -21,7 +21,7 @@ Passwords can be configured to control access to your DCS instances, ensuring th
- Lowercase letters - Lowercase letters
- Uppercase letters - Uppercase letters
- Digits - Digits
- special characters (:literal:`\`~!@#$^&*()-_=+\|{}:,<.>/?`) - special characters (:literal:`\`~!@#$^&*()-_=+\\|{}:,<.>/?`)
Using Passwords Securely Using Passwords Securely
------------------------ ------------------------

10
umn/source/operation_guide/migrating_data_with_dcs/introduction_to_migration_with_dcs.rst
View File

@ -35,7 +35,7 @@ The following table describes data migration modes supported by DCS.
+------------------------+--------------------------------------------------------------------------------------------------------------------------------+--------------------------------+---------------+---------------+ +------------------------+--------------------------------------------------------------------------------------------------------------------------------+--------------------------------+---------------+---------------+
| | | Single-Node and Master/Standby | Proxy Cluster | Redis Cluster | | | | Single-Node and Master/Standby | Proxy Cluster | Redis Cluster |
+------------------------+--------------------------------------------------------------------------------------------------------------------------------+--------------------------------+---------------+---------------+ +------------------------+--------------------------------------------------------------------------------------------------------------------------------+--------------------------------+---------------+---------------+
| Importing backup files | AOF files in OBS | Y | Y | × | | Importing backup files | AOF files in OBS | Y | Y | x |
| | | | | | | | | | | |
| | .. note:: | | | | | | .. note:: | | | |
| | | | | | | | | | | |
@ -59,11 +59,11 @@ The following table describes data migration modes supported by DCS.
+------------------------+--------------------------------------------------------------------------------------------------------------------------------+--------------------------------+---------------+---------------+ +------------------------+--------------------------------------------------------------------------------------------------------------------------------+--------------------------------+---------------+---------------+
| | Self-hosted Redis: Redis Cluster | Y | Y | Y | | | Self-hosted Redis: Redis Cluster | Y | Y | Y |
+------------------------+--------------------------------------------------------------------------------------------------------------------------------+--------------------------------+---------------+---------------+ +------------------------+--------------------------------------------------------------------------------------------------------------------------------+--------------------------------+---------------+---------------+
| | Other Redis: single-node or master/standby | × | × | × | | | Other Redis: single-node or master/standby | x | x | x |
+------------------------+--------------------------------------------------------------------------------------------------------------------------------+--------------------------------+---------------+---------------+ +------------------------+--------------------------------------------------------------------------------------------------------------------------------+--------------------------------+---------------+---------------+
| | Other Redis: proxy-based cluster | × | × | × | | | Other Redis: proxy-based cluster | x | x | x |
+------------------------+--------------------------------------------------------------------------------------------------------------------------------+--------------------------------+---------------+---------------+ +------------------------+--------------------------------------------------------------------------------------------------------------------------------+--------------------------------+---------------+---------------+
| | Other Redis: Redis Cluster | × | × | × | | | Other Redis: Redis Cluster | x | x | x |
+------------------------+--------------------------------------------------------------------------------------------------------------------------------+--------------------------------+---------------+---------------+ +------------------------+--------------------------------------------------------------------------------------------------------------------------------+--------------------------------+---------------+---------------+
.. note:: .. note::
@ -71,4 +71,4 @@ The following table describes data migration modes supported by DCS.
- **DCS for Redis** refers to Redis instances provided by DCS - **DCS for Redis** refers to Redis instances provided by DCS
- **Self-hosted Redis** refers to self-hosted Redis on the cloud, from other cloud vendors, or in on-premises data centers. - **Self-hosted Redis** refers to self-hosted Redis on the cloud, from other cloud vendors, or in on-premises data centers.
- **Other Redis** refers to Redis services provided by other cloud vendors. - **Other Redis** refers to Redis services provided by other cloud vendors.
- **Y**: Supported. **×**: Not supported. - **Y**: Supported. **x**: Not supported.

2
umn/source/operation_guide/operating_dcs_instances/modifying_dcs_instance_specifications.rst
View File

@ -50,7 +50,7 @@ Scaling
- 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. - 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. - 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. - 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. - 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. - Backup records created before scaling cannot be restored.
Procedure Procedure

1
umn/source/permissions_management/creating_a_user_and_granting_dcs_permissions.rst
View File

@ -28,7 +28,6 @@ Process Flow
.. figure:: /_static/images/en-us_image_0000001196623620.png .. figure:: /_static/images/en-us_image_0000001196623620.png
:alt: **Figure 1** Process of granting DCS permissions :alt: **Figure 1** Process of granting DCS permissions
**Figure 1** Process of granting DCS permissions **Figure 1** Process of granting DCS permissions
#. .. _dcs-ug-210626004__en-us_topic_0170877287_en-us_topic_0170877287_li10176121316284: #. .. _dcs-ug-210626004__en-us_topic_0170877287_en-us_topic_0170877287_li10176121316284:

2
umn/source/service_overview/comparing_redis_versions.rst
View File

@ -18,7 +18,7 @@ When creating a DCS Redis instance, you can select the cache engine version and
+========================================+=======================================================+==================================================================================================================================================================================================+ +========================================+=======================================================+==================================================================================================================================================================================================+
| Instance deployment mode | Based on VMs | Containerized based on physical servers | | Instance deployment mode | Based on VMs | Containerized based on physical servers |
+----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Time required for creating an instance | 3–15 minutes, or 10–30 minutes for cluster instances. | 8 seconds | | Time required for creating an instance | 3-15 minutes, or 10-30 minutes for cluster instances. | 8 seconds |
+----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| QPS | 100,000 QPS per node | 100,000 QPS per node | | QPS | 100,000 QPS per node | 100,000 QPS per node |
+----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +----------------------------------------+-------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

1
umn/source/service_overview/dcs_instance_types/master_standby_redis.rst
View File

@ -54,7 +54,6 @@ Architecture
.. figure:: /_static/images/en-us_image_0296786164.png .. figure:: /_static/images/en-us_image_0296786164.png
:alt: **Figure 1** Master/Standby DCS instance architecture :alt: **Figure 1** Master/Standby DCS instance architecture
**Figure 1** Master/Standby DCS instance architecture **Figure 1** Master/Standby DCS instance architecture
Architecture description: Architecture description:

1
umn/source/service_overview/dcs_instance_types/proxy_cluster_redis.rst
View File

@ -35,7 +35,6 @@ Each Proxy Cluster instance consists of load balancers, proxies, cluster manager
.. figure:: /_static/images/en-us_image_0296786822.png .. figure:: /_static/images/en-us_image_0296786822.png
:alt: **Figure 1** Proxy Cluster DCS Redis instance architecture :alt: **Figure 1** Proxy Cluster DCS Redis instance architecture
**Figure 1** Proxy Cluster DCS Redis instance architecture **Figure 1** Proxy Cluster DCS Redis instance architecture
Architecture description: Architecture description:

2
umn/source/service_overview/dcs_instance_types/redis_cluster.rst
View File

@ -44,7 +44,6 @@ The Redis Cluster instance type provided by DCS is compatible with the `native R
.. figure:: /_static/images/en-us_image_0277578727.png .. figure:: /_static/images/en-us_image_0277578727.png
:alt: **Figure 1** Distributed architecture of Redis Cluster :alt: **Figure 1** Distributed architecture of Redis Cluster
**Figure 1** Distributed architecture of Redis Cluster **Figure 1** Distributed architecture of Redis Cluster
- Presharding - Presharding
@ -55,5 +54,4 @@ The Redis Cluster instance type provided by DCS is compatible with the `native R
.. figure:: /_static/images/en-us_image_0000001280621500.png .. figure:: /_static/images/en-us_image_0000001280621500.png
:alt: **Figure 2** Redis Cluster presharding :alt: **Figure 2** Redis Cluster presharding
**Figure 2** Redis Cluster presharding **Figure 2** Redis Cluster presharding

1
umn/source/service_overview/dcs_instance_types/single-node_redis.rst
View File

@ -42,7 +42,6 @@ Architecture
.. figure:: /_static/images/en-us_image_0296784660.png .. figure:: /_static/images/en-us_image_0296784660.png
:alt: **Figure 1** Single-node DCS Redis instance architecture :alt: **Figure 1** Single-node DCS Redis instance architecture
**Figure 1** Single-node DCS Redis instance architecture **Figure 1** Single-node DCS Redis instance architecture
Architecture description: Architecture description:

5
umn/source/service_overview/ha_and_dr_policies.rst
View File

@ -11,7 +11,6 @@ Whether you use DCS as the frontend cache or backend data store, DCS is always r
.. figure:: /_static/images/en-us_image_0266235346.png .. figure:: /_static/images/en-us_image_0266235346.png
:alt: **Figure 1** DCS DR architecture evolution :alt: **Figure 1** DCS DR architecture evolution
**Figure 1** DCS DR architecture evolution **Figure 1** DCS DR architecture evolution
To meet the reliability requirements of your data and services, you can choose to deploy your DCS instance within a single AZ or across AZs. To meet the reliability requirements of your data and services, you can choose to deploy your DCS instance within a single AZ or across AZs.
@ -27,7 +26,6 @@ Single-AZ deployment means deploying an instance within a physical equipment roo
.. figure:: /_static/images/en-us_image_0266235448.png .. figure:: /_static/images/en-us_image_0266235448.png
:alt: **Figure 2** HA for a single-node DCS instance deployed within an AZ :alt: **Figure 2** HA for a single-node DCS instance deployed within an AZ
**Figure 2** HA for a single-node DCS instance deployed within an AZ **Figure 2** HA for a single-node DCS instance deployed within an AZ
**Master/Standby DCS instance**: Data is persisted to disk in the master node and incrementally synchronized and persisted to the standby node, achieving hot standby and data persistence. **Master/Standby DCS instance**: Data is persisted to disk in the master node and incrementally synchronized and persisted to the standby node, achieving hot standby and data persistence.
@ -36,7 +34,6 @@ Single-AZ deployment means deploying an instance within a physical equipment roo
.. figure:: /_static/images/en-us_image_0266235321.png .. figure:: /_static/images/en-us_image_0266235321.png
:alt: **Figure 3** HA for a master/standby DCS instance deployed within an AZ :alt: **Figure 3** HA for a master/standby DCS instance deployed within an AZ
**Figure 3** HA for a master/standby DCS instance deployed within an AZ **Figure 3** HA for a master/standby DCS instance deployed within an AZ
**Cluster DCS instance**: Similar to a master/standby instance, data in each shard (instance process) of a cluster instance is synchronized between master and standby nodes and persisted on both nodes. **Cluster DCS instance**: Similar to a master/standby instance, data in each shard (instance process) of a cluster instance is synchronized between master and standby nodes and persisted on both nodes.
@ -45,7 +42,6 @@ Single-AZ deployment means deploying an instance within a physical equipment roo
.. figure:: /_static/images/en-us_image_0266235394.png .. figure:: /_static/images/en-us_image_0266235394.png
:alt: **Figure 4** HA for a cluster DCS instance deployed within an AZ :alt: **Figure 4** HA for a cluster DCS instance deployed within an AZ
**Figure 4** HA for a cluster DCS instance deployed within an AZ **Figure 4** HA for a cluster DCS instance deployed within an AZ
Cross-AZ DR Cross-AZ DR
@ -57,7 +53,6 @@ The master and standby nodes of a master/standby or cluster DCS instance can be
.. figure:: /_static/images/en-us_image_0266235441.png .. figure:: /_static/images/en-us_image_0266235441.png
:alt: **Figure 5** Cross-AZ deployment of a master/standby DCS instance :alt: **Figure 5** Cross-AZ deployment of a master/standby DCS instance
**Figure 5** Cross-AZ deployment of a master/standby DCS instance **Figure 5** Cross-AZ deployment of a master/standby DCS instance
.. note:: .. note::

36
umn/source/service_overview/permissions_management.rst
View File

@ -52,41 +52,41 @@ You can grant users permissions by using roles and policies.
+---------------------------------------------+----------------+----------------+--------------------+ +---------------------------------------------+----------------+----------------+--------------------+
| Operation | DCS FullAccess | DCS UserAccess | DCS ReadOnlyAccess | | Operation | DCS FullAccess | DCS UserAccess | DCS ReadOnlyAccess |
+=============================================+================+================+====================+ +=============================================+================+================+====================+
| Modifying instance configuration parameters | Y | Y | × | | Modifying instance configuration parameters | Y | Y | x |
+---------------------------------------------+----------------+----------------+--------------------+ +---------------------------------------------+----------------+----------------+--------------------+
| Deleting background tasks | Y | Y | × | | Deleting background tasks | Y | Y | x |
+---------------------------------------------+----------------+----------------+--------------------+ +---------------------------------------------+----------------+----------------+--------------------+
| Accessing instances using Web CLI | Y | Y | × | | Accessing instances using Web CLI | Y | Y | x |
+---------------------------------------------+----------------+----------------+--------------------+ +---------------------------------------------+----------------+----------------+--------------------+
| Modifying instance running status | Y | Y | × | | Modifying instance running status | Y | Y | x |
+---------------------------------------------+----------------+----------------+--------------------+ +---------------------------------------------+----------------+----------------+--------------------+
| Expanding instance capacity | Y | × | × | | Expanding instance capacity | Y | x | x |
+---------------------------------------------+----------------+----------------+--------------------+ +---------------------------------------------+----------------+----------------+--------------------+
| Changing instance passwords | Y | Y | × | | Changing instance passwords | Y | Y | x |
+---------------------------------------------+----------------+----------------+--------------------+ +---------------------------------------------+----------------+----------------+--------------------+
| Modifying DCS instances | Y | × | × | | Modifying DCS instances | Y | x | x |
+---------------------------------------------+----------------+----------------+--------------------+ +---------------------------------------------+----------------+----------------+--------------------+
| Performing a master/standby switchover | Y | Y | × | | Performing a master/standby switchover | Y | Y | x |
+---------------------------------------------+----------------+----------------+--------------------+ +---------------------------------------------+----------------+----------------+--------------------+
| Backing up instance data | Y | Y | × | | Backing up instance data | Y | Y | x |
+---------------------------------------------+----------------+----------------+--------------------+ +---------------------------------------------+----------------+----------------+--------------------+
| Analyzing big keys or hot keys | Y | Y | × | | Analyzing big keys or hot keys | Y | Y | x |
+---------------------------------------------+----------------+----------------+--------------------+ +---------------------------------------------+----------------+----------------+--------------------+
| Creating DCS instances | Y | × | × | | Creating DCS instances | Y | x | x |
+---------------------------------------------+----------------+----------------+--------------------+ +---------------------------------------------+----------------+----------------+--------------------+
| Deleting instance backup files | Y | Y | × | | Deleting instance backup files | Y | Y | x |
+---------------------------------------------+----------------+----------------+--------------------+ +---------------------------------------------+----------------+----------------+--------------------+
| Upgrading instance version | Y | Y | × | | Upgrading instance version | Y | Y | x |
+---------------------------------------------+----------------+----------------+--------------------+ +---------------------------------------------+----------------+----------------+--------------------+
| Restoring instance data | Y | Y | × | | Restoring instance data | Y | Y | x |
+---------------------------------------------+----------------+----------------+--------------------+ +---------------------------------------------+----------------+----------------+--------------------+
| Resetting instance passwords | Y | Y | × | | Resetting instance passwords | Y | Y | x |
+---------------------------------------------+----------------+----------------+--------------------+ +---------------------------------------------+----------------+----------------+--------------------+
| Migrating instance data | Y | Y | × | | Migrating instance data | Y | Y | x |
+---------------------------------------------+----------------+----------------+--------------------+ +---------------------------------------------+----------------+----------------+--------------------+
| Downloading instance backup data | Y | Y | × | | Downloading instance backup data | Y | Y | x |
+---------------------------------------------+----------------+----------------+--------------------+ +---------------------------------------------+----------------+----------------+--------------------+
| Deleting DCS instances | Y | × | × | | Deleting DCS instances | Y | x | x |
+---------------------------------------------+----------------+----------------+--------------------+ +---------------------------------------------+----------------+----------------+--------------------+
| Querying instance configuration parameters | Y | Y | Y | | Querying instance configuration parameters | Y | Y | Y |
+---------------------------------------------+----------------+----------------+--------------------+ +---------------------------------------------+----------------+----------------+--------------------+

1
umn/source/service_overview/related_services.rst
View File

@ -11,7 +11,6 @@ DCS is used together with other services, including VPC, ECS, IAM, Cloud Eye, CT
.. figure:: /_static/images/en-us_image_0277837533.png .. figure:: /_static/images/en-us_image_0277837533.png
:alt: **Figure 1** Relationships between DCS and other services :alt: **Figure 1** Relationships between DCS and other services
**Figure 1** Relationships between DCS and other services **Figure 1** Relationships between DCS and other services
VPC VPC