… focused on MySQL 5.6 GTIDs. You can find part one here. Our goal will be to go from setup #1 to setup… scenarios: For these tests, all servers are running on 127.0.0.1 with ports ranging from 10000 for s0 to 10004 for….0.0.1‘,master_user=’rsandbox’,master_password=’rsandbox’,master_port=10001,master_auto_position=1; s0> start slave; # For s1, s3 and s4 mysql…
Post: Percona Server for MySQL 5.5.31-30.3 now available
May 24, 2013 By Leave a Comment
… Server for MySQL version 5.5.31-30.3[/caption] Percona is glad to announce the release of Percona Server for MySQL 5.5.31-30.3 on May 24, 2013 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.5.31, including all the bug fixes in it, Percona Server 5.5.31-30.3 is now…
Post: Experiences with the McAfee MySQL Audit Plugin
May 23, 2013 By 4 Comments
… for the test (5.5.28-29.1). This is needed as the plugin needs the offset to some MySQL data structures that, the…_json_file=1 audit_json_socket_name=/tmp/audit.sock #audit_json_socket=1 audit_json_log_file=/var/lib/mysql/audit.log…”} {“msg-type”:”activity”,”date”:”1369155747383″,”thread-id”:”6440″,”query-id”:”0“,”user”:”debian-sys-maint”,”priv_user”:”debian-sys-maint”,”host…
Post: Summertime Percona MySQL training update
June 6, 2013 By 1 Comment
… – 5pm In July we have: Moving to MySQL 5.6 – Utrecht, Netherlands Begins Monday, July 1, 2013 , 9am – 5pm London, United Kingdom Begins… – 5pm Moving to MySQL 5.6 – Belfast, IE Begins Thursday, August 1, 2013 , 9am – 5pm In August we have: Moving to MySQL 5.6 – Miami, FL Begins Monday, August 5, 2013 , 9am – 5pm Moving to MySQL 5…
Post: MySQL and the SSB - Part 2 - MyISAM vs InnoDB low concurrency
May 22, 2013 By Leave a Comment
… In my previous blog post I compared MySQL 5.5.30 to MySQL 5.6.10, both with default settings using… Flight #2 Flight #2 is similar to Flight #1. MyISAM is faster than InnoDB when the …recommended to prevent assorted security risks symbolic-links=0 innodb_stats_persistent innodb_stats_auto_update=off …
Post: Percona MySQL University @Portland next Monday!
June 12, 2013 By Leave a Comment
… new Features in MySQL 5.6 Garrick Peterson, a member of Percona’s RemoteDBA team, will talk about MHA for MySQL High Availability… replication integrity And finally, Andrew Ferlitsch will share with how MySQL can be used to provide access to government data. The…… 
So register now! Please also join the Portland MySQL Meetup group for more MySQL-focused events in Portland If you love the…
Post: Choosing a MySQL HA Solution - Post-Webinar Q&A
June 7, 2013 By Leave a Comment
… with a two-NIC bonded pair you’ll get roughly 1.67x the throughput of a single port. [Don’t try…: What is my recommendation for MySQL 5.6? Is MHA ready for MySQL 5.6? A: My personal recommendation for MySQL 5.6, based on what…: Incorrect information in file: ‘./mysql/servers.frm’ ERROR: 1033 Incorrect information in file: ‘./mysql/servers.frm’ Running mysql_install_db under strace, I…
Post: Multicast replication in Percona XtraDB Cluster (PXC) and Galera
June 5, 2013 By
…, this isn’t really much different from standard mysql replication. 1 master with 5 async slaves is going to send a separate replication… interface, eth1: [all nodes]# ip ro add dev eth1 224.0.0.0/4 [all nodes]# ip ro show | grep 224 224… mysql]# service mysql stop [root@node1 mysql]# service mysql stop [root@node1 mysql]# service mysql start –wsrep_cluster_address=gcomm:// [root@node2 mysql]# service mysql start [root@node3 mysql…
Post: Percona Server 5.6.11-60.3 first Release Candidate now available
June 3, 2013 By 3 Comments
… 5.6.11-60.3 on June 3rd, 2013 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.6.11, including all the bug fixes in it, Percona Server 5.6.11-60.3 is… #1177780, bug fixed #1154954. Release notes for Percona Server for MySQL 5.6.11-60.3 are available in our online documentation…
Comment: Converting Character Sets
June 12, 2013 By 22 Comments
Approach number 1 is correct. There was no truncation: MEDIUMTEXT is bigger than TEXT. MySQL does this to make sure there’s *no* truncation, as explained in the manual – http://dev.mysql.com/doc/refman/5.1/en…
