June 20, 2013

Post: Repair MySQL 5.6 GTID replication by injecting empty transactions

… post I explained how to repair MySQL 5.6 GTID replication using two different methods…. entry ’4′ for key ‘PRIMARY” on query. Default database: ‘test’. Query: ‘insert into t VALUES(NULL,’salazar’)’ …different ways to find the failed transaction. You can examine the binary logs or you can also check

Post: MySQL 5.6 Compatible Percona Toolkit 2.2 Released

Check out the Percona Toolkit supported platforms and versions. When you upgrade to MySQL 5.6, be sure to upgrade to…: analyzing MySQL query logs. So the ability to parse memcached, Postgres, Apache, and other logs was…-time to limit how long they run. There are more changes in addition to those …

Post: Is your MySQL buffer pool warm? Make it sweat!

mysql_slowlogd. This daemon is similar to running `tail -f slow.log`, except that it knows how to follow the log stream across log…playback –mysql-host 127.0.0.1 –mysql-username playback –mysql-password PaSSwOrd –mysql-schema schema_name –query-log…lines up with the blue part. Check back Thursday…

Post: MySQL and Percona Server in LinkBench benchmark

how to setup and run this benchmark, can be found here. We decided to run this benchmark for MySQL… used this dataset to check server behavior …how to run benchmark: [mysqld] user=root port=3306 innodb_buffer_pool_size = 30G innodb_flush_method = O_DIRECT innodb_log…=1000 query_cache_size=0 query_cache…

Post: How to Monitor MySQL with Percona's Nagios Plugins

to deadlocks and timeouts, applications often don’t handle or log this error appropriately. The pmp-check-mysql-status plugin can be configured tochecking that the server is alive and responds to a query. The pmp-check-mysql-status is also very flexible and can be used to

Post: How to convert MySQL's SHOW PROFILES into a real profile

how much time MySQL spends in various phases of queryquery consumed 0.18 seconds. Where did the time go? mysql> SHOW PROFILE FOR QUERY 1; +———————-+———-+ | Status | Duration | +———————-+———-+ | starting | 0.000032 | | checkinglogging slow query

Post: Slow Query Log analyzes tools

Query Log – Especially after the changes to log all queries slow query log may be growing too rapidly to follow, so we implemented slow query log filter (based on parse_mysql

Post: Flexviews - part 3 - improving query performance using materialized views

to using mysql binary logsto convert it. You can easily check that it parses by running the SELECT portion, adding LIMIT 0 toto actually build the contents of the view, making it available for querying: mysqlhow you can combine both types of views together. The complete method examples show how to

Post: How to use tcpdump on very busy hosts

… mk-query-digest output was obviously bogus when compared to the host’s slow-query-log (for example, none of the top 5 slow queries reported by mkqd appeared in the actual slow logto capture tcpdump data in seconds (1200 = 20 min) TMP=’/tmp’ LOCKFILE=”$self.lockfile” TMPfile=”$self.temp” RESfile=”$self.result” # check lock…