ApsaraDB for Redis provides Community Edition and Enhanced Edition (Tair). ApsaraDB for Redis Enhanced Edition (Tair) allows you to create performance-enhanced instances. This topic describes how to create an ApsaraDB for Redis instance to meet your business requirements.
- An Alibaba Cloud account is created. For more information, see Create your Alibaba Cloud account.
- To create a pay-as-you-go instance, you must keep sufficient balance in your account.
For more information, see Billable items and prices.
- Log on to the ApsaraDB for Redis console.
- In the upper-right corner of the page, click Create Instance.
- On the buy page, select a billing method for the new instance.
Note You can switch the billing method from pay-as-you-go to subscription, but cannot switch it from subscription to pay-as-you-go.
- Subscription: You must pay for an instance when you create it. We recommend that you select this billing method for long-term use because it is more cost-effective than the pay-as-you-go billing method. Higher discounts are offered for longer subscription periods.
- Pay-as-you-go: You must pay for the instance on an hourly basis based on your actual usage. We recommend that you select this billing method for short-term subscriptions. You can release your pay-as-you-go instance to reduce costs when it is no longer used.
- Configure the instance parameters. The following table describes these parameters.
Section Parameter Description Basic configuration Region and Zone The region where you want to create your ApsaraDB for Redis instance. You cannot change the region after you purchase the instance.
- To maximize access speed, we recommend that you select a region that is close to the geographic location of your users.
- To enable connections over the internal network, make sure that the ApsaraDB for Redis instance is deployed in the same region as Elastic Compute Service (ECS) instances that need to access the ApsaraDB for Redis instance. Otherwise, the ECS instances can access the ApsaraDB for Redis instance only over the Internet. Connections over the Internet may degrade the service performance.
Zone Select a zone within the specified region. Each region has multiple isolated locations that are known as zones. Each zone has its own independent power supply and network. To minimize the network latency between an ECS instance and an ApsaraDB for Redis instance that are deployed in the same zone, connect them over an internal network.Note To implement zone-disaster recovery, you can deploy the ApsaraDB for Redis instance across multiple zones. Network Type
- VPC: A virtual private cloud (VPC) is an isolated network that provides higher security and better performance than the classic network. We recommend that you select a VPC.
- Classic Network: Cloud services in the classic network are not isolated. Access control to cloud services in the classic network is implemented by the security groups or whitelist policies of the services.
- To enable connections over the internal network, make sure that the ApsaraDB for Redis instance is connected to the same type of network as the ECS instances or ApsaraDB RDS instances that need to access the ApsaraDB for Redis instance.
- If you select the VPC network type, make sure that the ApsaraDB for Redis instance is connected to the same VPC as the ECS instances or ApsaraDB RDS instances that need to access the ApsaraDB for Redis instance.
- You can change the network type of ApsaraDB for Redis instances from Classic Network to VPC. However, you cannot change the network type from VPC to Classic Network.
VPC Select a VPC in which you want to create the ApsaraDB for Redis instance. For more information about VPCs, see Create a VPC. VSwitch Select a vSwitch in the VPC. If no vSwitches are created in the VPC in the current zone, create a vSwitch as needed. For more information, see Create a vSwitch. Instance Edition
- Community Edition: This edition is compatible with the open source Redis protocol and provides high performance.
- Enhanced Edition (Tair): This edition is developed based on ApsaraDB for Redis Community Edition. ApsaraDB for Redis Enhanced Edition (Tair) is optimized in terms of performance, storage, and data schemas. For more information, see Overview.
Series Enhanced Performance: uses a multi-threading model. This parameter is available only if the Edition parameter is set to Enhanced Edition (Tair). The performance of this series is three times that of a Community Edition instance of the same specifications. This series also provides multiple data schema modules to simplify development. For more information, see Performance-enhanced instances.Note Hybrid storage instances are discontinued. For more information, see ApsaraDB for Redis hybrid-storage instances are discontinued. Version The engine version of the ApsaraDB for Redis instance.Note The instances that run Redis 2.8 will soon be phased out. We recommend that you create an instance that uses the latest engine version for more features and more stable performance. Architecture Type
- Cluster: eliminates the performance bottleneck that is caused by a single-threading model. You can use the high-performance cluster instance to process large-capacity workloads.
- Standard: runs in a master-replica architecture, provides high-performance caching services, and ensures high data reliability.
- Read/Write Splitting: ensures high availability and high performance, and supports multiple specifications. The read/write splitting architecture allows a large number of concurrent requests to read hot data from read replicas. This reduces the loads on the master node and minimizes the O&M cost.
Shards Specifies the number of data shards for the cluster instance. Data is distributed across the data shards in the cluster instance.Note This parameter is supported only when you set the Architecture Type parameter to Cluster. Node Type
- If you set the Architecture Type parameter to Cluster or Standard, you must set the Node Type parameter to Master-Replica. This creates a dual-node hot-standby architecture that provides data persistence with high data reliability and availability.
- If you set the Architecture Type parameter to Read-Write Splitting, you can choose the node type based on the number of read replicas.
Instance Class Each instance type contains a group of configurations, such as the memory capacity, maximum number of concurrent connections, and maximum bandwidth. For more information, see Overview.Note The database metadata is generated after you create an ApsaraDB for Redis instance. The size of the metadata on each data shard of cluster instances is 30 MB to 50 MB. The total size of the metadata for a cluster equals the sum of metadata on all data shards of the cluster. Password Setting
- Later: Set a password after the instance is created. For more information, see Change or reset the password.
- Now: Enter a password for the instance.
- The password must be 8 to 32 characters in length.
- The password must contain at least three of the following types of characters: uppercase letters, lowercase letters, digits, and special characters.
- The following special characters are supported:
! @ # $ % ^ & * ( ) _ + - =.
Purchase plan Instance Name Enter a name for the instance to identify and manage the instance. Quantity Specify the number of instances that you want to create. The instances have the same specifications. You can create up to 99 instances. Subscription Duration If you select the subscription billing method, you must specify the duration and select whether to enable auto-renewal.
- Click Buy Now.
- On the Confirm Order page, read and accept ApsaraDB for Redis Agreement of Service and follow the instructions
to pay for the instance. After the payment is complete, wait for one to five minutes. Then, you can find the new ApsaraDB for Redis instance in the ApsaraDB for Redis console.
- Q: How long does it take for the system to create an instance?
A: The time it takes to create an instance depends on the number of data shards on the instance. A larger number of data shards require more resources. As a result, it takes more time to allocate resources. For example, it takes two to three minutes to create a standard master-replica instance, 10 to 15 minutes to create a 128-shard cluster master-replica instance, and 20 to 40 minutes to create a 256-shard cluster master-replica instance.Note
- For standard instances, the amount of time depends on single-shard instances.
- The master node of a read/write splitting instance processes read and write requests. Each master node is regarded as a data shard. Each read replica is regarded as a data shard.
- Q: Why am I unable to find the created instance?
A: The following table describes the possible causes and solutions.
Possible cause Solution The region that you selected in the console is not the region where the instance is deployed. Log on to the ApsaraDB for Redis console and select the region where the instance is deployed. The instance list in the ApsaraDB for Redis console is not updated or is updated before the instance is created. Wait for several minutes and then update the instance list to check whether the instance appears in the list. Resources are insufficient. The system may fail to create the instance due to insufficient resources. In this case, your payment is refunded. You can check your refund on the Orders page.
After you confirm that the payment is refunded, you can try to create your instance in another zone. You can also submit a ticket.
- Q: Why did I fail to create a standalone instance of ApsaraDB for Redis?
A: Starting December 19, 2019, standalone instances of ApsaraDB for Redis were phased out. For more information, see Deprecated standalone instances.
Related API operations
|CreateInstance||Creates an ApsaraDB for Redis instance.|