Comment 10 for bug 1099742

Hi Vladimir,

Unfortunately the gdb backtrace didn't provide much information since mysqld binary was stripped. I tried to reproduce this with the settings you provided, but with no success. Perhaps it somehow also depends on your load, your OS configuration and the way you initialize shutdown. I still believe this is triggered by some mysqld option or a combination of those. I have rounded a list of suspects here (mostly because they are different from usual settings and so far you're the only one who experiences this bug):

innodb_log_file_size=5242880
innodb_support_xa=ON
innodb_thread_concurrency=32
myisam_recover_options=BACKUP
max_binlog_size=104857600

Could you try to reproduce the bug with the following settings instead:

innodb_log_file_size=128M
innodb_support_xa=OFF
innodb_thread_concurrency=0
myisam_recover_options=OFF
max_binlog_size=1G

Note that changing innodb_log_file_size requires graceful shutdown and removal of old innodb log files (ib_logfile*). Also it seems like you may have a number of configuration files in /etc/mysql/conf.d which may overwrite the settings from /etc/my.cnf, so please be careful to place these settings into the last file to be included (most likely wsrep.cnf).

Also, could you try to reproduce the bug with wsrep_provider='none' ?