Hi all
MySQL Community 5.1.41
RHEL-v5
I'm getting a "Transaction level 'READ-COMMITTED' in InnoDB...." Error while writing to a new DB in my M-M configuration.
I've followed these references for this particular bug/issue.
here ->
http://bugs.mysql.com/bug.php?id=47842 &
here ->
http://bugs.mysql.com/bug.php?id=40360
I've decided to move binlog_format to MIXED which should eliminate my issue.
It would be best to do this on the fly with no restart / of mysql.
So I'm wondering if its safe in a M-M environment to issue the SET GLOBAL binlog_format='MIXED'; command to both servers at the same time.
This will obviously have an effect on the current running transactions as well as those in the immediate pipeline.. Will this cause any ill effects to data being served?
Relevant current innodb and bin-log sections of my.cnf below..
## INNODB SETTINGS
innodb_data_home_dir = /var/lib/mysql/ibdata
innodb_data_file_path = ib_data1:100M:autoextend
innodb_log_group_home_dir = /var/lib/mysql/ibdata_logs
innodb_log_file_size = 256M
innodb_log_files_in_group = 2
innodb_log_buffer_size = 32M
innodb_buffer_pool_size = 4G
innodb_additional_mem_pool_size = 20M
innodb_support_xa = 1
#innodb_file_per_table = 1
innodb_flush_log_at_trx_commit = 1
innodb_flush_method = O_DIRECT
innodb_max_dirty_pages_pct = 80
#innodb_thread_concurrency = 16
#innodb_commit_concurrency = 8
## BINLOG SETTINGS
log-bin = /var/log/mysql/my2-bin
log-bin-index = /var/log/mysql/my2-bin.index
expire_logs_days = 4
sync_binlog = 1
- kpf