{"id":2295,"date":"2012-02-05T09:32:45","date_gmt":"2012-02-05T14:32:45","guid":{"rendered":"http:\/\/www.bytebot.net\/blog\/?p=2295"},"modified":"2012-02-05T09:32:51","modified_gmt":"2012-02-05T14:32:51","slug":"replication-features-of-2011-by-sergey-petrunia","status":"publish","type":"post","link":"http:\/\/www.bytebot.net\/blog\/archives\/2012\/02\/05\/replication-features-of-2011-by-sergey-petrunia","title":{"rendered":"Replication features of 2011 by Sergey Petrunia"},"content":{"rendered":"

Sergey Petrunia<\/a> of the\u00a0MariaDB<\/a> project & Monty Program<\/a>.<\/p>\n

MySQL 5.5 GA at the end of 2010. MariaDB 5.3 RC towards the end of 2011 (beta in June 2011).<\/p>\n

MySQL 5.5 is merged to Percona Server 5.5 which included semi-sync replication, slave fsync options, atuomatic relay log recovery, RBR slave type conversions (question if this is useful or not), individual log flushing (very useful, but not many using), replication heartbeat, SHOW RELAYLOG EVENTS. About 2\/3rds of the audience use MySQL 5.5 in production, with only 2 people using semi-sync replication.<\/p>\n

MariaDB 5.3 brings replication features brings group commit in the binary log, which is merged into Percona Server 5.5. Checksums for binlog events which is merged from MySQL 5.6. Sergey goes in-depth about the group commit for the binary log<\/a>. To find out a little more about MariaDB replication changes, see Replication<\/a> in the Knowledgebase.<\/p>\n

There are several implementations of group commit. Facebook started it, followed by MariaDB & Oracle. Percona 5.5 is GA so the feature is there, its not in MySQL 5.6 (yet?), and MariaDB 5.3 is where its at. Seems like the MariaDB implementation is the best so far – refer to the Facebook benchmark<\/a> performed by Mark Callaghan.<\/p>\n

Annotated RBR<\/a> poses a compatibility problem. MariaDB 5.3 has annotate_rows, while MySQL 5.6 has rows_query event. They are different events. So you cannot have a MariaDB 5.3 master and a MySQL 5.6 slave at this moment. So MySQL 5.6 will have a flag to mark “ignorable” binlog events which will be merged into MariaDB and this will make binary logs compatible again.<\/p>\n

There is now also optimized RBR for tables with no primary key<\/a>.<\/p>\n

MySQL 5.6 also has crash-safe slave (replication information stored in tables). Crash-safe master (binary log recovery if the server starts & sees the binary log is corrupted). Parallel event execution<\/a> is something that is new in MySQL 5.6 which is the most important feature for Sergey.<\/p>\n

Pre-heating: There is mk-slave-prefetch (famous quote<\/a>: “Please don’t use mk-slave-prefetch on #MySQL unless you are Facebook.”). There is replication booster<\/a> by Yoshinori Matsunobu. There is a Python version<\/a> of mk-slave-prefetch that Facebook uses.<\/p>\n

Share this:<\/h3>