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-11-11 13:33:02 +00:00
parent a801aab463
commit 50aa5b1b1c
8 changed files with 162 additions and 162 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
umn/source/getting_started/accessing_an_instance/access_in_different_languages/java/redisson.rst
View File

@ -133,7 +133,7 @@ Procedure
// singleServerConfig.setPassword("********"); // singleServerConfig.setPassword("********");
RedissonClient redisson = Redisson.create(config); RedissonClient redisson = Redisson.create(config);
//Test concurrentMap. Data is synchronized to Redis when the put method is used. //Test concurrentMap. Data is synchronized to Redis when the put method is used.
ConcurrentMap map = redisson.getMap("FirstMap"); ConcurrentMap<String, Object> map = redisson.getMap("FirstMap");
map.put("wanger", "male"); map.put("wanger", "male");
map.put("zhangsan", "nan"); map.put("zhangsan", "nan");
map.put("lisi", "female"); map.put("lisi", "female");
@ -205,7 +205,7 @@ Procedure
//Set a password. //Set a password.
// clusterServersConfig.setPassword("********"); // clusterServersConfig.setPassword("********");
RedissonClient redisson = Redisson.create(config); RedissonClient redisson = Redisson.create(config);
ConcurrentMap map = redisson.getMap("FirstMap"); ConcurrentMap<String, Object> map = redisson.getMap("FirstMap");
map.put("wanger", "male"); map.put("wanger", "male");
map.put("zhangsan", "nan"); map.put("zhangsan", "nan");
map.put("lisi", "female"); map.put("lisi", "female");

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

@ -33,7 +33,7 @@ Alarm Policies for DCS Redis Instances
| | | | | | | | | | | |
| | | 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 | | |
| | | | | | | | | | | |

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

@ -75,7 +75,7 @@ DCS Redis 3.0 Instance Metrics
| | | | | | | | | | | | | |
| | | | | dcs_instance_id | | | | | | | dcs_instance_id | |
+----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+
| node_status | Instance Node Status | Status of instance nodes. If the status is normal, the value is **0**. If the status is abnormal, the value is **1**. | - | Monitored object: | 1 minute | | node_status | Instance Node Status | Status of instance nodes. If the status is normal, the value is **0**. If the status is abnormal, the value is **1**. | ``-`` | Monitored object: | 1 minute |
| | | | | | | | | | | | | |
| | | | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | Single-node, master/standby, or cluster DCS Redis instance | |
| | | | | | | | | | | | | |
@ -456,7 +456,7 @@ DCS Redis 4.0 and 5.0 Instance Metrics
| | | | | | | | | | | | | |
| | | | | dcs_instance_id | | | | | | | dcs_instance_id | |
+----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+ +----------------------------+----------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------+------------------------------------------------------------+------------------------------+
| Instance Node Status | Instance Node Status | Status of instance nodes. If the status is normal, the value is **0**. If the status is abnormal, the value is **1**. | - | Monitored object: | 1 minute | | Instance Node Status | Instance Node Status | Status of instance nodes. If the status is normal, the value is **0**. If the status is abnormal, the value is **1**. | ``-`` | Monitored object: | 1 minute |
| | | | | | | | | | | | | |
| | | | | Single-node, master/standby, or cluster DCS Redis instance | | | | | | | Single-node, master/standby, or cluster DCS Redis instance | |
| | | | | | | | | | | | | |
@ -1025,7 +1025,7 @@ Node Metrics of DCS Redis Instances
| | | | | | | | | | | | | |
| | | | | dcs_cluster_redis_node | | | | | | | dcs_cluster_redis_node | |
+----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+ +----------------------------+----------------------------+--------------------------------------------------------------------------------------------------------------------------------+---------------+---------------------------------------------------------------+------------------------------+
| ms_repl_offset | Replication Gap | Data synchronization gap between the master and the replica | - | Monitored object: | 1 minute | | ms_repl_offset | Replication Gap | Data synchronization gap between the master and the replica | ``-`` | Monitored object: | 1 minute |
| | | | | | | | | | | | | |
| | | | | Replica of a cluster DCS Redis 4.0 or 5.0 instance | | | | | | | Replica of a cluster DCS Redis 4.0 or 5.0 instance | |
| | | | | | | | | | | | | |

64
umn/source/service_overview/command_compatibility/redis_3.0_commands.rst
View File

File diff suppressed because it is too large Load Diff

64
umn/source/service_overview/command_compatibility/redis_4.0_commands.rst
View File

File diff suppressed because it is too large Load Diff

78
umn/source/service_overview/command_compatibility/redis_5.0_commands.rst
View File

File diff suppressed because it is too large Load Diff

102
umn/source/service_overview/command_compatibility/web_cli_commands.rst
View File

File diff suppressed because it is too large Load Diff

4
umn/source/service_overview/comparing_dcs_and_open-source_cache_services.rst
View File

@ -20,12 +20,12 @@ DCS for Redis vs. Open-Source Redis
| Service deployment | Requires 0.5 to 2 days to prepare servers. | - Creates a Redis 3.0 instance in 5 to 15 minutes. | | Service deployment | Requires 0.5 to 2 days to prepare servers. | - Creates a Redis 3.0 instance in 5 to 15 minutes. |
| | | - Creates a containerized Redis 4.0 or 5.0 instance within 8 seconds. | | | | - Creates a containerized Redis 4.0 or 5.0 instance within 8 seconds. |
+------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Version | - | Deeply engaged in the open-source community and supports the latest Redis version. Currently, Redis 3.0, 4.0, and 5.0 are supported. | | Version | ``-`` | Deeply engaged in the open-source community and supports the latest Redis version. Currently, Redis 3.0, 4.0, and 5.0 are supported. |
+------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Security | Network and server safety is the user's responsibility. | - Network security is ensured using VPCs and security groups. | | Security | Network and server safety is the user's responsibility. | - Network security is ensured using VPCs and security groups. |
| | | - Data reliability is ensured by data replication and scheduled backup. | | | | - Data reliability is ensured by data replication and scheduled backup. |
+------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Performance | - | 100,000 QPS per node | | Performance | ``-`` | 100,000 QPS per node |
+------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ +------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Monitoring | Provides only basic statistics. | Provides more than 30 monitoring metrics and customizable alarm threshold and policies. | | Monitoring | Provides only basic statistics. | Provides more than 30 monitoring metrics and customizable alarm threshold and policies. |
| | | | | | | |