…! # For s0,s1, s3, s4 mysql> stop slave; mysql> change master to master_port=10002; mysql> start slave; # And then check … mysqlbinlog to start reading from there? Unfortunately, there is no –start-gtid-position option or equivalent. See bug #68566…., it is good to be aware of the current limitations…
Post: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
May 21, 2013 By 8 Comments
… specific replication topology. However you should keep in mind some limitations of the current implementation. This post is the first one… slave #2, change configuration and restart it: mysql> show slave status\G [...] Slave_IO_Running: No Slave_SQL_Running: Yes [...] The error log… not on slave #2: # slave #1 mysql> change master to master_auto_position = 1; mysql> start slave; and let’s create a…
Post: MySQL and the SSB - Part 2 - MyISAM vs InnoDB low concurrency
May 22, 2013 By Leave a Comment
… cold test. All tests were done with no concurrency. The hardware for this test was …be good for raw performance, but there are limitations which MyISAM imposes that are difficult to work …=/mnt/mysql56/data basedir=/usr/local/mysql socket=/var/lib/mysql/mysql.sock user=justin innodb_buffer_pool_…
Post: Choosing a MySQL HA Solution - Post-Webinar Q&A
June 7, 2013 By Leave a Comment
… limit the amount of data sent over the wire, but it comes at the cost of having binary logs which are no… is my recommendation for MySQL 5.6? Is MHA ready for MySQL 5.6? A: My personal recommendation for MySQL 5.6, based…: Incorrect information in file: ‘./mysql/servers.frm’ ERROR: 1033 Incorrect information in file: ‘./mysql/servers.frm’ Running mysql_install_db under strace, I…
Post: ZFS on Linux and MySQL
May 24, 2013 By 17 Comments
… (30 mirrors + spares + OS partition mirror) and I limited the ARC size to 4GB. I don’t … copy on write filesystem, the snapshots are free, no performance penalty. You can easily run a server …ZFS on Linux is a very interesting solution for MySQL backup servers. All backup solutions have an impact …
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
May 22, 2013 By 8 Comments
These limitations are part of the reason we decided not to merge MySQL 5.6 global transaction ID into MariaDB. In MariaDB… make it use GTID to connect, START SLAVE. There is no need for any special configuration or to restart or otherwise…
Post: Galera Flow Control in Percona XtraDB Cluster for MySQL
May 2, 2013 By 5 Comments
… setting really does no more than to change if the fc_limit is dynamically resized or not. It contains no other magic that… in a master/slave cluster might be: mysql> set global wsrep_provider_options=”gcs.fc_limit=500; gcs.fc_master_slave=YES… reasonable to increase the fc_limit because the only lagging nodes will be the slaves with no writes coming from them. However…
Post: More on MySQL transaction descriptors optimization
April 26, 2013 By Leave a Comment
… (on the left) vs. two-node (on the right) configuration. No surprises here, the general pattern is consistent with what we… optimization in MySQL 5.6 virtually eliminates contention on the mutex protecting the list of transactions, its applicability is quite limited. Namely… –max-requests=0 –percentile=99 –mysql-user=root –mysql-db=sbtest8t1M –mysql-table-engine=INNODB –mysql-socket=/tmp/mysql.sock –oltp-point-selects=1 –oltp…
Post: MySQL 5.6 Compatible Percona Toolkit 2.2 Released
March 25, 2013 By 2 Comments
… pt-mysql-summary have built-in MySQL options No more “pt-stalk — -h db1 -u me”. pt-stalk 2.2 and pt-mysql-summary 2.2 have all the standard MySQL… forever by default, so specify –iterations or –run-time to limit how long they run. There are more changes in addition…
Post: Memory allocators: MySQL performance improvements in Percona Server 5.5.30-30.2
April 15, 2013 By
… and jemalloc allocators. Observations: = MySQL 5.5.30 – throughput of MySQL 5.5.30 with glibc is limited first of all by inefficiency… transaction list causes performance drop = MySQL 5.6.10 – in autocommit mode 5.6.10 has no problem with transaction list scanning… solved in our recent release and such we have almost no difference in results between runs either with glibc or jemalloc
