This section describes how to create a DB instance that is compatible with Cassandra APIs.
Parameter |
Description |
---|---|
Region |
The region where the tenant is located. NOTICE:
Select the region nearest where you will be accessing the DB from so latency can be kept to a minimum and response time will be faster. Also, products deployed in different regions cannot communicate with each other through a private network and you cannot change the region of an instance after creating the instance. |
DB Instance Name |
The new name can be the same as an existing instance name. It must start with a letter and consist of 4 to 64 characters. Only letters (case-sensitive), digits, hyphens (-), and underscores (_) are allowed. After the DB instance is created, you can change the DB instance name. For details, see section Changing a DB Instance Name. |
Compatible API |
Cassandra |
DB Instance Type |
Cluster |
DB Engine Version |
3.11 |
AZ |
An AZ is a part of a region with its own independent power supplies and networks. AZs are physically isolated but can communicate through an internal network connection. |
Parameter |
Description |
---|---|
Instance Specifications |
The CPU and memory of a DB instance. Different performance specifications support different numbers of connections and maximum IOPSs. Select CPU and memory specifications based on your service requirements. After a DB instance is created, you can change its CPU and memory. For details, see Changing a DB Instance Class. |
Nodes |
The number of nodes ranges from 3 to 200. Select the number of nodes based on the site requirements. After a DB instance is created, you can add nodes. For details, see Adding Nodes. |
Storage Space |
Storage space depends on the instance specifications. The minimum storage space is 100 GB, and the storage space you set must be an integer. You can select a minimum of 1 GB each time you scale up storage space. After a DB instance is created, you can scale up its storage space. For details, see Scaling Up Storage Space. |
Parameter |
Description |
---|---|
VPC |
The virtual network where your DB instances are located. A VPC isolates networks for different services. You can select an existing VPC or create a VPC. If there are no VPCs available, the system allocates resources to you by default. For details on how to create a subnet, see the "Creating a VPC" section in the Virtual Private Cloud User Guide. NOTE:
After the GaussDB(for Cassandra) instance is created, the VPC where the instance resides cannot be changed. |
Subnet |
A subnet provides dedicated network resources that are logically isolated from other networks for network security. |
Security Group |
A security group controls access between GaussDB NoSQL instances and other services. When you select a security group, you must ensure that it allows the client to access DB instances. If there are no security groups available, the system allocates resources to you by default. |
Parameter |
Description |
---|---|
Administrator |
The default administrator account is rwuser. |
Administrator Password |
Set a password for the administrator. The password:
Keep this password secure. If you lose it, the system cannot retrieve it. |
Confirm Password |
Enter the administrator password again. |
Parameter Template |
A parameter template contains engine configuration values that can be applied to one or more instances. After a DB instance is created, you can modify parameters to better meet your service requirements. For details, see Modifying a Parameter Template. |
Parameter |
Description |
---|---|
Tags |
The setting is optional. Adding tags helps you better identify and manage your DB instances. Each DB instance can have up to 20 tags. A tag is composed of a key-value pair.
After a DB instance is created, you can view its tag details on the Tags tab. In addition, you can add, modify, and delete tags for existing DB instances. For details, see Managing Tags. |
You can click in the upper right corner of the page to refresh the DB instance statuses.