June 19, 2013

Post: How to fix your PRM cluster when upgrading to RHEL/CentOS 6.4

what happensmysql): Master percona1 (unmanaged) p_mysql:1 (ocf::percona:mysql): Slave percona2 (unmanaged) p_mysql:2 (ocf::percona:mysql): Slave percona3 (unmanaged) And now you are able to

Post: Choosing a MySQL HA Solution - Post-Webinar Q&A

to do it. One way is to set up replication filters on the slave, as described in the MySQL manual. You can configure the slave to only replicateMySQL‘s internal understanding of what‘s happening on the system below. Having never experimented with GlusterFS, though, I decided to

Post: Disconnecting a replication slave is easier with MySQL 5.5+ (RESET SLAVE vs. RESET SLAVE ALL)

… disconnect a replication slave? In short For MySQL 5.0 and 5.1, run STOP SLAVE, CHANGE MASTER TO MASTER_HOST=” and then RESET SLAVE. For MySQL 5… we try to restart replication, it fails. However, I don’t like the error message, specifically the ‘fix in config file’ part. What happens if we…

Post: Automation: A case for synchronous replication

to MySQL Replication based solution. With MySQL Replication you have to have one Master node which handles traffic. You may be able to send some traffic to Slavesin the previous article is not needed. On the contrary. Not well tested clusters fail and they often fail harder than MySQL Replication

Post: Reasons for MySQL Replication Lag

MySQL Replication Lag. The story is typically along the lines everything is same as before and for some unknown reason the slaveslave read traffic from non warmed up slave will often cause warmup to be longer, because it has to happen in the single thread. In

Post: Upgrading MySQL

in MySQL history when issues would only happen at high load. You can do this inSlave(s) If you want to minimize downtime it is best to use MySQL Replication for upgrade. Once you have setup slave

Post: MySQL Replication vs DRBD Battles

to the point what we’re comparing here – it is mainly DRBD to MySQL Replication based techniques (lets leave MySQLto have lost transactions which may happen with async replication. Another similar case is when you’re looking to ensured consistency – MySQL Replication

Post: Percona XtraDB Cluster (PXC): what about GRA_*.log files ?

to understand what‘s is happening. As the GRA files contain binlog events in ROW format representing the failed transaction this post explains how toMySQL replication log Now we need to select one GRA log file: [root@node2 mysql]# ls GRA_*.log GRA_3_3.log [root@node2 mysql

Post: Percona Replication Manager, a solution for MySQL high availability with replication using Pacemaker

to a level where we started looking at other ways of achieving higher availability using MySQL replicationto MMM If the master fails, a new master is promoted from the slaves, no master toto the main Pacemaker resource agents branch. More testing and cleaning will be needed before that happen

Post: Percona XtraDB Cluster - installation and setup webinar follow up Q&A

to fail with the tar stream being from the future. The 0.3 – 0.4 second delay seems too much to me. According toin PXC can be a master or a slave on asynchronous replication, galera and built-in mysql replication