[ERROR] [FATAL] InnoDB: Semaphore

 

mysql版本:5.7.29

 

 

今天在导入大数据的dump文件的时候,数据库自动重启,查看错误日志如下:

 

2021-08-12T01:51:52.625334Z 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 4690ms. The settings might not be optimal. (flushed=155 and evicted=0, during the time.)
InnoDB: ###### Diagnostic info printed to the standard error stream
2021-08-12T01:51:56.796554Z 0 [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.
2021-08-12 09:51:56 0x7f0a63a6d700  InnoDB: Assertion failure in thread 139682598278912 in file ut0ut.cc line 918
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
01:51:57 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

 

解决办法:

关闭innodb_adaptive_hash_index

set global innodb_adaptive_hash_index=0;

 

上一篇:macOS 执行git命令时出现fatal: protocol ‘git@https‘ is not supported


下一篇:GIT·提交报错:fatal unable to access ‘XXX.git‘ OpenSSL SSL_read Connection was aborted