Description:
2019-04-07T16:27:48.808323+08:00 0 [Warning] InnoDB: A long semaphore wait:
--Thread 140595609646848 has waited at row0ins.cc line 2501 for 241.00 seconds the semaphore:
S-lock on RW-latch at 0x7ff25ca994b8 created in file buf0buf.cc line 1460
a writer (thread id 140595591153408) has reserved it in mode exclusive
number of readers 0, waiters flag 1, lock_word: 0
Last time read locked in file row0ins.cc line 2501
Last time write locked in file /export/home/pb2/build/sb_0-24964902-1505320269.78/rpm/BUILD/mysql-5.7.20/mysql-5.7.20/storage/innobase/include/mtr0mtr.ic line 153
......
BACKGROUND THREAD
-----------------
srv_master_thread loops: 38025929 srv_active, 0 srv_shutdown, 1042877 srv_idle
srv_master_thread log flush and writes: 39068806
----------
SEMAPHORES
----------
OS WAIT ARRAY INFO: reservation count 1909289821
--Thread 140595609646848 has waited at row0ins.cc line 2501 for 242.00 seconds the semaphore:
S-lock on RW-latch at 0x7ff25ca994b8 created in file buf0buf.cc line 1460
a writer (thread id 140595591153408) has reserved it in mode exclusive
number of readers 0, waiters flag 1, lock_word: 0
Last time read locked in file row0ins.cc line 2501
Last time write locked in file /export/home/pb2/build/sb_0-24964902-1505320269.78/rpm/BUILD/mysql-5.7.20/mysql-5.7.20/storage/innobase/include/mtr0mtr.ic line 153
--Thread 140609515607808 has waited at row0ins.cc line 2501 for 242.00 seconds the semaphore:
S-lock on RW-latch at 0x7ff25ca994b8 created in file buf0buf.cc line 1460
a writer (thread id 140595591153408) has reserved it in mode exclusive
number of readers 0, waiters flag 1, lock_word: 0
......
END OF INNODB MONITOR OUTPUT
============================
InnoDB: ###### Diagnostic info printed to the standard error stream
2019-04-07T16:39:40.824859+08:00 0 [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.
2019-04-07 16:39:40 0x7fe2735fe700 InnoDB: Assertion failure in thread 140610575001344 in file ut0ut.cc line 916
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.
How to repeat:
I do not know how to repeat.
Only once.
