检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
An Elastic Cloud Server (ECS) has been created. For details about how to create an ECS, see Purchasing an ECS in Custom Config Mode. The source self-hosted Redis instance must support the SYNC command. Otherwise, the RDB file cannot be exported using redis-cli.
Connections (Default/Limit) Bandwidth Limit (MB/s) Bandwidth Limit per Redis Server (MB/s) Reference Performance (QPS) Reference Performance per Node (QPS) Specification Code (spec_code in the API) 1 1 2 20,000 96 48 200,000 100,000 redis.ha.xu1.large.p2.1 1 1 3 30,000 144 48 300,000
Single-node instances only have one master node, and can be vulnerable of data reliability and service level agreement (SLA) when a physical server is faulty. Exercise caution. You are not advised to use them in production environments.
Connecting to Redis on ioredis For a client server running Ubuntu (Debian series), see Client Server Running Ubuntu (Debian Series). For a client server running CentOS (Red Hat series), see Client Server Running CentOS (Red Hat Series).
There is no Service Level Agreement (SLA) assurance. Master/Standby Two replicas (one master node and one standby node). Data persistence is available. Node faults can be rectified through master/standby switchovers, ensuring access.
Figure 3 HA among master and standby nodes within an AZ Cross-AZ DR Within a Region The master and standby nodes of a DCS instance (single-node type not included) can be deployed across AZs (in different equipment rooms).
The following formulas are for reference: Minimum number of connections = (QPS of a single node accessing Redis)/(1000 ms/Average time spent on a single command) Maximum number of connections = (QPS of a single node accessing Redis)/(1000 ms/Average time spent on a single command)
Application The client of the instance, which is the application running on an Elastic Cloud Server (ECS). DCS Memcached instances are compatible with the Memcached protocol, and can be accessed through open-source clients.
Request Parameters None Response Parameters Status code: 200 Table 2 Response body parameters Parameter Type Description job_id String ID of the cluster shard master/replica role switch task.
= 200; @Value("${redis.retry.attempts:3}") private Integer redisRetryAttempts = 3; @Value("${redis.retry.interval:200}") private Integer redisRetryInterval = 200; @Bean public RedissonClient redissonClient() { Config redissonConfig = new Config(
50}") private Integer redisPoolMinSize = 50; @Value("${redis.pool.maxSize:200}") private Integer redisPoolMaxSize = 200; @Value("${redis.pool.maxWaitMillis:2000}") private Integer redisPoolMaxWaitMillis = 2000; @Value("${redis.pool.softMinEvictableIdleTimeMillis
Changing Cluster DCS Instances to be Across AZs To implement disaster recovery, cluster instances (whose master and standby nodes are) in a single AZ can be deployed across AZs by migrating the standby nodes to other AZs.
(The new backup is used only once in this analysis, and is not recorded in Backing Up or Restoring Instance Data). Archived: Select a backup file in RDB format from the historical backup records. Analyzing a master node using a new backup may deteriorate instance performance.
Value range: N/A. node_role String Parameter description: Node role. Value range: redis-server: Redis server node redis-proxy: proxy node node_type String Parameter description: Node master/standby role.
Master/standby: Each master/standby instance runs on two nodes (one master and one standby). The standby node replicates data synchronously from the master node. If the master node fails, the standby node automatically becomes the master node.
Response Parameters Status code: 200 Table 3 Response body parameters Parameter Type Description job_id String ID of the instance node start or stop task.
Asynchronous Master/Replica Node Switchover Function This API is used to asynchronously switch master or replica nodes. Calling Method For details, see Calling APIs.
Response Parameters Status code: 200 Table 3 Response body parameters Parameter Type Description job_id String ID of the task for killing a specified node or instance.
status={status} Example Responses Status code: 200 Node information queried successfully. { "instance_id" : "11368fbb-de1e-4613-9080-1c374b71a1af", "total" : 1, "nodes" : [ { "logical_node_id" : "79653bcbd0e5c104fefedd188aa372d6", "name" : "(master)192.168.68.157",
When the master node is faulty, a replica with a smaller weight has a higher priority to be promoted to master. Calling Method For details, see Calling APIs.
