检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
DCS Best Practices This section summarizes best practices of Distributed Cache Service (DCS) in common scenarios. Each practice is given a description and procedure. Table 1 DCS best practices Best Practice Description Serializing Access to Frequently Accessed Resources Describes
Diagnosing DCS Faults Scenarios By collecting and analyzing metrics such as flow control, memory usage, and command duration statistics, you can quickly learn about the overall usage of DCS and acquire troubleshooting methods. Precautions DCS diagnosis can be performed for Redis instances
DCS Instance Types Single-Node Redis Master/Standby Redis Proxy Cluster Redis Redis Cluster Read/Write Splitting Redis Comparing DCS Redis Instance Types Single-Node Memcached (Discontinued) Master/Standby Memcached (Discontinued)
DCS Instance Specifications Redis 4.0/5.0/6.0/7.0 Redis 6.0 Enterprise Edition Redis 3.0 Instance Specifications (Discontinued) Memcached Instance Specifications (Discontinued)
What Is DCS? Huawei Cloud Distributed Cache Service (DCS) is an online, distributed, fast in-memory cache service compatible with Redis. It is reliable, scalable, usable out of the box, and easy to manage, meeting your requirements for high read/write performance and fast data access
Selecting DCS Products Select a DCS Redis instance based on your service scenarios, performance requirements, and budget. This document provides references for selecting product editions, instance types, and instance specifications. Selecting a Product Edition Table 1 Product editions
Restarting a DCS Instance To recover an instance in cases such as high memory fragmentation ratio or fault occurrence, try restarting the instance on the DCS console. DCS instances can be restarted in batches. Notes and Constraints The DCS instances must be in the Running or Faulty
Process of Using DCS How to Manage DCS Instances You can access Distributed Cache Service (DCS) from the web-based management console or by using RESTful application programming interfaces (APIs) through HTTPS requests. Using the console You can sign up and log in to the console,
Viewing DCS Metrics The Cloud Eye service monitors the running performance your DCS instances. Procedure Log in to the DCS console. Click in the upper left corner of the console and select the region where your instance is located. In the navigation pane, choose Cache Manager. Click
Monitored DCS Events Introduction Event monitoring provides event collection, query, and alarm reporting. These major events or DCS operation events can be collected to Cloud Eye to alarm. Namespace SYS.DCS Monitored events Table 1 DCS events Event Name Event ID Event Severity Description
Restoring DCS Instances This section describes how to restore instances on the DCS console. This function helps restore instances deleted by mistake. To migrate backup data to other DCS instances, see Backup Import Between DCS Redis Instances. Notes and Constraints You can enable
Common DCS Metrics This section describes common Redis metrics. Table 1 Common metrics Metric Description CPU Usage This metric indicates the maximum value in each measurement period (minute-level: every minute; second-level: every 5 seconds). For a single-node or master/standby instance
Deleting a DCS Instance On the DCS console, you can delete one or multiple DCS instances at a time. You can also delete all instance creation tasks that have failed to run. Notes and Constraints The DCS instances exist, and must be in the Running, Faulty, or Stopped state. Deleting
DCS Dashboard Template DCS is an in-memory database service. It is compatible with Redis, an in-memory database engine, and meets your requirements for high concurrency and fast data access. LTS collects, stores, and queries cloud resource operation records. You can use these records
v1.27.16-r10 or later v1.28: v1.28.15-r0 or later v1.29: v1.29.10-r0 or later v1.30: v1.30.6-r0 or later Other clusters of later versions Forward to a custom backend server group Forward LoadBalancer ingress requests to both pods in the CCE cluster (default backend server group) and an ECS
Using Commands to Generate TPC-DS Test Sets The SQL statements of the 99 TPC-DS SQL standard queries can be generated as follows: Preparations Modify the following files in the query_templates directory before generating TPC-DS query statements: Log in to the ECS and go to the /data1
Using Commands to Generate TPC-DS Test Sets The SQL statements of the 99 TPC-DS SQL standard queries can be generated as follows: Preparations Modify the following files in the query_templates directory before generating TPC-DS query statements: Log in to the ECS and go to the /data1
Inserting Data to a DCS Table Function This statement is used to insert data in a DLI table to the DCS key. Syntax Insert the SELECT query result into a table. 1 2 3 4 5 6 7 INSERT INTO DLI_TABLE SELECT field1,field2... [FROM DLI_TEST] [WHERE where_condition] [LIMIT num]
Querying BCS Alarm Statistics Function This API is used to query the alarm statistics of a specified metric of a BCS service. URI POST /v2/{project_id}/blockchains/{blockchain_id}/events/statistic Table 1 Path Parameters Parameter Mandatory Type Description project_id Yes String Project
Querying BCS Monitoring Data Function This API is used to query the monitoring data of a specified metric of a BCS service. URI POST /v2/{project_id}/blockchains/{blockchain_id}/metric/list Table 1 Path Parameters Parameter Mandatory Type Description project_id Yes String Project