Constraints

CPU and memory

GeminiDB Influx API supports cluster (performance-enhanced), cluster, and single-node instances.

• For details about specifications of different instance types, see Instance Specifications.
• You can change the specifications to meet your service requirements by following Changing vCPUs and Memory.

Storage

The storage space depends on the selected instance specifications.

Disk capacity of GeminiDB Influx instances can be scaled up. For details, see Manually Scaling Up Storage Space of a GeminiDB Influx Instance.

Tag

A maximum of 20 tags can be added for each instance.

For more information, see Managing Tags.

Free backup space

GeminiDB Influx 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 Configuring an Automated Backup Policy.

Instance name

• Can contain 4 to 64 characters.
• Must start with a letter. Only letters (case-sensitive), digits, hyphens (-), and underscores (_) are allowed.

Backup name

• Can contain 4 to 64 characters.
• Must start with a letter. Only letters (case sensitive), digits, hyphens (-), and underscores (_) are allowed.

Parameter template name

• Can contain 1 to 64 characters.
• Only letters (case sensitive), digits, hyphens (-), underscores (_), and periods (.) are allowed.

Password of database administrator rwuser

• Can contain 8 to 32 characters.
• Can contain at least two types of the following characters: uppercase letters, lowercase letters, digits, and special characters ~!@#%^*-_=+? For more information, see Changing the Administrator Password of a GeminiDB Influx Database.
• Keep your password secure. The system cannot retrieve it if it is lost.

Database port

Port for accessing a database. The default value is 8635 and cannot be changed.

VPC

After a GeminiDB Influx instance is created, the VPC where the instance is deployed cannot be changed.

Security group

A security group controls access between GeminiDB Influx 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.

Access control

A load balancer address does not support security groups. After an instance is created, configure IP address access control. If no whitelist is configured, all IP addresses that can communicate with the VPC can access the instance.

Database access

• If remote access is not enabled, GeminiDB Influx instances and their associated ECSs must be in the same VPC subnet.

• The security group must allow access from the associated ECS.

  By default, a GeminiDB Influx instance cannot be accessed through an ECS in a different security group. You need to add an inbound rule to the security group.

• The default port of the GeminiDB Influx instance is 8635 and cannot be changed.

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 Influx instance

• GeminiDB Influx instances cannot be rebooted through commands. They must be rebooted on the console.
• Restarting an instance will interrupt services, so off-peak hours are the best time. Ensure that your application can be reconnected.

Viewing GeminiDB Influx instance backups

GeminiDB Influx instance backups are stored in OBS buckets and are invisible to you.

Changing the CPU or memory of a GeminiDB Influx instance

• Second-level intermittent disconnection occurs once when the specifications are changed on a single node. Therefore, the entire instance is intermittently disconnected several times. Ensure that the client can be reconnected. You are advised to change the specifications during off-peak hours.
• For a node whose specifications are being changed, its computing tasks are handed over to other nodes. Change specifications of nodes during off-peak hours to prevent instance overload.

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.

Recycle bin

• You can move unsubscribed yearly/monthly instances and deleted pay-per-use instances to the recycle bin. You can restore an instance that was deleted up to 7 days ago from the recycle bin.
• The recycling policy is enabled by default and cannot be disabled. Instances in the recycle bin are retained for 7 days by default, and this will not incur any charges.
• Currently, you can put a maximum of 100 instances into the recycle bin.
• If you delete an instance running out of storage, it will not be moved to the recycle bin.