What Should I Do If a GaussDB Database Problem Causes a Connection Failure?

Check whether any of the following problems occur on the GaussDB instance:

1. The GaussDB instance is not properly connected.

   Solution: Check the connection. If you connect to the GaussDB instance through a private network, the instance can be accessed only through an ECS in the same VPC. If you connect to a GaussDB instance through a public network, the ECS and the instance can be in different VPCs.

2. The maximum number of connections has been reached.

   Solution: Check whether the CPU usage and the number of current connections are normal by using GaussDB resource monitoring. If either of them reaches the maximum, reboot, disconnect, or change the CPU and memory of the GaussDB instance.

3. The DB instance is abnormal. For example, the instance is suspended during reboot, the GaussDB system is faulty, or the instance or table is locked.

   Solution: Reboot the instance to see if the problem is resolved. If the problem persists, contact technical support.