June 18, 2013

Post: No more MySQL Crash Safe Replication in 5.0 ?

… cloning Slave->Slave by use of LVM without pausing replication (so you can get consistent master position). It is all great but… impression this thing works. Until this issue is fixed getting Crash Safe replication with MySQL is not impossible but surely more complicated… do traditional and recommended way with FLUSH TABLES WITH READ LOCK for snapshot creation. This happens when you have large amount…

Comment: SELECT LOCK IN SHARE MODE and FOR UPDATE

…; And I can’t understand why. Transaction 1 takes X lock for record 192, then Transaction 2 try to take the… lock for that record) and it can’t! Why??? I have serialized access with GET_LOCK and RELEASE_LOCK and that helped to avoid lock wait timeouts, but i’am not sure that they are replication safe. Are they replication

Post: State of MySQL Market and will Replication live ?

… MySQL and get some HA out of the box even on the medium level. Seriously – MySQL Cluster, Continuent, Master-Master Replication, DRBD… – some companies I talk to are committed to “no vendor lock in” policy and would not like proprietary solutions, another – typically… getting it up and running fast and Scalability on the scale of Big Table with Map Reduce. Indeed I think MySQL Replication

Post: How FLUSH TABLES WITH READ LOCK works with Innodb Tables

… it works. Even though with general lock compatibility guidelines Read Lock should not conflict with another Read Lock, it does for this statement… from getting field list from all tables) Reads though would not be blocked, ie there is no MYISAM like table lock priority… writes to the slave can be done by simply pausing replication.

Post: MySQL Limitations Part 1: Single-Threaded Replication

… single-threaded replication. It is severe and getting much worse as servers get more and more CPUs and CPU cores. The replication replay process…? Here are a few I’ve seen: Use DRBD replication instead of MySQL replication. Problem: you end up with an idle standby… order. If any error occurred, such as a deadlock or lock wait timeout, then the coordinator would instruct the workers to…

Post: Making MySQL Replication Parallel

…, the problem is however implementing it right without changing MySQL Replication semantics – which is – Slave database state corresponds to master database… threads inside the server to share same transactional/lock context. In this case replication could accumulate number of queries execute them in… file and setup multi-master replication so slave can read all of them in parallel you can get replication parallel enough for many…

Post: Using LVM for MySQL Backup and Replication Setup

…The catch here is FLUSH TABLES WITH READ LOCK actually waits for all statements to complete, even…undo size is not large enough snapshot will get invalidated and backup will be aborted. Sometimes …_pos=401934686; 12) Run SLAVE START to restart replication. With slightly modified process you can clone …

Post: Percona XtraDB Cluster: Failure Scenarios with only 2 nodes

…,’percona1′,’peter’); ERROR 1213 (40001): Deadlock found when trying to get lock; try restarting transaction percona1 mysql> insert into percona values (0… sec) You can keep inserting data, it won’t be replicated and you will have 2 different version of your inconsistent… restart if you wish to continue. (FATAL) at galera/src/replicator_str.cpp:state_transfer_required():34 120723 23:45:30…

Post: READ-COMMITED vs REPETABLE-READ in tpcc-like load

… RBR mode (as READ-COMMITED does not support STATEMENT based replication in 5.1), and everything was run under XtraDB-9… got 60 Deadlock errors “1213, Deadlock found when trying to get lock; try restarting transaction” in READ-COMMITED mode, and 0 Deadlocks… less-tested READ-COMMITED does not work with statement-based replication in 5.1 with READ-COMMITED you may have more…

Post: INSERT INTO ... SELECT Performance with Innodb tables.

… in proper order. Gets pretty complicated ? Well all you need to know it had to be done fore replication to work right… log disabled ? If replication is not used you can enable innodb_locks_unsafe_for_binlog option, which will relax locks which Innodb sets… the name says it makes locks unsafe fore replication and point in time recovery, so use innodb_locks_unsafe_for_binlog option with…