Usage notes
Graph Database (GDB) handles basic database operations and maintenance (O&M) for you, such as managing high availability and applying security patches. However, you must be aware of the usage constraints for GDB instances.
Feature | Usage constraint |
Instance deployment | GDB instances can be created only in the following regions:
Note The supported regions are for reference only. For the actual list of supported regions, see the purchase page in the console. |
Data backup |
|
Data restoration |
|
Instance upgrade | A GDB instance upgrade causes a transient connection disconnection. To prevent service interruptions, prepare for the upgrade in advance and configure your application to automatically reconnect. |
Failover | If the primary node of a GDB High-availability Edition instance fails, the system quickly switches to the secondary node. A transient connection disconnection occurs during the failover. Configure your application to automatically reconnect to prevent service interruptions. |
Storage space | If the storage space of a GDB instance is full, the instance is automatically locked and becomes read-only. Regularly check your storage space usage. |
Performance optimization | If a GDB instance has insufficient CPU cores, memory, IOPS, storage space, or connections, database performance may be affected. To resolve this, optimize your data or upgrade the instance type. |