May 24, 2012

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

in /usr/lib/ocf/resource.d/heartbeat/ directory. To use this agent, you’ll need a Pacemaker configuration. As a startingMySQL configuration, Pacemaker will automatically add “skip-start-slave” for a saner behavior. One of the important setting is “log_slave_updates = OFF” (default value). In

Post: Infinite Replication Loop

to write a blog post about these infinite loop of binary log statements in MySQL Replication. To explain what they are, how to identify them… and how toin the loop, you can try to skip the statements by stopping the slave, set global SQL_SLAVE_SKIP_COUNTER and start the slave

Post: MySQL Query Cache

option query_cache_limit was implemented which limits result set which can be stored in query cache. If you need larger queries toto use query cache ? Third party application – You can’t change how it works with MySQL to

Post: Recovery beyond data restore

in this case ? Your main options are using Backup or Slave with delayed replication (which you already could have set up with mk-slaveto MySQL bugs or wrong use. Interesting enough very few people have their data recovery practices ironed out so they can answer how

Comment: MySQL Server Memory Usage

how do you determine the memory consumption per connection in average? This leads to…select’, ’378247551′ ‘Com_set_option‘, ’285487367′ ‘Com_show…’, ’8′ ‘Com_slave_start‘, ’0′ ‘Com_slave_stop’, ’0…used before. skipUSE ALL MEMORY AVAILABLE #innodb_log_buffer_size=8M # Lowered from 32M according to MySQL