Mysqld got signal 11

MySQL & MariaDB Percona Distribution for MySQL
,
1

after a failed request, the server hung up and stopped running
starts only in mode: innodb_force_recovery = 6
config:

[mysqld]
#innodb_force_recovery = 6
log-error                      = /var/log/mysql/error.log
slow-query-log-file            = /var/log/mysql/slow.log

bind-address    = 0.0.0.0
default-authentication-plugin=mysql_native_password
skip-name-resolve
key_buffer_size         = 64M
max_allowed_packet      = 128M
max_connections         = 300
read_buffer_size        = 256K
read_rnd_buffer_size    = 512K
net_buffer_length       = 256K
connect_timeout         = 30
lock_wait_timeout       = 300
character-set-server    = cp1251
group_concat_max_len    = 4194304
event_scheduler         = On
read_only               = On
transaction-isolation           = READ-COMMITTED

gtid_mode               = On
enforce_gtid_consistency= On
disabled_storage_engines="MyISAM,BLACKHOLE,FEDERATED,ARCHIVE,MEMORY"
binlog_checksum=NONE

tmp_table_size          = 256M
max_heap_table_size     = 256M
join_buffer_size        = 2M
preload_buffer_size     = 4M
max_prepared_stmt_count = 131056

binlog_row_image        = minimal
binlog_expire_logs_seconds = 432000
max_binlog_size         = 300M
relay-log-recovery      = 1
relay_log_space_limit           = 50G
master_verify_checksum          = ON
binlog_cache_size               = 1M
sync_binlog                     = 50
sync_relay_log                  = 2000

innodb-status-file
innodb_buffer_pool_size         = 3G
innodb_buffer_pool_instances    = 3
innodb_doublewrite              = 0
innodb_flush_log_at_trx_commit  = 0
innodb_flush_method             = O_DIRECT
innodb_lock_wait_timeout        = 10
innodb_log_file_size            = 512M
innodb_read_io_threads          = 6
innodb_write_io_threads         = 6
innodb_io_capacity_max          = 4000
innodb_io_capacity              = 2000
innodb_monitor_enable           = all
innodb_print_all_deadlocks      = ON

### Percona ###
thread_handling                 = pool-of-threads
innodb_corrupt_table_action     = salvage
slow_query_log = ON
log_slow_rate_limit = 50
log_slow_rate_type = query
long_query_time = 2
log_slow_verbosity = full

### Group Replication Settings ###
plugin_load_add=group_replication.so
group_replication_group_name=""
group_replication_start_on_boot=off
group_replication_local_address= "db-3:33061"
group_replication_group_seeds= "db-1:33061,db-2:33061,db-3:33061"
group_replication_bootstrap_group=off
sql_mode="NO_ENGINE_SUBSTITUTION"

log:

You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
2024-03-13T10:30:09.027007Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.18-9) starting as process 31845
10:30:29 UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
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 0x46000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x1fac551]
/usr/sbin/mysqld(handle_fatal_signal+0x333) [0x11d0fb3]
/lib64/libpthread.so.0(+0x12d80) [0x7fd67912cd80]
/usr/sbin/mysqld(lock_print_info_summary(_IO_FILE*, unsigned long)+0xc8) [0x20e62c8]
/usr/sbin/mysqld(srv_printf_innodb_monitor(_IO_FILE*, unsigned long, unsigned long*, unsigned long*)+0xc3c) [0x221b4fc]
/usr/sbin/mysqld(srv_monitor_thread()+0x150) [0x221b880]
/usr/sbin/mysqld(std::thread::_State_impl<std::thread::_Invoker<std::tuple<Runnable, void (*)()> > >::_M_run()+0xbd) [0x2117dbd]
/lib64/libstdc++.so.6(+0xc2a53) [0x7fd677a3fa53]
/lib64/libpthread.so.0(+0x82de) [0x7fd6791222de]
/lib64/libc.so.6(clone+0x43) [0x7fd67711ba53]
Please help us make Percona Server better by reporting any
bugs at https://bugs.percona.com/

You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash
2

With only a 3GB buffer pool, you should probably only have 1 instance.

Woah! You turned off InnoDB’s data protection! This should be enabled so that InnoDB can survive a crash.

This rarely needs to be changed: https://www.percona.com/blog/tuning-mysql-innodb-flushing-for-a-write-intensive-workload/

Unless you have 50,000 connections to MySQL, you should not be running with the thread pool plugin.

This mode is meant as “disaster recovery” mode. You should ONLY start MySQL to dump all data, then erase everything and import from that dump.

I see GR is running. What about the other nodes?

3

after update to Server version: 8.0.36-28 Percona Server (GPL), Release 28, Revision 47601f19
server started but I got another error:
other servers are working

2024-03-14T11:53:41.235232Z 0 [Warning] [MY-013737] [Repl] Plugin group_replication reported: 'This member joined a group on which all members do not support member actions, as such it did reset its member configuration to the default one.'
2024-03-14T11:53:41.236269Z 0 [Warning] [MY-013783] [Repl] This member joined a group on which all members do not support replication failover channels integration on Group Replication, as such it did reset its replication failover channels configuration to the default one.
2024-03-14T11:53:41.237011Z 0 [Warning] [MY-013426] [Repl] Plugin group_replication reported: 'Member version is read compatible with the group.'
2024-03-14T11:53:41.237174Z 24 [System] [MY-011511] [Repl] Plugin group_replication reported: 'This server is working as secondary member with primary member address sds360-db-1:3306.'
2024-03-14T11:53:41.237237Z 0 [System] [MY-011565] [Repl] Plugin group_replication reported: 'Setting super_read_only=ON.'
2024-03-14T11:53:41.237314Z 0 [ERROR] [MY-013467] [Repl] Plugin group_replication reported: 'No valid or ONLINE members exist to get the missing data from the group. For cloning check if donors of the same version and with clone plugin installed exist. For incremental recovery check if you have donors where the required data was not purged from the binary logs.'
2024-03-14T11:53:41.237410Z 0 [ERROR] [MY-011712] [Repl] Plugin group_replication reported: 'The server was automatically set into read only mode after an error was detected.'
2024-03-14T11:53:41.237533Z 0 [System] [MY-011565] [Repl] Plugin group_replication reported: 'Setting super_read_only=ON.'
2024-03-14T11:53:41.237599Z 0 [System] [MY-011503] [Repl] Plugin group_replication reported: 'Group membership changed to sds360-db-2:3306, sds360-db-1:3306, sds360-db -3:3306 on view 17103702251866697:31.'
2024-03-14T11:53:41.237648Z 0 [ERROR] [MY-011486] [Repl] Plugin group_replication reported: 'Message received while the plugin is not ready, message discarded.'
2024-03-14T11:53:42.237322Z 24 [System] [MY-014010] [Repl] Plugin group_replication reported: 'Plugin 'group_replication' has been started.'
2024-03-14T11:53:44.559615Z 0 [System] [MY-011504] [Repl] Plugin group_replication reported: 'Group membership changed: This member has left the group.