Constraints
The following tables list the constraints designed to ensure stability and security of GeminiDB Cassandra instances.
Specifications
Resource Type |
Specifications |
Description |
---|---|---|
CPU and memory |
GeminiDB Cassandra cluster instances are supported. |
|
Storage Space |
The storage space depends on the selected instance specifications. |
Storage capacity can be scaled up or down. For details, see Overview. |
Quotas
Resource Type |
Constraint |
Description |
---|---|---|
Tag |
A maximum of 20 tags can be added for each instance. |
For more information, see Managing GeminiDB Cassandra Instance Tags. |
Free backup space |
GeminiDB Cassandra instances provide free backup storage. |
For more information, see Backup Storage. |
Retention period |
The default value is 7 days. The value ranges from 1 to 3660 days. |
For more information, see Automated Backup Policy. |
Naming Rules
Item |
Description |
---|---|
Instance name |
|
Backup name |
|
Parameter template name |
|
Security
Item |
Description |
---|---|
Password of database administrator rwuser |
|
Database port |
Database port number. When creating a GeminiDB Cassandra instance, you cannot specify a port number. The default port number is 8635. The port number can be changed after the instance is created. The database port ranges from 2100 to 9500 except 2180, 2181, 2887, 3887, 7000, 7001, 7199, 8000, 8018, 8079, 8091, 8092, 8479, 8484, 8636, and 8999. |
VPC |
After a GeminiDB Cassandra instance is created, the VPC where the instance is deployed cannot be changed. |
Intranet security group |
A security group controls access between GeminiDB Cassandra API and other services. Ensure that the security group you selected allows your client to access the instance. If no security group is available, the system creates one for you. |
Instance Operations
Function |
Constraint |
---|---|
Database access |
|
Instance deployment |
The servers where instances are deployed are not directly visible to you. You can only access the instances through IP addresses and database ports. |
Restarting a GeminiDB Cassandra instance |
|
Viewing GeminiDB Cassandra instance backups |
GeminiDB Cassandra instance backups are stored in OBS buckets and are invisible to you. |
Changing the CPU or memory of a GeminiDB Cassandra instance |
|
Data restoration |
To prevent data loss, you are advised to back up key data before data restoration. |
Storage |
If the storage space of an instance is full, data cannot be written to databases. You are advised to periodically check the storage space. GeminiDB Cassandra instance storage can be automatically scaled up in case of a sudden surge in data volumes. Enable autoscaling by following Automatically Scaling Up Storage Space. |
Recycle bin |
|
For details about other development and O&M specifications that can effectively evaluate and improve service system stability, see Database Rules.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot