MySQL server crash after running SELECT queries with a connection pool of 60
Posted by: Chinmay Ram
Date: June 10, 2022 06:37AM

MySQL server crashes when we run a set of select queries for a connection pool of 60. There seems to be no huge increase in the CPU, memory or any resources. The innodb_bufferpool_size is quite sufficient (approx 28GB). stack trace for the crash is mentioned below.


| key_buffer_size | 8388608
| max_connections | 1000
| innodb_log_buffer_size| 16777216
Server version: 8.0.26 MySQL Community Server - GPL



06:46:36 UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x7f5994000f80
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 = 7f5eac09bc50 thread_stack 0x46000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x3d) [0x20e7edd]
/usr/sbin/mysqld(handle_fatal_signal+0x30b) [0xf387fb]
/lib64/libpthread.so.0(+0x118e0) [0x7f61277e78e0]
/usr/sbin/mysqld(temptable::Handler::index_next_conditional(unsigned char*, temptable::Handler::NextCondition)+0x8c) [0x262d1fc]
/usr/sbin/mysqld(handler::ha_index_next(unsigned char*)+0x1ee) [0x103da2e]
/usr/sbin/mysqld(IndexScanIterator<false>::Read()+0x55) [0xd257d5]
/usr/sbin/mysqld(AggregateIterator::Read()+0x183) [0x12adbd3]
/usr/sbin/mysqld(MaterializeIterator::MaterializeQueryBlock(MaterializeIterator::QueryBlock const&, unsigned long long*)+0x133) [0x12ae213]
/usr/sbin/mysqld(MaterializeIterator::Init()+0x351) [0x12aeb71]
/usr/sbin/mysqld(NestedLoopIterator::Read()+0xd5) [0x12ac295]
/usr/sbin/mysqld(NestedLoopIterator::Read()+0xa7) [0x12ac267]
/usr/sbin/mysqld(MaterializeIterator::MaterializeQueryBlock(MaterializeIterator::QueryBlock const&, unsigned long long*)+0x133) [0x12ae213]
/usr/sbin/mysqld(MaterializeIterator::Init()+0x351) [0x12aeb71]
/usr/sbin/mysqld(MaterializeIterator::MaterializeQueryBlock(MaterializeIterator::QueryBlock const&, unsigned long long*)+0x8c) [0x12ae16c]
/usr/sbin/mysqld(MaterializeIterator::Init()+0x351) [0x12aeb71]
/usr/sbin/mysqld(AggregateIterator::Init()+0x27) [0x12ada27]
/usr/sbin/mysqld(Query_expression::ExecuteIteratorQuery(THD*)+0x21a) [0xebc8ca]
/usr/sbin/mysqld(Query_expression::execute(THD*)+0x2f) [0xebccaf]
/usr/sbin/mysqld(Sql_cmd_dml::execute(THD*)+0x186) [0xe47906]
/usr/sbin/mysqld(mysql_execute_command(THD*, bool)+0x9c8) [0xdf1ab8]
/usr/sbin/mysqld(dispatch_sql_command(THD*, Parser_state*)+0x40b) [0xdf50cb]
/usr/sbin/mysqld(dispatch_command(THD*, COM_DATA const*, enum_server_command)+0xdda) [0xdf638a]
/usr/sbin/mysqld(do_command(THD*)+0x194) [0xdf8184]
/usr/sbin/mysqld() [0xf29900]
/usr/sbin/mysqld() [0x259ac6e]
/lib64/libpthread.so.0(+0x744b) [0x7f61277dd44b]
/lib64/libc.so.6(clone+0x3f) [0x7f6125d5b40f]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f5994059038): is an invalid pointer
Connection ID (thread ID): 162
Status: NOT_KILLED

Options: ReplyQuote


Subject
Written By
Posted
MySQL server crash after running SELECT queries with a connection pool of 60
June 10, 2022 06:37AM


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.