If you are using Percona Replication Manager (PRM) with RHEL/CentOS prior to 6.4, upgrading …::heartbeat:IPaddr2): Started percona3 reader_vip_2 (ocf::heartbeat:IPaddr2): Started percona2 reader_vip_3 (ocf::heartbeat:IPaddr2): Started percona1 writer_vip (ocf::heartbeat…
Post: Choosing a MySQL HA Solution - Post-Webinar Q&A
June 7, 2013 By Leave a Comment
… split-brain situation. Typically DRBD is run in combination with heartbeat or pacemaker or something similar, and if one of the…’d suggest reading over the manual’s description of how replication filtering rules are processed. There are some informative flowcharts in… if you’re not using GTID-based replication. If you are using GTID-based replication, it looks like you’ll need to…
Post: Emulating global transaction ID with pt-heartbeat
November 4, 2011 By 6 Comments
… why we built a pseudo global transaction ID into pt-heartbeat, the replication heartbeat tool included with Percona Toolkit. It has some of…, even when automated. Wouldn’t it be nice if the replication heartbeat record on C actually said approximately which binary log and… have multiple heartbeat rows in your heartbeat table, and multiple instances of pt-heartbeat, one per server in your replication topology. The heartbeat table is…
Post: Actively monitoring replication connectivity with MySQL's heartbeat
December 29, 2011 By 2 Comments
… slave with replication‘s heartbeat enabled and connected to a 5.1 master doesn’t break the replication. Of course, the heartbeat will not…_received_heartbeats | 1476 | +—————————+——-+ Conclusion If you need to know when exactly the connection between your Master/Slaves breaks then replication‘s heartbeat is…
Post: Percona Replication Manager, a solution for MySQL high availability with replication using Pacemaker
November 29, 2011 By 102 Comments
… ocf:heartbeat:mysql \ params config=”/etc/mysql/my.cnf” pid=”/var/run/mysqld/mysqld.pid” \ socket=”/var/run/mysqld/mysqld.sock” replication…_vip_1 ocf:heartbeat:IPaddr2 \ params ip=”10.2.2.171″ nic=”eth0″ primitive reader_vip_2 ocf:heartbeat:IPaddr2 \ params ip… reader_vip_3 ocf:heartbeat:IPaddr2 \ params ip=”10.2.2.173″ nic=”eth0″ primitive writer_vip ocf:heartbeat:IPaddr2 \ params ip…
Post: Finding your MySQL High-Availability solution – Replication
November 13, 2009 By 6 Comments
… the most popular HA solution for MySQL, replication. High Availability solution for MySQL: Replication This HA solution is the easiest to implement… the availability of the MySQL replication link between the servers. Replication often break for various reasons and while replication is broken, there is… blog post, I’ll present another HA solution build around Heartbeat and DRBD.
Post: Finding your MySQL High-Availability solution – The questions
October 16, 2009 By 36 Comments
… the most common ones: – MySQL replication with manual failover – Master-Master with MMM manager – Heartbeat/SAN – Heartbeat/DRBD – NDB Cluster These technologies are… choices. Write capacity MySQL replication Fair Master-Master with MMM manager Fair Heartbeat/SAN (depends on SAN) Excellent Heartbeat/DRBD Good NDB Cluster…
Comment: Percona Replication Manager, a solution for MySQL high availability with replication using Pacemaker
May 27, 2012 By 102 Comments
… ocf:heartbeat:mysql \ params config=”/usr/local/mysql/etc/my.cnf” pid=”/usr/local/mysql/mysqld.pid” socket=”/tmp/mysqld.sock” replication…_vip_1 ocf:heartbeat:IPaddr2 \ params ip=”192.168.163.171″ nic=”eth0″ primitive reader_vip_2 ocf:heartbeat:IPaddr2 \ params ip… reader_vip_3 ocf:heartbeat:IPaddr2 \ params ip=”192.168.163.173″ nic=”eth0″ primitive writer_vip ocf:heartbeat:IPaddr2 \ params ip…
Comment: Finding your MySQL High-Availability solution – The questions
October 19, 2009 By 36 Comments
… lose data, ruling out replication, and needs HA and sharding. The only solution there is to have multiple Heartbeat/DRBD pairs, that… by Heartbeat/DRBD or NDB Cluster. @Todd: Replication are two different ways of replicating data, from my experience, DRBD is more reliable than replication…
Post: Percona Toolkit 2.1.9 is ready
February 15, 2013 By Leave a Comment
…. This release primarily aims to restore backwards-compatibility with pt-heartbeat 2.1.7 and older, but it also has important… bug 1103221: pt-heartbeat 2.1.8 doesn’t use precision/sub-second timestamps * Fixed bug 1099665: pt-heartbeat 2.1.8… of pt-heartbeat, made the tool report a huge amount of replication lag. This release makes the tool compatible with pt-heartbeat 2…
