AWS MySQL RDS Case Stops Responding and Starts Automatically

Question

We have an instance of AWS MySQL RDS about 1.7T in size. Sometimes it becomes unresponsive and no operations can be performed.

• CPU utilization, IOPS write, IOPS read, queue depth, write throughput, write latency and read latency to zero.
• The number of connections is added.
• "Show innodb engine status" freezes

• Many requests (about 25 for each) using rdsadmin, which are in a hang state.

  SELECT count(*) from mysql.rds_replication_status WHERE action = 'reset slave' and master_host is NULL and master_port is NULL GROUP BY action_timestamp,called_by_user,action,mysql_version,master_host,master_port ORDER BY action_timestamp LIMIT 1;
  
  SELECT NAME, VALUE FROM mysql.rds_configuration; 
  

• After a while, the instance automatically reboots with the following error.

  A MySQL reboot is initiated to troubleshoot MySQL backup issues. Please note that as part of this survey, a database snapshot will be executed after the MySQL restart is complete.

What could be the problem? This happens quite often. Sometimes, to our surprise, this happens during off-peak times.

Answer 1

I ran into the same issue and raised an issue with AWS support. Got the following explanation:

---

RDS , " " (PITR). , RDS- RDS, , , . , , DB.

RDS multi-AZ, - :

Multi AZ 2 : 1- Single Box Experience, , . 2 - , Single AZ.

, , AWS , AWS , , .

---

, . 3 .

Answer 2

db, , , , , .

mysql .

, .

Answer 3

, 5.6.34.