Need a help with Percona Mysql 8.0.19-10 crush investigation.

Guys Hi, I am hitting a crush on one of my MYSQL Servers with such a log below.
Both Servers are on Google Cloud and have 8CPU Cores and 52GB RAM and abolutely same configuration (difference in databases only)
This is only part of log: 

2020-04-15T13:44:25.184454Z 4965526 [Warning] [MY-010055] [Server] IP address ‘’ could not be resolved: Name or service not known
13:44:25 UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x7fed09633c10
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 = 7fef46212c30 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x3d) [0x200b90d]
/usr/sbin/mysqld(handle_fatal_signal+0x333) [0x11cf0f3]
/lib64/ [0x7ffa1773f5f0]
/usr/sbin/mysqld(dict_foreign_qualify_index(dict_table_t const*, char const**, char const**, unsigned long, dict_index_t const*, dict_index_t const*, bool, unsigned long)+0xa1) [0x23ab4f1]
/usr/sbin/mysqld(dict_foreign_find_index(dict_table_t const*, char const**, char const**, unsigned long, dict_index_t const*, bool, unsigned long)+0x8c) [0x23ab68c]
/usr/sbin/mysqld() [0x20ff35a]
/usr/sbin/mysqld(bool ha_innobase::commit_inplace_alter_table_impl<dd::Table>(TABLE*, Alter_inplace_info*, bool, dd::Table const*, dd::Table*)+0x110d) [0x211603d]
/usr/sbin/mysqld(ha_innobase::commit_inplace_alter_table(TABLE*, Alter_inplace_info*, bool, dd::Table const*, dd::Table*)+0xae) [0x21186ae]
/usr/sbin/mysqld() [0x1117ec4]
/usr/sbin/mysqld(mysql_alter_table(THD*, char const*, char const*, HA_CREATE_INFO*, TABLE_LIST*, Alter_info*)+0x61c5) [0x112c2f5]
/usr/sbin/mysqld(Sql_cmd_alter_table::execute(THD*)+0x483) [0xfed8a3]
/usr/sbin/mysqld(mysql_execute_command(THD*, bool)+0x3c90) [0x108da00]
/usr/sbin/mysqld(Prepared_statement::execute(String*, bool)+0x949) [0x10bc359]
/usr/sbin/mysqld(Prepared_statement::execute_loop(String*, bool)+0xb4) [0x10bebe4]
/usr/sbin/mysqld(mysqld_stmt_execute(THD*, Prepared_statement*, bool, unsigned long, PS_PARAM*)+0x191) [0x10c01f1]
/usr/sbin/mysqld(dispatch_command(THD*, COM_DATA const*, enum_server_command)+0x1895) [0x1091875]
/usr/sbin/mysqld(do_command(THD*)+0x204) [0x1092ce4]
/usr/sbin/mysqld() [0x11c0050]
/usr/sbin/mysqld() [0x24e57dc]
/lib64/ [0x7ffa17737e65]
/lib64/ [0x7ffa158be88d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fed0984d498): alter table user_group_to_coupons add constraint user_group_to_coupons_user_group_id_foreign foreign key (user_group_id) references user_groups (id) on delete CASCADE on update CASCADE
Connection ID (thread ID): 4965497

Please help us make Percona Server better by reporting any
bugs at

You may download the Percona Server operations manual by visiting You may find information
in the manual which will help you identify the cause of the crash.
2020-04-15T13:44:36.673526Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.19-10) starting as process 4131
100 200
2020-04-15T14:04:41.324762Z 0 [System] [MY-010229] [Server] Starting XA crash recovery…
2020-04-15T14:04:41.348223Z 0 [System] [MY-010232] [Server] XA crash recovery finished.
2020-04-15T14:04:42.225483Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2020-04-15T14:04:42.731240Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: ‘8.0.19-10’ socket: ‘/var/lib/mysql/mysql.sock’ port: 3306 Percona Server (GPL), Release 10, Revision f446c04.
2020-04-15T14:04:42.748037Z 7 [Warning] [MY-010055] [Server] IP address ‘’ could not be resolved: Name or service not known
2020-04-15T14:04:42.811146Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: ‘/var/lib/mysql/mysqlx.sock’ bind-address: ‘::’ port: 33060
2020-04-15T14:04:42.922549Z 9 [Warning] [MY-010055] [Server] IP address ‘’ could not be resolved: Name or service not known
2020-04-15T14:04:43.285452Z 10 [Warning] [MY-010055] [Server] IP address ‘’ could not be resolved: Name or service not known

This is my conf file: 

<br>port = 3306<br>socket = /var/lib/mysql/mysql.sock<br><br>[mysqld]<br><br>user = mysql<br>default-storage-engine = InnoDB<br>socket = /var/lib/mysql/mysql.sock<br>pid-file = /var/lib/mysql/<br>sql_mode = "TRADITIONAL,ALLOW_INVALID_DATES,ERROR_FOR_DIVISION_BY_ZERO"<br><br>key-buffer-size = 32M<br>myisam-recover-options = FORCE,BACKUP<br><br>default_authentication_plugin = mysql_native_password<br>max-allowed-packet = 1073741824<br>max-connect-errors = 1000000<br>skip-external-locking<br><br>datadir = /var/lib/mysql/<br><br>log-bin = /var/lib/mysql/mysql-bin<br>binlog_expire_logs_seconds = 1209600<br>max_binlog_size = 256M<br>relay_log_info_repository = TABLE<br>binlog_checksum = NONE<br>log_slave_updates = ON<br>binlog_format = ROW<br><br>key-buffer-size = 256M<br>sort-buffer-size = 16M<br>join-buffer-size = 8M<br>read-buffer-size = 8M<br>read-rnd-buffer-size = 2M<br>tmp-table-size = 64M<br>thread-stack = 256K<br>#table-open-cache = 500<br>thread-cache-size = 16384<br>table-open-cache-instances = 1<br>open-files-limit = 65000<br>table-definition-cache = 4096<br><br>net-read-timeout = 300<br>net-write-timeout = 300<br>interactive_timeout = 300<br>wait_timeout = 300<br>innodb-flush-method = O_DIRECT<br>innodb-log-files-in-group = 2<br>innodb-log-file-size = 1G<br>innodb-flush-log-at-trx-commit = 1<br>innodb-file-per-table = 1<br>innodb-buffer-pool-size = 32768M<br>innodb_buffer_pool_instances = 64<br>innodb_buffer_pool_chunk_size = 512M<br>innodb_log_buffer_size = 1024M<br>
log-error = /var/log/mysql/mysql-error.log<br>log-queries-not-using-indexes = 1<br>slow-query-log = 1<br>slow-query-log-file = /var/log/mysql/mysql-slow.log<br>long-query-time = 2<br>bind-address =<br>max-allowed-packet = 1G<br>max-connections = 10000<br>server-id = 208

Please advice, where to dig the problem? 

Hi @stinger we think this looks like it could be a bug. 
Would you be OK to report this to JIRA so that our bug research team can look at it, please? The URL is and the forms there will lead you through the information that’s needed, and you’ll be kept informed on progress. You can also check if it’s been spotted before. 
The open source forums are more “information” than “bug” though you will get the forum bug badge if you come back and paste the JIRA report link here :slight_smile:

Hi, @“lorraine.pocklington”
Thank you for your advice, I will follow it!