Help Center/ TaurusDB/ FAQs/ Database Connections/ What Do I Do If the Number of GaussDB(for MySQL) Database Connections Reaches the Upper Limit?
Updated on 2024-09-05 GMT+08:00
View PDF
Share

What Do I Do If the Number of GaussDB(for MySQL) Database Connections Reaches the Upper Limit?

The number of database connections indicates the number of applications that can be simultaneously connected to a database, and is irrelevant to the maximum number of users allowed by your applications or websites.

If there is an excessive number of database connections, applications may fail to be connected, and the full and incremental backups may fail, affecting services.

Fault Locating

  1. Check whether applications are connected, optimize the connections, and release unnecessary connections.
  2. Check the specifications and scale them up if needed.
  3. Check whether any metrics are abnormal and whether any alarms are generated on the Cloud Eye console. Cloud Eye monitors database metrics, such as the CPU usage, memory usage, storage space usage, and database connections, and allows you to configure alarm policies to identify risks in advance if any alarms are generated. For details, see the Cloud Eye User Guide.

Solution

  1. Connect to an instance through a private network. Using a private network prevents congestion caused by insufficient bandwidth.

    For details, see:

    Connecting to a DB Instance over a Private Network

  2. On the console, set the parameter innodb_adaptive_hash_index to off to reduce lock wait time.

    For details, see Modifying a Parameter Template.

  3. Optimize slow queries.
Parent topic: Database Connections