Server version: 5.5.27-log Percona XtraDB Cluster (GPL), wsrep_23.6.r356
mysqld.log
121001 15:37:47 InnoDB: Error; possible reasons:InnoDB: 1) Table rename would cause two FOREIGN KEY constraintsInnoDB: to have the same internal name in case-insensitive comparison.InnoDB: 2) table db.v3_cam_ip_plus /* Partition p00 */ exists in the InnoDB internal dataInnoDB: dictionary though MySQL is trying to rename table 08:37:47 UTC - mysqld got signal 11 ;This could be because you hit a bug. It is also possible that this binaryor one of the libraries it was linked against is corrupt, improperly built,or misconfigured. This error can also be caused by malfunctioning hardware.We will try our best to scrape up some info that will hopefully helpdiagnose the problem, but since we have already crashed, something is definitely wrong and this may fail.Please help us make Percona Server better by reporting anybugs at http://bugs.percona.com/key_buffer_size=2147483648read_buffer_size=67108864max_used_connections=106max_threads=301thread_count=39connection_count=38It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 22443738 K bytes of memoryHope that’s ok; if not, decrease some variables in the equation.Thread pointer: 0x2aad6424ea20Attempting backtrace. You can use the following information to find outwhere mysqld died. If you see no messages after this, something wentterribly wrong…stack_bottom = 401f40c8 thread_stack 0x40000/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7c14a5]/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x69b6c4]/lib64/libpthread.so.0[0x3b64c0eb10]/usr/sbin/mysqld[0x5ecda6]/usr/sbin/mysqld(_Z16explain_filenameP3THDPKcPcj26enum_explain_filename_mode+0x370)[0x5ed320]/usr/sbin/mysqld[0x7cce17]/usr/sbin/mysqld[0x7ce2c9]/usr/sbin/mysqld[0x83885d]/usr/sbin/mysqld[0x7faf0f]/usr/sbin/mysqld[0x7d9889]/usr/sbin/mysqld(_ZN12ha_partition17del_ren_cre_tableEPKcS1_P5TABLEP24st_ha_create_information+0x13d)[0x97b68d]/usr/sbin/mysqld(_Z18mysql_rename_tableP10handlertonPKcS2_S2_S2_j+0x115)[0x5edec5]/usr/sbin/mysqld(_Z17mysql_alter_tableP3THDPcS1_P24st_ha_create_informationP10TABLE_LISTP10Alter_infojP8st_orderb+0x2286)[0x5f7576]/usr/sbin/mysqld(_ZN21Alter_table_statement7executeEP3THD+0x4ec)[0x7a35bc]/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x3049)[0x5935e9]/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x333)[0x595b23]/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x21ff)[0x5985ff]/usr/sbin/mysqld(_Z10do_commandP3THD+0x169)[0x598db9]/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x15f)[0x63364f]/usr/sbin/mysqld(handle_one_connection+0x51)[0x633811]/lib64/libpthread.so.0[0x3b64c0673d]/lib64/libc.so.6(clone+0x6d)[0x3b644d3d1d]Trying to get some variables.Some pointers may be invalid and cause the dump to abort.Query (3364fa70): ALTER TABLE v3_cam_ip_plus PARTITION BY RANGE(TO_DAYS(dt))( PARTITION p00 VALUES LESS THAN (0) ENGINE = InnoDB, PARTITION p01 VALUES LESS THAN (734653) ENGINE = InnoDB, PARTITION p02 VALUES LESS THAN (734745) ENGINE = InnoDB, PARTITION p04 VALUES LESS THAN (734867) ENGINE = InnoDB, PARTITION p05 VALUES LESS THAN (734965) ENGINE = InnoDB, PARTITION MERGER_2012628 VALUES LESS THAN (735047) ENGINE = InnoDB, PARTITION pcurrent_2012628 VALUES LESS THAN (735048) ENGINE = InnoDB, PARTITION pcurrent_2012629 VALUES LESS THAN (735049) ENGINE = InnoDB)Connection ID (thread ID): 645329Status: NOT_KILLEDYou may download the Percona Server operations manual by visitinghttp://www.percona.com/software/percona-server/. You may find informationin the manual which will help you identify the cause of the crash.121001 15:40:58 InnoDB: Error: table 121001 15:40:58 [Warning] Invalid (old?) table or database name '#sql5534_1_2’tmp.<result 2 when explaining filename ‘#sql5534_1_2’> does not exist in the InnoDB internalInnoDB: data dictionary though MySQL is trying to drop it.InnoDB: Have you copied the .frm file of the table to theInnoDB: MySQL database directory from another database?InnoDB: You can look for further help fromInnoDB: MySQL :: MySQL 8.0 Reference Manual :: 15.21 InnoDB Troubleshooting
mysqld got signal 11
perror 11OS error code 11: Resource temporarily unavailable
My server has 32GB RAM.
innodb settings:
innodb_max_dirty_pages_pct=0innodb_log_file_size = 1Ginnodb_buffer_pool_size = 8Ginnodb_additional_mem_pool_size = 4M #global bufferinnodb_status_file #extra reportinginnodb_file_per_table #enable alwaysinnodb_flush_log_at_trx_commit = 2 #2/0 = perf, 1 = ACIDinnodb_table_locks = 0 #preserve table locksinnodb_log_buffer_size = 128M #global bufferinnodb_lock_wait_timeout = 60innodb_thread_concurrency = 16 #recommend 2x core quantityinnodb_commit_concurrency = 16 #recommend 4x num disksinnodb_flush_method = O_DIRECT #