running mysqld 5.7.19-17, as a new slave in a 1 Master 3 slave architecture
This is the first server to run on 5.7, others were to be upgraded, beginning today. This slave had been running error free for 4 days, when a simple insert caused a similar failure as referenced above.
2017-11-21T02:12:41.279263Z 0 [Warning] InnoDB: A long semaphore wait:
--Thread 139710996440832 has waited at row0ins.cc line 2511 for 241.00 seconds the semaphore:
X-lock on RW-latch at 0x7f1daef78f70 created in file buf0buf.cc line 1456
a writer (thread id 139709876315904) has reserved it in mode SX
number of readers 0, waiters flag 1, lock_word: 10000000
Last time read locked in file row0sel.cc line 3765
InnoDB: ###### Diagnostic info printed to the standard error stream
2017-11-21T02:24:33.293036Z 0 [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.
2017-11-21 02:24:33 0x7f1109c90700 InnoDB: Assertion failure in thread 139711155341056 in file ut0ut.cc line 917
key_buffer_size=67108864
read_buffer_size=4194304
max_used_connections=1
max_threads=4097
thread_count=2
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 33677646 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf0362b]
/usr/sbin/mysqld(handle_fatal_signal+0x471)[0x7a1561]
/lib64/libpthread.so.0(+0xf5e0)[0x7f1de00735e0]
/lib64/libc.so.6(gsignal+0x37)[0x7f1dde17c1f7]
/lib64/libc.so.6(abort+0x148)[0x7f1dde17d8e8]
/usr/sbin/mysqld[0x76f3f6]
/usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0xfd)[0x10d2a9d]
/usr/sbin/mysqld(srv_error_monitor_thread+0xadb)[0x106da5b]
/lib64/libpthread.so.0(+0x7e25)[0x7f1de006be25]
/lib64/libc.so.6(clone+0x6d)[0x7f1dde23f34d]
Given that this machine is not yet in service, I may just restart from a clean backup, but would like to know what's going on.
running mysqld 5.7.19-17, as a new slave in a 1 Master 3 slave architecture
This is the first server to run on 5.7, others were to be upgraded, beginning today. This slave had been running error free for 4 days, when a simple insert caused a similar failure as referenced above.
2017-11- 21T02:12: 41.279263Z 0 [Warning] InnoDB: A long semaphore wait:
--Thread 139710996440832 has waited at row0ins.cc line 2511 for 241.00 seconds the semaphore:
X-lock on RW-latch at 0x7f1daef78f70 created in file buf0buf.cc line 1456
a writer (thread id 139709876315904) has reserved it in mode SX
number of readers 0, waiters flag 1, lock_word: 10000000
Last time read locked in file row0sel.cc line 3765
InnoDB: ###### Diagnostic info printed to the standard error stream 21T02:24: 33.293036Z 0 [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.
2017-11-
2017-11-21 02:24:33 0x7f1109c90700 InnoDB: Assertion failure in thread 139711155341056 in file ut0ut.cc line 917
key_buffer_ size=67108864 size=4194304 connections= 1 size)*max_ threads = 33677646 K bytes of memory
read_buffer_
max_used_
max_threads=4097
thread_count=2
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0 mysqld( my_print_ stacktrace+ 0x3b)[0xf0362b] mysqld( handle_ fatal_signal+ 0x471)[ 0x7a1561] libpthread. so.0(+0xf5e0) [0x7f1de00735e0 ] libc.so. 6(gsignal+ 0x37)[0x7f1dde1 7c1f7] libc.so. 6(abort+ 0x148)[ 0x7f1dde17d8e8] mysqld[ 0x76f3f6] mysqld( _ZN2ib5fatalD1E v+0xfd) [0x10d2a9d] mysqld( srv_error_ monitor_ thread+ 0xadb)[ 0x106da5b] libpthread. so.0(+0x7e25) [0x7f1de006be25 ] libc.so. 6(clone+ 0x6d)[0x7f1dde2 3f34d]
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x30000
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
/lib64/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
Given that this machine is not yet in service, I may just restart from a clean backup, but would like to know what's going on.