检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
If password-free access is required, delete the line that contains "password". To access the instance using an ACL user, configure the instance password {password} in the {username:password} format. For details, see Configuring DCS Redis ACL Users.
Data Deletion If you delete a DCS instance, all data stored in the instance will be deleted. Nobody can view or restore the data once it is deleted. Parent topic: Security
URI DELETE /v2/{project_id}/instances/{instance_id}/public-ip Table 1 Path Parameters Parameter Mandatory Type Description project_id Yes String Project ID. For details, see Obtaining a Project ID. instance_id Yes String Instance ID.
Table 4 Error codes returned in case of a backup or restoration failure Error Code Description dcs.08.0001 Failed to start the backup and restore tool. dcs.08.0002 Operation timed out. dcs.08.0003 Failed to delete bucket. dcs.08.0004 Failed to obtain AK/SK. dcs.08.0005 Failed to create
To delete custom templates, click Delete in the Operation column on the right of the templates to be deleted. Click Yes. Parent Topic: Configuring DCS Instance Parameter Templates
Billing starts from the Run time on the DCS instance's Basic Information page For example, if you purchase a pay-per-use DCS instance at 8:45:30, and delete it at 8:55:00, the billing period is from 8:00:00 to 9:00:00.
You can delete the test data after data import. If there is any DB not used by your service systems, you can write test data into the DB, and run the flushdb command to clear the database after importing data into DCS.
If it is not required, delete this parameter. accept: specifies the user-defined listening port number of Stunnel. Specify this parameter when accessing an instance on a Redis client. connect: specifies the service address and port of Stunnel.
You can call APIs to create, delete, and modify instances. Available in all regions API Overview
Check whether the request parameters are valid. 400 DCS.4935 Only one slave replication has dns ip, can not delete The replica cannot be deleted because at least one DNS IP address must be retained.
trying to remove the LRU keys first. volatile-random: Evict keys randomly, but only among keys that have an expire set. allkeys-random: Evict keys randomly. volatile-ttl: Evict keys with an expire set, and try to evict keys with a shorter time to live (TTL) first. noeviction: Do not delete
You can stop, delete, or restart them in batches. Verifying the Migration Before data migration, if the target Redis has no data, check data integrity after the migration is complete in the following way: Connect to the source Redis and the target Redis.
You can stop, delete, or restart them in batches. Verifying the Migration Before data migration, if the target Redis has no data, check data integrity after the migration is complete in the following way: Connect to the source Redis and the target Redis.
If the number of replicas is already the minimum supported by the instance, you can no longer delete replicas. Parent topic: Instance Scaling and Upgrade
created_at String Time when the restoration task was created. progress String Restoration progress. error_code String Error code displayed for a restoration failure. dcs.08.0001 - Failed to start the backup and restoration tool. dcs.08.0002 - Execution timed out. dcs.08.0003 - Failed to delete
This parameter is mandatory when you delete replicas from a cluster instance. For details, see Querying AZs. node_list No Array of strings ID of the replica to delete.
updated_at String Time at which DCS instance backup is completed. progress String Backup progress. error_code String Error code displayed for a backup failure. dcs.08.0001 - Failed to start the backup and restoration tool. dcs.08.0002 - Execution timed out. dcs.08.0003 - Failed to delete
You can stop, delete, or restart them in batches. Verifying the Migration After the migration is complete, check data integrity in the following way. Connect the source Redis and the target Redis. For details, see redis-cli.
In this case, delete the key. If the error information contains "not in the same slot", reconstruct your service. Do not use cross-slot keys in a multi-key command. You can also use a master/standby instance instead of a Proxy Cluster instance as the target.
trying to remove the LRU keys first. volatile-random: Evict keys randomly, but only among keys that have an expire set. allkeys-random: Evict keys randomly. volatile-ttl: Evict keys with an expire set, and try to evict keys with a shorter time to live (TTL) first. noeviction: Do not delete
