A TencentDB for MySQL instance experiences a sudden surge or a continuous growth in memory utilization. You can view detailed memory utilization monitoring data in the following chart:
After a sudden surge or a steady slow growth, the memory utilization reaches an unhealthy level of more than 96% and fluctuates slightly. In this case, the memory utilization may trigger custom Cloud Monitor memory alarms many times.
Inefficient SQL statements or incorrect database parameters can cause the memory utilization to increase. An unexpected business peak may cause OOM (out of memory) of two-node and three-node TencentDB for MySQL instances, and when the instances are unavailable due to OOM, a source-replica switch will be triggered. During the switch, instances are usually unavailable for less than 60 seconds. If the switch occurs during peak hours, business stability and continuity will be seriously affected.
In MySQL, memory can be roughly divided into two parts: globally shared memory and session-level private memory.
- Shared memory is allocated upon the creation of an instance and shared by all connections.
- Private memory is allocated by the system upon connection to the MySQL server.
Some special SQL statements or field types may cause the cache to be allocated to a single thread repeatedly. Therefore, all OOM exceptions are caused by the private memory of each connection. The risk of high memory utilization can be mitigated by limiting database connections and optimizing inefficient SQL statements. If this doesn't work, you can upgrade the memory configuration so as to improve the overall concurrency and stability of the database. For more information on memory parameters, please see Memory Allocation.
- Optimize slow SQL statements to reduce the session-level private memory usage. You can use DBbrain to analyze slow SQL statements.
- Reduce invalid persistent connections and lower the connection pool configuration or concurrency level on the program side without affecting the business. You can use DBbrain to view the current session information.
- Monitor memory utilization (optional and applicable to MySQL 5.7 and above): enable the performance schema feature, and query memory information from tables whose name starts with "memory_summary" in the performance_schema database. For example, the memory_summary_global_by_event_name table records global memory utilization.
- If the preceding steps don't work, upgrade the configuration of your TencentDB for MySQL instance.
- During the upgrade, your business can operate normally. After the upgrade, there will be a momentary disconnection. Please make sure that your business has a reconnection mechanism.
- To protect your business from being affected by insufficient memory or CPU resources, configure alarm policies for instance resources which help you identify potential resource shortage in advance. For more information, please see Alarm Policies (Cloud Monitor).