Thread 140699996440320 has waited at trx0rseg.ic line 50 for 946 seconds
I'm seeing this repeatedly in my log:
--Thread 140699996440320 has waited at trx0rseg.ic line 50 for 946 seconds the semaphore:
X-lock on RW-latch at 0x7ff74ff50408 created in file buf0buf.cc line 778
a writer (thread id 140700155893504) has reserved it in mode SX
number of readers 0, waiters flag 1, lock_word: 10000000
Last time read locked in file lob0impl.cc line 1220
Last time write locked in file /var/tmp/portage/dev-db/mysql-community-8.0.21/work/mysql/storage/innobase/buf/buf0flu.cc line 1334
OS WAIT ARRAY INFO: signal count 152272
RW-shared spins 1313, rounds 1786, OS waits 920
RW-excl spins 36740, rounds 1105468, OS waits 37025
RW-sx spins 794, rounds 23820, OS waits 729
Spin rounds per wait: 1.36 RW-shared, 30.09 RW-excl, 30.00 RW-sx
------------
Then eventually
stack_bottom = 0 thread_stack 0x46000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x3c) [0x55c05ade7a7c]
/usr/sbin/mysqld(handle_fatal_signal+0x303) [0x55c059d08443]
/lib/libpthread.so.0(+0x14570) [0x7ff774f3b570]
/lib/libc.so.6(gsignal+0x141) [0x7ff774118df1]
/lib/libc.so.6(abort+0x121) [0x7ff774102535]
/usr/sbin/mysqld(+0xdf74ff) [0x55c059a684ff]
/usr/sbin/mysqld(ib::fatal::~fatal()+0xcd) [0x55c05b04a58d]
/usr/sbin/mysqld(srv_error_monitor_thread()+0xa45) [0x55c05afdd765]
/usr/sbin/mysqld(std::thread::_State_impl<std::thread::_Invoker<std::tuple<Runnable, void (*)()> > >::_M_run()+0xb5) [0x55c05aee8fa5]
/usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/libstdc++.so.6(+0xd0690) [0x7ff7744dc690]
/lib/libpthread.so.0(+0x83a7) [0x7ff774f2f3a7]
/lib/libc.so.6(clone+0x3f) [0x7ff7741e4faf]
Could this mean there is corrupted data in the structure or could it be a bug?
The version is 8.0.21.
Subject
Views
Written By
Posted
Thread 140699996440320 has waited at trx0rseg.ic line 50 for 946 seconds
1242
December 13, 2020 07:28PM
476
December 14, 2020 09:07AM
550
December 15, 2020 09:27PM
422
December 16, 2020 10:57AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.