Comment 26 for bug 1040735

After more than 24 hours, the slave-only server I updated to try and replicate this again didn't hang, so it's been downgraded.

The main difference between it and the one that hung is that the hung one has a Fusion-IO based SSD array for storage, and the one that didn't hang is a RAID-10 array of hard drives.

Here's a diff of the config differences between the two servers. db02 is the one that didn't hang, db04 is the one that did. Hopefully this will be helpful.

Dan.

--- sugar-db02/etc/my.cnf 2012-08-28 14:26:10.000000000 -0400
+++ sugar-db04/etc/my.cnf 2012-08-23 05:45:16.000000000 -0400
@@ -49,21 +46,26 @@
 read_buffer_size=512K
 read_rnd_buffer_size=4M
 innodb_file_per_table
-innodb_buffer_pool_size=16G
+innodb_buffer_pool_size=28G

+innodb_adaptive_flushing_method = keep_average
 innodb_additional_mem_pool_size=48M
 innodb_log_buffer_size=16M
-innodb_flush_log_at_trx_commit=0
+innodb_flush_log_at_trx_commit=2
+innodb_read_ahead=none
+innodb_flush_neighbor_pages=0
 innodb_flush_method = ALL_O_DIRECT

 innodb_lock_wait_timeout=50
-innodb_log_group_home_dir=/data/logs
+innodb_log_group_home_dir=/dblogs/mysql
 innodb_data_home_dir=/data/mysql
 innodb_data_file_path=ibdata1:10M:autoextend
 innodb_log_files_in_group=2
 innodb_log_file_size=4G
+innodb_log_block_size=4096

-innodb_io_capacity=10000
+innodb_io_capacity=20000
 innodb_write_io_threads=64
 innodb_read_io_threads=64