… I had an interesting surprise with concurrent inserts into a MyISAM table. The inserts were not happening concurrently with SELECT statements… be serialized for the binary log; otherwise replaying the binary log can result in a different order of execution. The MySQL manual actually says this…
Post: Filtered MySQL Replication
November 7, 2007 By 7 Comments
… fan of filtered or partial MySQL Replication (as of version MySQL 5.0) – there is enough … allowing replication to control what will be logged to binary log and so replicated. On the Slave …MyISAM tables, because MyISAM can’t be disabled and so if you create tables as MYISAM or ALTER them to MyISAM…
Post: MySQL Crash Recovery
July 30, 2006 By 26 Comments
… care of or which may seriously affect MySQL Performance. MyISAM Corruption – If you’re writting to MyISAM tables there is very large chance… use innodb-safe-binlog option in MySQL 4.1 so your Innodb log and binary log are synchronized. In MySQL 5.0 XA is taking care of this synchronization. .frm Corruption – Few people know MySQL is…
Post: Using LVM for MySQL Backup and Replication Setup
August 21, 2006 By 53 Comments
… for all local disk based storage engines It works with MyISAM and Innodb and BDB, It also should work with Solid… record binary log position which is done by running SHOW MASTER STATUS – This is binary log position you’ll need to point your MySQL Slaves created from this snapshot. 4) Snapshot created, now you want to let MySQL…
Post: Jeremy Cole on MySQL Replication
May 27, 2006 By 12 Comments
… they are quite different for Replication. As you probably know MyISAM uses buffered IO so if master crashes you’re out…’m surprised to read enabling binary log drops update performance. I guess Jeremy speaks about enabling binary log and setting sync_binlog option which… to flush their cache. Watch out for MySQL 5.0 – if you enabled Binary log with MySQL 5.0 you loose group commit which…
Post: MySQL Server Variables - SQL layer or Storage Engine specific.
June 8, 2006 By 14 Comments
… does it mean MyISAM variables are not important ? Not really. You still have some tables in MyISAM format in “mysql” database. Plus HEAP… in practice it is MyISAM related. expire_logs_days This is replication/binlogging related options – when to delete binary logs from master. It does…
Post: MySQL Replication vs DRBD Battles
April 28, 2008 By 12 Comments
… one while with MySQL Replication you can use Maatkit to merge the changes after all, also you can review binary logs to see… storage engines you’re using – DRBD does not work with MyISAM (check required) so you need to have processes to ensure… also allows building very nice mixed environments with MySQL – for example you can replicate binary logs using DRBD so if master node fails…
Post: No more MySQL Crash Safe Replication in 5.0 ?
January 29, 2008 By 7 Comments
… expected. Innodb during recovery also prints position in the MySQL binary log: InnoDB: Last MySQL binlog file position 0 589600615, file name ./galax-bin… you’re only using Innodb tables and not touching your MyISAM system tables) and use this position to point to proper… master, or later use for point in time recovery using binary log.
Post: When would you use SAN with MySQL ?
March 9, 2009 By 18 Comments
… systems. MySQL has to do more than one fsync() for the log because it internally implements XA to synchronize with binary log and also… (as SAN users often are) you better have binary log flushed on commit too. MySQL also has broken group commit (which we have… having only one IO at the time if Innodb or MyISAM tables are used. There is read-ahead functionality but usually…
Post: Managing Slave Lag with MySQL Replication
October 12, 2007 By 11 Comments
… MyISAM slaves used for long reporting queries can have queries running for hours which stalls replication progress for this time. As MySQL… Master-Master setup do not forget to disable binary logging with SET SQL_BIN_LOG=0 before you run ALTER TABLE query. Replication… being replicated. Unfortunately MySQL Slow Query Log does not log replication queries. Though this is one of few slow query logging improvements you can…
