Apr
14
2015
--

Percona Toolkit 2.2.14 is now available

href="http://www.percona.com/blog/wp-content/uploads/2013/03/Percona_ToolkitLogoVert_RGB.png"> class="alignright wp-image-13951" style="margin: 7px;" src="http://www.percona.com/blog/wp-content/uploads/2013/03/Percona_ToolkitLogoVert_RGB-300x249.png" alt="Percona Toolkit" width="180" height="149" />Percona is pleased to announce the availability of  href="http://www.percona.com/software/percona-toolkit">Percona Toolkit 2.2.14.  Released April 14, 2015. Percona Toolkit is a collection of advanced command-line tools to perform a variety of MySQL server and system tasks that are too difficult or complex for DBAs to perform manually. Percona Toolkit, like all Percona software, is free and open source.

This release is the current GA (Generally Available) stable release in the 2.2 series. It includes multiple bug fixes for pt-table-checksum with better support for Percona XtraDB Cluster, various other fixes, as well as continued preparation for MySQL 5.7 compatibility. Full details are below. Downloads are available  href="http://www.percona.com/downloads/percona-toolkit/2.2.14/">here and from the  href="http://www.percona.com/doc/percona-server/5.5/installation.html">Percona Software Repositories.

New Features:

  • href="http://www.percona.com/doc/percona-toolkit/2.2/pt-slave-find.html">pt-slave-find can now resolve the IP address and show the slave’s hostname. This can be done with the new --resolve-address option.
  • href="http://www.percona.com/doc/percona-toolkit/2.2/pt-table-sync.html">pt-table-sync can now ignore the tables whose names match a specific Perl regex with the new --ignore-tables-regex option.

Bugs Fixed:

  • Fixed bug rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/bugs/925781">925781: Inserting non-BMP characters into a column with utf8 charset would cause the Incorrect string value error when running the href="http://www.percona.com/doc/percona-toolkit/2.2/pt-table-checksum.html">pt-table-checksum.
  • Fixed bug rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/bugs/1368244">1368244: href="http://www.percona.com/doc/percona-toolkit/2.2/pt-online-schema-change.html">pt-online-schema-change --alter-foreign-keys-method=drop-swap` was not atomic and thus it could be interrupted. Fixed by disabling common interrupt signals during the critical drop-rename phase.
  • Fixed bug rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/bugs/1381280">1381280: href="http://www.percona.com/doc/percona-toolkit/2.2/pt-table-checksum.html">pt-table-checksum was failing on BINARY field in Primary Key. Fixed by implementing new --binary-index flag to optionally create checksum table using BLOB data type.
  • Fixed bug rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/bugs/1421405">1421405: Running href="http://www.percona.com/doc/percona-toolkit/2.2/pt-upgrade.html">pt-upgrade against a log with many identical (or similar) queries was producing repeated sections with the same fingerprint.
  • Fixed bug rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/bugs/1402730">1402730: href="http://www.percona.com/doc/percona-toolkit/2.2/pt-duplicate-key-checker.html">pt-duplicate-key-checker was not checking for duplicate keys when --verbose option was set.
  • Fixed bug rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/bugs/1406390">1406390: A race condition was causing href="http://www.percona.com/doc/percona-toolkit/2.2/pt-heartbeat.html">pt-heartbeat to crash with sleep argument error.
  • Fixed bug rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/bugs/1417558">1417558: href="http://www.percona.com/doc/percona-toolkit/2.2/pt-stalk.html">pt-stalk when used along with --collect-strace didn’t write the strace output to the expected destination file.
  • Fixed bug rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/bugs/1421025">1421025: Missing dependency for perl-TermReadKey RPM package was causing toolkit commands to fail when they were run with --ask-pass option.
  • Fixed bug rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/bugs/1421781">1421781: href="http://www.percona.com/doc/percona-toolkit/2.2/pt-upgrade.html">pt-upgrade would fail when log contained SELECT...INTO queries. Fixed by ignoring/skipping those queries.
  • Fixed bug rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/bugs/1425478">1425478: href="http://www.percona.com/doc/percona-toolkit/2.2/pt-stalk.html">pt-stalk was removing non-empty files that were starting with an empty line.
  • Fixed bug rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/bugs/1419098">1419098: Fixed bad formatting in the href="http://www.percona.com/doc/percona-toolkit/2.2/pt-table-checksum.html">pt-table-checksum documentation.

Details of the release can be found in the  href="http://www.percona.com/doc/percona-toolkit/2.2/release_notes.html#v2-2-14-released-2015-04-14">release notes and the  rel="nofollow" href="https://launchpad.net/percona-toolkit/+milestone/2.2.14" rel="nofollow">2.2.14 milestone at Launchpad. Bugs can be reported on the Percona Toolkit rel="nofollow" href="https://bugs.launchpad.net/percona-toolkit/+filebug" rel="nofollow">launchpad bug tracker.

The post rel="nofollow" href="http://www.percona.com/blog/2015/04/14/percona-toolkit-2-2-14-is-now-available/">Percona Toolkit 2.2.14 is now available appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.

Mar
31
2015
--

Percona XtraBackup 2.2.10 for MySQL hot backups is now available (free!)

href="http://www.percona.com/blog/wp-content/uploads/2013/01/Percona_XtraBackup.jpg"> class="alignright size-full wp-image-12668" src="http://www.percona.com/blog/wp-content/uploads/2013/01/Percona_XtraBackup.jpg" alt="Percona XtraBackup for MySQL" width="229" height="87" /> Percona is glad to announce the release of Percona XtraBackup 2.2.10 on March 31, 2015. Downloads are available from our href="http://www.percona.com/downloads/XtraBackup/LATEST/">download site or href="http://www.percona.com/doc/percona-xtrabackup/2.2/installation.html">Percona Software Repositories.

href="http://www.percona.com/software/percona-xtrabackup">Percona XtraBackup enables MySQL backups without blocking user queries, making it ideal for companies with large data sets and mission-critical applications that cannot tolerate long periods of downtime. Offered free as an open source solution, Percona XtraBackup drives down backup costs while providing unique features for MySQL backups.

Bugs Fixed:

  • Decrypting backup with the wrong key would make the backup unusable and unrecoverable. innobackupex doesn’t automatically delete the *.qp and *.xbcrypt files anymore, after href="http://www.percona.com/doc/percona-xtrabackup/2.2/innobackupex/innobackupex_option_reference.html#cmdoption-innobackupex--decrypt">--decrypt and href="http://www.percona.com/doc/percona-xtrabackup/2.2/innobackupex/innobackupex_option_reference.html#cmdoption-innobackupex--decompress">--decompress are used. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1413044" rel="nofollow">#1413044.
  • href="http://www.percona.com/doc/percona-server/5.6/management/changed_page_tracking.html">XtraDB Changed Page Tracking wasn’t working with innobackupex. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1436793" rel="nofollow">#1436793.
  • Fixed Percona XtraBackup assertion caused by dirty pages remaining in the buffer pool after the log was fully applied. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1368846" rel="nofollow">#1368846.
  • Backup will not be prepared and innobackupex will stop with an error if the transaction log file is corrupted and it wasn’t applied to the intended LSN. Previously this was showing only as a warning. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1414221" rel="nofollow">#1414221.
  • New status log-applied is introduced for backup prepared with href="http://www.percona.com/doc/percona-xtrabackup/2.2/innobackupex/innobackupex_option_reference.html#cmdoption-innobackupex--redo-only">--redo-only to avoid making the backup unusable by preparing full or incremental backup without href="http://www.percona.com/doc/percona-xtrabackup/2.2/innobackupex/innobackupex_option_reference.html#cmdoption-innobackupex--redo-only">--redo-only and then applying next incremental on top of it. Incremental backup now can be applied only to backup in log-applied state, but not to full-prepared as it was earlier. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1436790" rel="nofollow">#1436790.

Release notes with all the bugfixes for Percona XtraBackup 2.2.10 are available in our href="http://www.percona.com/doc/percona-xtrabackup/2.2/release-notes/2.2/2.2.10.html">online documentation. Bugs can be reported on the rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+filebug" rel="nofollow">launchpad bug tracker. Percona XtraBackup is an open source, free MySQL hot backup software that performs non-blocking backups for InnoDB and XtraDB databases.

The post rel="nofollow" href="http://www.percona.com/blog/2015/03/31/percona-xtrabackup-2-2-10-is-now-available/">Percona XtraBackup 2.2.10 for MySQL hot backups is now available (free!) appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.

Mar
30
2015
--

Percona XtraDB Cluster 5.5.41-25.11 is now available

href="http://www.percona.com/blog/wp-content/uploads/2013/02/XtraDB-Cluster.jpg"> class="alignright size-full wp-image-12836" src="http://www.percona.com/blog/wp-content/uploads/2013/02/XtraDB-Cluster.jpg" alt="Percona XtraDB Cluster 5.5.41-25.11" width="237" height="82" />Percona is glad to announce the new release of href="http://www.percona.com/software/percona-xtradb-cluster">Percona XtraDB Cluster 5.5 on March 30th 2015. Binaries are available from href="http://www.percona.com/downloads/">downloads area or from our href="http://www.percona.com/doc/percona-xtradb-cluster/5.5/installation.html">software repositories.

Based on Percona Server href="http://www.percona.com/doc/percona-server/5.5/release-notes/Percona-Server-5.5.41-37.0.html">5.5.41-37.0 including all the bug fixes in it, Galera Replicator 2.11, and on Codership wsrep API 25.11, Percona XtraDB Cluster 5.5.41-25.11 is now the current 5.5 General Availability release. All of Percona‘s software is open-source and free, and all the details of the release can be found in the rel="nofollow" href="https://launchpad.net/percona-xtradb-cluster/+milestone/5.5.41-25.11" rel="nofollow">5.5.41-25.11 milestone at Launchpad.

Bugs Fixed:

  • href="http://www.percona.com/doc/percona-xtradb-cluster/5.5/manual/xtrabackup_sst.html#xtrabackup-sst">XtraBackup SST wouldn’t stop when MySQL was SIGKILLed. This would prevent MySQL to initiate a new transfer as port 4444 was already utilized. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1380697">#1380697.
  • garbd was returning incorrect return code, ie. when garbd was already started, return code was 0. Bugs fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1308103">#1308103 and rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1422863">#1422863.
  • wsrep_sst_xtrabackup-v2 script was causing innobackupex to print a false positive stack trace into the log. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1407599">#1407599.
  • MyISAM DDL (CREATE TABLE only) isn’t replicated anymore when href="http://www.percona.com/doc/percona-xtradb-cluster/5.5/wsrep-system-index.html#wsrep_replicate_myisam">wsrep_replicate_myisam is OFF. Note, for older nodes in the cluster, href="http://www.percona.com/doc/percona-xtradb-cluster/5.5/wsrep-system-index.html#wsrep_replicate_myisam">wsrep_replicate_myisam should work since the TOI decision (for MyISAM DDL) is done on origin node. Mixing of non-MyISAM and MyISAM tables in the same DDL statement is not recommended with href="http://www.percona.com/doc/percona-xtradb-cluster/5.5/wsrep-system-index.html#wsrep_replicate_myisam">wsrep_replicate_myisam OFF since if any table in list is MyISAM, the whole DDL statement is not put under TOI (total order isolation). This also doesn’t work if default_storage_engine variable is set to MyISAM (which is not recommended for Percona XtraDB Cluster) and a table is created without the ENGINE option. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1402338">#1402338.
  • Percona XtraDB Cluster now shows a warning in case additional utilities, like pv which may not affect critical path of SST, are not installed. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1248688">#1248688.
  • href="http://www.percona.com/doc/percona-xtradb-cluster/5.5/wsrep-system-index.html#wsrep_causal_reads">wsrep_causal_reads variable was not honored when declared as global. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1361859">#1361859.
  • garbd would not work when cluster address was specified without the port. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1365193">#1365193.
  • garbd was running as root user on Debian. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1392388">#1392388.
  • Errors in garbd init script stop/start functions have been fixed. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1367956">#1367956.
  • If mysqld gets killed during the SST it will leave an unclean data directory behind. This would cause Percona XtraDB Cluster to fail when the server would be started next time because the data directory would be corrupted. This was fixed by resuming the startup in case wsrep-recover failed to recover due to corrupted data directory. The old behavior is still achievable through --exit-on-recover-fail command line parameter to mysqld_safe or exit-on-recover-fail under [mysqld_safe] in my.cnf. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1378578">#1378578.
  • gvwstate.dat file was removed on joiner when href="http://www.percona.com/doc/percona-xtradb-cluster/5.5/manual/xtrabackup_sst.html#xtrabackup-sst">XtraBackup SST method was used. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1388059">#1388059.
  • xtrabackup-v2 SST did not clean the undo log directory. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1394836">#1394836.
  • stderr of SST/Innobackupex is logged to syslog with appropriate tags if sst-syslog is in [sst] or [mysqld_safe] has syslog in my.cnf. This can be overridden by setting the sst-syslog to -1 in [sst]. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1399134">#1399134.
  • clustercheck can now check if the node is PRIMARY or not, to allow for synced nodes which go out of PRIMARY not to take any writes/reads. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1403566">#1403566.
  • Race condition between donor and joiner in Xtrabackup SST Configuration has been fixed. This caused XtraBackup SST to fail when joiner took longer to spawn the second listener for SST. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1405668">#1405668.
  • SST will now fail early if the xtrabackup_checkpoints file is missing on the joiner side. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1405985">#1405985.
  • socat utility was not properly terminated after a timeout. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1409710">#1409710.
  • 10 seconds timeout in href="http://www.percona.com/doc/percona-xtradb-cluster/5.5/manual/xtrabackup_sst.html#xtrabackup-sst">Xtrabackup SST Configuration script was not enough for the joiner to delete existing files before it started the socat receiver on systems with big datadir. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1413879">#1413879.
  • Conflict between href="http://www.percona.com/doc/percona-server/5.6/management/enforce_engine.html#enforce_storage_engine">enforce_storage_engine and href="http://www.percona.com/doc/percona-xtradb-cluster/5.5/wsrep-system-index.html#wsrep_replicate_myisam">wsrep_replicate_myisam for CREATE TABLE has been fixed. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1435482">#1435482.
  • SST processes are now spawned with fork/exec instead of posix_spawn to allow for better cleanup of child processes in event of non-graceful termination (SIGKILL or a crash etc.). Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1382797">#1382797.
  • Variable length arrays in WSREP code were causing debug builds to fail. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1409042">#1409042.
  • Signal handling in mysqld has been fixed for SST processes. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1399175">#1399175.
  • Inserts to a table with autoincrement primary key could result in duplicate key error if another node joined or dropped from the cluster during the insert processing. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1366997">#1366997.

Other bugs fixed: rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1391634">#1391634 and rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1396757">#1396757.

Release notes for Percona XtraDB Cluster href="http://www.percona.com/doc/percona-xtradb-cluster/5.5/release-notes/Percona-XtraDB-Cluster-5.5.41-25.11.html">5.5.41-25.11 are available in our href="http://www.percona.com/doc/percona-xtradb-cluster/5.5/index.html">online documentation along with the href="http://www.percona.com/doc/percona-xtradb-cluster/5.5/installation.html">installation instructions.

Help us improve our software quality by reporting any bugs you encounter using our rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+filebug" rel="nofollow">bug tracking system. As always, thanks for your continued support of Percona!

Please also note that Percona XtraDB Cluster 5.6 series is the latest General Availability series and current GA release is href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/release-notes/Percona-XtraDB-Cluster-5.6.22-25.8.html">5.6.22-25.8.

The post rel="nofollow" href="http://www.percona.com/blog/2015/03/30/percona-xtradb-cluster-5-5-41-25-11-is-now-available/">Percona XtraDB Cluster 5.5.41-25.11 is now available appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.

Mar
09
2015
--

5 free handy tools for monitoring and managing MySQL replication

MySQL Replication is very simple to set up. In this post I’ll discuss its importance and five handy tools for monitoring and managing MySQL replication.

What is MySQL Replication? It’s the process of copying the (real-time events) data from one master instance to another slave instance and maintaining the redundant consistent data in a different machine. This enables a distributed database system that shares the same level of information.

In MySQL the replication works based on the three threads as shown below.

1) I/O thread on the slave server:  To start on receiving replication events, an I/O thread starts on the slave server and connects to the master server.

2) Master connection handler thread:  As a connection handier, master starts a thread whenever a replication slave connects to a master. The master server sends the events from its binary log file to the slave I/O thread, notifying slave about newly written events to its binary log. The slave I/O thread which records them to in the slave’s relay log file.

3) Slave SQL thread:  When it starts, immediately reads the events from the relay log and applies on the Slave DB. Once it finishes the processing of every relay log and if the I/O thread is writing the events to a new relay log file then it deletes the processed one. Suppose if the  I/O thread is writing  the events on a relay log and which is the same file SQL thread is reading then the SQL thread pauses until more events are available in the relay log.

MySQL replication (slave) redundant instances is an excellent method of improving data performance and stability. It ensures the availability of another copy of a database whenever there arises any issues with the master server. One of the other advantages is the report query (select) offloading to a slave server, which is a common practice to reduce the workload of the master DB server as there are multiple servers that are able to respond to the queries. The third advantage is to schedule the backup from the slave server, etc.

All the benefits discussed above are smart and effective only if replication is up and running and the data is in sync with the master.

Let us see the set of very useful tools from Percona Toolkit which help you in monitoring and managing the MySQL replication (Slaves).

href="http://www.percona.com/blog/wp-content/uploads/2015/03/5-free-handy-tools-for-monitoring-and-managing-MySQL-replication.png"> class="alignright size-medium wp-image-29073" src="http://www.percona.com/blog/wp-content/uploads/2015/03/5-free-handy-tools-for-monitoring-and-managing-MySQL-replication-300x300.png" alt="5 free handy tools for monitoring and managing MySQL replication" width="300" height="300" />1) href="http://www.percona.com/doc/percona-toolkit/2.2/pt-heartbeat.html">pt-heartbeat: Tool measures/monitor replication lag on a MySQL in real time. It is important to have a replication monitoring system to confirm that replication is up and running and lag is current.

In typical way of monitoring, we use “SHOW SLAVE STATUS” to find out the information like Slave_IO_Running: Yes, Slave_SQL_Running: Yes and Seconds_Behind_Master: 0 etc, but is not reliable as  Seconds_Behind_Master shows difference between last timestamp read in the binlogs and current time. Many reasons like slow network, long running queries, blocking operations or a 2nd level slaves(Master > slave1> slave2) etc. can produce an irrelevant value for the variable.

So I recommend to use pt-heartbeat, which depends only on the heartbeat record being replicated to slave instead of the above said unreliable method of finding the lag. pt-heartbeat will insert/update a row in the master and the time delay is calculated depending on when the data was inserted and when it became available to read in the slave. It works at any depth in the replication hierarchy. For example, it will reliably report how far a slave lags its original master (master’s master).

Example :

On Master:
[root@Tst1Master ~]#pt-heartbeat --daemonize -D test --update -h<IP address> --create-table
On Slave:
[root@Tst1Slave ~]#pt-heartbeat -D test --monitor --master-server-id 1
0.00s [  0.00s,  0.00s,  0.00s ]
0.00s [  0.00s,  0.00s,  0.00s ]
0.00s [  0.00s,  0.00s,  0.00s ]
0.00s [  0.00s,  0.00s,  0.00s ]

We used to schedule the backup from the slave to avoid the additional load with the master server. In this case it is important to confirm the slave is current with the master to ascertain the backup is having the recent data. Here is a simple script you can use to verify the replication status on a periodical basis(cron) and to know the status just before the backup scheduled.

#!/bin/bash
#     <300 - [Good]
#     300> <600 - [Warning]
#     > 600 - [Critical]
MAIL_FROM="root@`hostname`"
MAIL_TO="mailid@mail.com"
Warningthreshold=300
Criticalthreshold=600
backup=$1
CMD=$(/root/bin/pt-heartbeat -D test --master-server-id 1 --check | cut -d. -f1)
# Pass the parameter "test.sh backup" to denote the call is from the backup script.
if [ $CMD -lt $Warningthreshold ]
then
MESSAGE=`date +'%m:%d:%Y %H:%M:%S'`" [Good] current delay: "$CMD;
elif [ $CMD -gt $Warningthreshold ] && [ $CMD -lt $Criticalthreshold ]
then
MESSAGE=`date +'%m:%d:%Y %H:%M:%S'`" [Warning] current delay: "$CMD;
elif [ $CMD -gt $Criticalthreshold ]
then
MESSAGE=`date +'%m:%d:%Y %H:%M:%S'`" [Critical] current delay: $CMD Check the replication"
else
MESSAGE=`date +'%m:%d:%Y %H:%M:%S'`" [Error] Replication status check failed need to investigate."
fi
#No arguments supplied"
if [ -z "$1" ] && [ $CMD -gt $Warningthreshold ]
then
(echo "Subject: Replication status on `hostname`";
echo "Replication status : "
echo $MESSAGE
)  | /usr/sbin/sendmail -O NoRecipientAction=add-to -f${MAIL_FROM} ${MAIL_TO}
elif [ $# -eq 1 ]
then
(echo "Subject: Replication status check prior to backup on `hostname`";
echo "Replication status prior to backup:"
echo $MESSAGE
)  | /usr/sbin/sendmail -O NoRecipientAction=add-to -f${MAIL_FROM} ${MAIL_TO}
fi

2) href="http://www.percona.com/doc/percona-toolkit/2.2/pt-slave-find.html">pt-slave-find: Finds and prints replication hierarchy of the slaves – shows you the topology and replication hierarchy of your MySQL replication instances.

Example :

[root@Tst1Master ~]# ./pt-slave-find --host=192.168.56.10
192.168.56.10
Version         5.6.22-72.0-log
Server ID       1
Uptime          42:09 (started 2015-03-03T01:40:42)
Replication     Is not a slave, has 1 slaves connected, is not read_only
Filters
Binary logging  STATEMENT
Slave status
Slave mode      STRICT
Auto-increment  increment 1, offset 1
InnoDB version  5.6.22-72.0
+- 192.168.56.11
   Version         5.6.22-72.0
   Server ID       2
   Uptime          41:48 (started 2015-03-03T01:41:03)
   Replication     Is a slave, has 0 slaves connected, is not read_only
   Filters
   Binary logging  STATEMENT
   Slave status    0 seconds behind, running, no errors
   Slave mode      STRICT
   Auto-increment  increment 1, offset 1
   InnoDB version  5.6.22-72.0

[root@Tst1Master ~]# ./pt-slave-find --host=192.168.56.10 --report-format=hostname
192.168.56.10
+- 192.168.56.11

3) href="http://www.percona.com/doc/percona-toolkit/2.2/pt-slave-restart.html">pt-slave-restart: Watches the MySQL replication slaves for any error and tries to restart the replication.

The tool is very useful for skipping statements  class="Apple-converted-space">that cause errors class="Apple-converted-space"> and continuing replication. If you use this carelessly, the slave will be having the inconsistent data. class="Apple-converted-space"> However  when you use the tool, I recommended you to confirm the consistency of data between master and slave with help of pt-table-checksum.

Example : Restart the slave for error-numbers=1062 (Duplicate entry ‘1’ for key ‘PRIMARY’)

#pt-slave-restart --socket=/var/lib/mysql/custom-feeds/mysql.sock --ask-pass --error-numbers=1062

4) href="http://www.percona.com/doc/percona-toolkit/2.2/pt-table-checksum.html">pt-table-checksum: Performs an online replication consistency check by executing href="http://www.percona.com/blog/2014/10/13/how-to-avoid-hash-collisions-when-using-mysqls-crc32-function/">checksum queries on the master, which produces different results on replicas that are inconsistent with the master.

Example :

[root@Tst1Master ~]# ./pt-table-checksum -dD
            TS ERRORS  DIFFS     ROWS  CHUNKS SKIPPED    TIME TABLE
03-03T02:34:44      0      1        2       1       0   0.011 d.t

Note: It  is important to run the pt-table-checksum tool regardless of whether or not you’ve ever skipped an event with pt-slave-restart to make sure we are having the identical data on the slave side.

5) href="http://www.percona.com/doc/percona-toolkit/2.2/pt-table-sync.html">pt-table-sync: Sync the slave with their master (synchronizes data efficiently between MySQL tables.)

Example :

[root@Tst1Slave ~]# ./pt-table-sync -dD --print  --sync-to-master 192.168.56.11
REPLACE INTO `d`.`t`(`id`, `data`) VALUES ('1', 'Test1') /*percona-toolkit src_db:d src_tbl:t src_dsn:P=3306,h=192.168.56.10 dst_db:d dst_tbl:t dst_dsn:h=192.168.56.11 lock:1 transaction:1 changing_src:1 replicate:0 bidirectional:0 pid:6435 user:root host:Tst1Slave.mysql*/;
REPLACE INTO `d`.`t`(`id`, `data`) VALUES ('2', 'Test2') /*percona-toolkit src_db:d src_tbl:t src_dsn:P=3306,h=192.168.56.10 dst_db:d dst_tbl:t dst_dsn:h=192.168.56.11 lock:1 transaction:1 changing_src:1 replicate:0 bidirectional:0 pid:6435 user:root host:Tst1Slave.mysql*/;
[root@Tst1Slave ~]#

[root@Tst1Slave ~]# ./pt-table-sync -dD  --verbose  --execute  --sync-to-master 192.168.56.11
# Syncing h=192.168.56.11
# DELETE REPLACE INSERT UPDATE ALGORITHM START    END      EXIT DATABASE.TABLE
#      0       2      0      0 Chunk     03:38:09 03:38:09 2    d.t

We have successfully sync the tables so let us try the href="http://www.percona.com/blog/2014/10/13/how-to-avoid-hash-collisions-when-using-mysqls-crc32-function/">checksum again and confirm the table is in sync.

[root@Tst1Master ~]# ./pt-table-checksum -dD
            TS ERRORS  DIFFS     ROWS  CHUNKS SKIPPED    TIME TABLE
03-03T03:03:40      0      0        2       1       0   0.111 d.t

The aforesaid are the simple examples and based on your needs, you can choose the tools, options or modify the scripts. I also recommend that you to go through the documentations for more details on each tools.

The post rel="nofollow" href="http://www.percona.com/blog/2015/03/09/5-free-handy-tools-for-monitoring-and-managing-mysql-replication/">5 free handy tools for monitoring and managing MySQL replication appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.

Mar
05
2015
--

Percona XtraDB Cluster 5.6.22-25.8 is now available

href="http://www.percona.com/blog/wp-content/uploads/2013/02/XtraDB-Cluster.jpg"> class="alignright size-full wp-image-12836" src="http://www.percona.com/blog/wp-content/uploads/2013/02/XtraDB-Cluster.jpg" alt="Percona XtraDB Cluster 5.6.22-25.8" width="237" height="82" />Percona is glad to announce the new release of href="http://www.percona.com/software/percona-xtradb-cluster">Percona XtraDB Cluster 5.6 on March 5th 2015. Binaries are available from href="http://www.percona.com/downloads/">downloads area or from our href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/installation.html">software repositories.

Based on Percona Server href="http://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.22-72.0.html">5.6.22-72.0 including all the bug fixes in it, rel="nofollow" href="https://github.com/codership/galera/issues?q=milestone%3A25.3.9" rel="nofollow">Galera Replicator 3.9, and on Codership wsrep API 25.8, Percona XtraDB Cluster 5.6.22-25.8 is now the current General Availability release. All of Percona’s software is open-source and free, and all the details of the release can be found in the rel="nofollow" href="https://launchpad.net/percona-xtradb-cluster/+milestone/5.6.22-25.8" rel="nofollow">5.6.22-25.8 milestone at Launchpad.

Bugs Fixed:

  • href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/manual/xtrabackup_sst.html#xtrabackup-sst">XtraBackup SST wouldn’t stop when MySQL was SIGKILLed. This would prevent MySQL to initiate a new transfer as port 4444 was already utilized. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1380697" rel="nofollow">#1380697.
  • wsrep_sst_xtrabackup-v2 script was causing innobackupex to print a false positive stack trace into the log. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1407599" rel="nofollow">#1407599.
  • MyISAM DDL (CREATE/DROP) isn’t replicated any more when href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-system-index.html#wsrep_replicate_myisam">wsrep_replicate_myisam is OFF. Note, for older nodes in the cluster, href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-system-index.html#wsrep_replicate_myisam">wsrep_replicate_myisam should work since the TOI decision (for MyISAM DDL) is done on origin node. Mixing of non-MyISAM and MyISAM tables in the same DDL statement is not recommended with href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-system-index.html#wsrep_replicate_myisam">wsrep_replicate_myisam OFF since if any table in list is MyISAM, the whole DDL statement is not put under TOI (total order isolation), hence not replicated. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1402338" rel="nofollow">#1402338.
  • href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-provider-index.html#gcache.mem_size">gcache.mem_size option has been deprecated. A warning will now be generated if the variable has value different than 0. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1392408" rel="nofollow">#1392408.
  • stderr of SST/Innobackupex is logged to syslog with appropriate tags if sst-syslog is in [sst] or [mysqld_safe] has syslog in my.cnf. This can be overriden by setting the sst-syslog to -1 in [sst]. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1399134" rel="nofollow">#1399134.
  • clustercheck can now check if the node is PRIMARY or not, to allow for synced nodes which go out of PRIMARY not to take any writes/reads. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1403566" rel="nofollow">#1403566.
  • SST will now fail early if the xtrabackup_checkpoints is missing on the joiner side. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1405985" rel="nofollow">#1405985.
  • socat utility was not properly terminated after a timeout. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1409710" rel="nofollow">#1409710.
  • When started (without bootstrap), the node would hang if it couldn’t find a primary node. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1413258" rel="nofollow">#1413258.
  • 10 seconds timeout in Xtrabackup SST script was not enough for the joiner to delete existing files before it started the socat receiver on systems with big datadir. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1413879" rel="nofollow">#1413879.
  • Non booststrap node could crash while attempting to perform table%cache operations with the BF applier failed to open_and_lock_tables warning. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1414635" rel="nofollow">#1414635.
  • Percona XtraDB Cluster 5.6 would crash on ALTER TABLE / CREATE INDEX with Failing assertion: table->n_rec_locks == 0 error. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1282707" rel="nofollow">#1282707.
  • Variable length arrays in WSREP code were causing debug builds (-DWITH_DEBUG=ON) to fail. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1409042" rel="nofollow">#1409042.
  • Race condition between donor and joiner in Xtrabackup SST configuration has been fixed. This caused XtraBackup SST to fail when joiner took longer to spawn the second listener for SST. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1405668" rel="nofollow">#1405668.
  • Signal handling in mysqld has been fixed for SST processes. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1399175" rel="nofollow">#1399175.
  • SST processes are now spawned with fork/exec instead of posix_spawn to allow for better cleanup of child processes in event of non-graceful termination (SIGKILL or a crash etc.). Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1382797" rel="nofollow">#1382797.
  • href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-status-index.html#wsrep_local_cached_downto">wsrep_local_cached_downto would underflow when the node on which it is queried had no writesets in gcache. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1262179" rel="nofollow">#1262179.
  • A typo in href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-system-index.html#wsrep_provider_options">wsrep_provider_options could cause an unhandled exception. Bug fixed rel="nofollow" href="https://github.com/codership/galera/issues/215" rel="nofollow">#215.
  • Interrupted IST would result in HA_ERR_KEY_NOT_FOUND error in subsequent IST. Bug fixed rel="nofollow" href="https://github.com/codership/galera/issues/210" rel="nofollow">#210.

Other bugs fixed: rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1275814" rel="nofollow">#1275814.

Known Issue:

  • For those affected by crashes on donor during SST due to backup locks ( rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1401133" rel="nofollow">#1401133), please add the following to your my.cnf configuration file:[sst] /> inno-backup-opts='--no-backup-locks' />

    option as a workaround to force FLUSH TABLES WITH READ LOCK (NOTE: This workaround will is available only if you’re using Percona XtraBackup 2.2.9 or newer.). Or, as an alternative you can set your environment variable FORCE_FTWRL to 1 (for passing environment variables, see description of bug rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1381492" rel="nofollow">#1381492 in the previous release notes).

Release notes for Percona XtraDB Cluster href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/release-notes/Percona-XtraDB-Cluster-5.6.22-25.8.html">5.6.22-25.8 are available in our href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/index.html">online documentation along with the href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/installation.html">installation and href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/upgrading_guide_55_56.html">upgrade instructions.

Percona XtraDB Cluster code hosting has been moved to Github. The Bazaar branches will not be updated further.

Help us improve our software quality by reporting any bugs you encounter using our rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+filebug" rel="nofollow">bug tracking system. As always, thanks for your continued support of Percona!

The post rel="nofollow" href="http://www.percona.com/blog/2015/03/05/percona-xtradb-cluster-5-6-22-25-8-now-available/">Percona XtraDB Cluster 5.6.22-25.8 is now available appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.

Mar
04
2015
--

Percona Server 5.6.23-72.1 is now available

href="http://www.percona.com/blog/wp-content/uploads/2014/05/percona_server.jpeg"> class="alignright size-thumbnail wp-image-22759" src="http://www.percona.com/blog/wp-content/uploads/2014/05/percona_server-150x150.jpeg" alt="Percona Server" width="150" height="150" />Percona is glad to announce the release of href="http://www.percona.com/software/percona-server">Percona Server 5.6.23-72.1 on March 4, 2015. Download the latest version from the title="Percona Server 5.6" href="http://www.percona.com/downloads/Percona-Server-5.6/Percona-Server-5.6.23-72.1/" >Percona web site or from the Percona href="http://www.percona.com/doc/percona-server/5.6/installation.html#using-percona-software-repositories">Software Repositories.

Based on MySQL rel="nofollow" href="http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-23.html" rel="nofollow">5.6.23, including all the bug fixes in it, Percona Server 5.6.23-72.1 is the current GA release in the Percona Server 5.6 series. Percona Server is open-source and free – and this is the latest release of our enhanced, drop-in replacement for MySQL. Complete details of this release can be found in the rel="nofollow" href="https://launchpad.net/percona-server/+milestone/5.6.23-72.1" rel="nofollow">5.6.23-72.1 milestone on Launchpad.

New Features:

  • TokuDB storage engine package has been updated to version rel="nofollow" rel="nofollow" href="http://docs.tokutek.com/tokudb/tokudb-release-notes.html#tokudb-version-7-x">7.5.6.

Bugs Fixed:

  • RPM pre-install script assumed that the PID file was always located in the datadir. If it was not, during installation, wrong assumption could be made if the server was running or not. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1201896">#1201896.
  • SHOW GRANTS displayed only the privileges granted explicitly to the named account. Other effectively available privileges were not displayed. Fixed by implementing href="http://www.percona.com/doc/percona-server/5.6/management/extended_show_grants.html">Extended SHOW GRANTS feature. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1354988">#1354988 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=53645">#53645).
  • InnoDB lock monitor output was printed even if it was not requested. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1418996">#1418996.
  • The stored procedure key was made consistent with other keys in the href="http://www.percona.com/doc/percona-server/5.6/diagnostics/slow_extended.html">Slow Query Log by replacing space with an underscore. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1419230">#1419230.
  • Some --big-test MTR tests were failing for Percona Server because they weren’t updated. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1419827">#1419827.

Other bugs fixed: rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1408232">#1408232, and rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1420303">#1420303.

Release notes for Percona Server 5.6.23-72.1 are available in the  href="http://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.23-72.1.html">online documentation. Please report any bugs on the rel="nofollow" href="https://bugs.launchpad.net/percona-server/+filebug" rel="nofollow">launchpad bug tracker

The post rel="nofollow" href="http://www.percona.com/blog/2015/03/04/percona-server-5-6-23-72-1-now-available/">Percona Server 5.6.23-72.1 is now available appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.

Mar
04
2015
--

Percona Server 5.5.42-37.1 is now available

href="http://www.percona.com/blog/wp-content/uploads/2014/05/percona_server.jpeg"> class="alignright size-thumbnail wp-image-22759" src="http://www.percona.com/blog/wp-content/uploads/2014/05/percona_server-150x150.jpeg" alt="Percona Server" width="150" height="150" /> /> Percona is glad to announce the release of href="http://www.percona.com/software/percona-server">Percona Server 5.5.42-37.1 on March 4, 2015. Based on rel="nofollow" href="http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-42.html" rel="nofollow">MySQL 5.5.42 href="http://www.percona.com/blog/wp-content/uploads/2014/05/percona_server.jpeg">, including all the bug fixes in it, Percona Server 5.5.42-37.1 is now the current stable release in the 5.5 series.

Percona Server is open-source and free. Details of the release can be found in the rel="nofollow" href="https://launchpad.net/percona-server/+milestone/5.5.42-37.1" rel="nofollow">5.5.42-37.1 milestone on Launchpad. Downloads are available href="http://www.percona.com/downloads/">here and from the href="http://www.percona.com/doc/percona-server/5.5/installation.html">Percona Software Repositories.

Bugs Fixed:

  • RPM pre-install script assumed that the PID file was always located in the datadir. If it was not, during installation, wrong assumption could be made if the server was running or not. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1201896">#1201896.
  • SHOW GRANTS displayed only the privileges granted explicitly to the named account. Other effectively available privileges were not displayed. Fixed by implementing href="http://www.percona.com/doc/percona-server/5.5/management/extended_show_grants.html#extended-show-grants">Extended SHOW GRANTS feature. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1354988">#1354988 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=53645">#53645).
  • InnoDB lock monitor output was printed even if it was not requested. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1418996">#1418996.
  • The stored procedure key was made consistent with other keys in the href="http://www.percona.com/doc/percona-server/5.5/diagnostics/slow_extended_55.html#slow-extended-55">Slow Query Log by replacing space with an underscore. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1419230">#1419230.

Other bugs fixed: rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1408232">#1408232, rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1415843">#1415843 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=75642">#75642), bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1407941">#1407941, and bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1424568">#1424568 (upstream rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/75868">#75868).

(Please also note that Percona Server 5.6 series is the latest General Availability series and current GA release is href="http://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.23-72.1.html">5.6.23-72.1.)

Release notes for Percona Server 5.5.42-37.1 are available in our href="http://www.percona.com/doc/percona-server/5.5/release-notes/Percona-Server-5.5.42-37.1.html">online documentation. Bugs can be reported on the rel="nofollow" href="https://bugs.launchpad.net/percona-server/+filebug" rel="nofollow">launchpad bug tracker.

The post rel="nofollow" href="http://www.percona.com/blog/2015/03/04/percona-server-5-5-42-37-1-now-available/">Percona Server 5.5.42-37.1 is now available appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.

Feb
17
2015
--

Percona XtraBackup 2.2.9 is now available

href="http://www.percona.com/blog/wp-content/uploads/2013/01/Percona_XtraBackup.jpg"> class="alignright size-full wp-image-12668" src="http://www.percona.com/blog/wp-content/uploads/2013/01/Percona_XtraBackup.jpg" alt="Percona XtraBackup for MySQL" width="229" height="87" /> Percona is glad to announce the release of Percona XtraBackup 2.2.9 on February 17, 2015. Downloads are available from our href="http://www.percona.com/downloads/XtraBackup/LATEST/">download site or href="http://www.percona.com/doc/percona-xtrabackup/2.2/installation.html">Percona Software Repositories.

href="http://www.percona.com/software/percona-xtrabackup">Percona XtraBackup enables MySQL backups without blocking user queries, making it ideal for companies with large data sets and mission-critical applications that cannot tolerate long periods of downtime. Offered free as an open source solution, Percona XtraBackup drives down backup costs while providing unique features for MySQL backups.

Bugs Fixed:

  • Percona XtraBackup was vulnerable to MITM attack which could allow exfiltration of MySQL configuration information via --version-check option. This vulnerability was logged as rel="nofollow" rel="nofollow" href="http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=2015-1027">CVE 2015-1027. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1408375">#1408375.
  • xtrabackup_galera_info file isn’t overwritten during the Galera auto-recovery. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1418584">#1418584.
  • Percona XtraBackup man pages are now included with binary packages. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1156209">#1156209.
  • Percona XtraBackup now sets the maximum supported session value for lock_wait_timeout variable to prevent unnecessary timeouts when the global value is changed from the default. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1410339">#1410339.
  • New option --backup-locks, enabled by default, has been implemented to control if href="http://www.percona.com/doc/percona-server/5.6/management/backup_locks.html">backup locks will be used even if they are supported by the server. To disable backup locks innobackupex should be run with innobackupex --no-backup-locks option. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1418820">#1418820.

Release notes with all the bugfixes for Percona XtraBackup 2.2.9 are available in our href="http://www.percona.com/doc/percona-xtrabackup/2.2/release-notes/2.2/2.2.9.html">online documentation. Bugs can be reported on the rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+filebug" rel="nofollow">launchpad bug tracker. Percona XtraBackup is an open source, free MySQL hot backup software that performs non-blocking backups for InnoDB and XtraDB databases.

The post rel="nofollow" href="http://www.percona.com/blog/2015/02/17/percona-xtrabackup-2-2-9-now-available/">Percona XtraBackup 2.2.9 is now available appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.

Feb
06
2015
--

Percona Server 5.6.22-72.0 is now available

href="http://www.percona.com/blog/wp-content/uploads/2014/05/percona_server.jpeg"> class="alignright size-thumbnail wp-image-22759" src="http://www.percona.com/blog/wp-content/uploads/2014/05/percona_server-150x150.jpeg" alt="Percona Server" width="150" height="150" />Percona is glad to announce the release of href="http://www.percona.com/software/percona-server">Percona Server 5.6.22-72.0 on February 6, 2015. Download the latest version from the title="Percona Server 5.6" href="http://www.percona.com/downloads/Percona-Server-5.6/Percona-Server-5.6.22-72.0/" >Percona web site or from the Percona href="http://www.percona.com/doc/percona-server/5.6/installation.html#using-percona-software-repositories">Software Repositories.

Based on MySQL rel="nofollow" href="http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-22.html" rel="nofollow">5.6.22, including all the bug fixes in it, Percona Server 5.6.22-72.0 is the current GA release in the Percona Server 5.6 series. Percona Server is open-source and free – and this is the latest release of our enhanced, drop-in replacement for MySQL. Complete details of this release can be found in the rel="nofollow" href="https://launchpad.net/percona-server/+milestone/5.6.22-72.0" rel="nofollow">5.6.22-72.0 milestone on Launchpad.

New Features:

  • Percona Server is now able to log the query’s response times into href="http://www.percona.com/doc/percona-server/5.6/diagnostics/response_time_distribution.html#rtd-rw-split">separate READ and WRITE INFORMATION_SCHEMA tables. Two new INFORMATION_SCHEMA tables href="http://www.percona.com/doc/percona-server/5.6/diagnostics/response_time_distribution.html#QUERY_RESPONSE_TIME_READ">QUERY_RESPONSE_TIME_READ and href="http://www.percona.com/doc/percona-server/5.6/diagnostics/response_time_distribution.html#QUERY_RESPONSE_TIME_WRITE">QUERY_RESPONSE_TIME_WRITE have been implemented for READ and WRITE queries correspondingly.
  • Percona Server now supports href="http://www.percona.com/doc/percona-server/5.6/flexibility/online_gtid_deployment.html#online-gtid-deployment">Online GTID deployment. This enables GTID to be deployed on existing replication setups without making the master read-only and stopping all the slaves. This feature was ported from the Facebook branch.
  • New ps_tokudb_admin script has been implemented to make the TokuDB storage engine href="http://www.percona.com/doc/percona-server/5.6/tokudb/tokudb_installation.html#tokudb-quick-install">installation easier.

Bugs Fixed:

  • SET STATEMENT ... FOR would crash the server if it could not execute the due to: 1) if the was Read-Write in a Read-Only transaction (bug rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1387951">#1387951), 2) if the needed to re-open an already open temporary table and would fail to do so (bug rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1412423">#1412423), 3) if the needed to commit implicitly the ongoing transaction and the implicit commit would fail (bug rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1418049">#1418049).
  • TokuDB storage engine would fail to load after the upgrade on CentOS 5 and 6. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1413956">#1413956.
  • Fixed a potential low-probability crash in XtraDB linear read-ahead code. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1417953">#1417953.
  • Setting the href="http://www.percona.com/doc/percona-server/5.6/management/statement_timeout.html#max_statement_time">max_statement_time per query had no effect. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1376934">#1376934.

Other bugs fixed: rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1407941">#1407941, and rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1415843">#1415843 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=75642">#75642)

Release notes for Percona Server 5.6.22-72.0 are available in the  href="http://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.22-72.0.html">online documentation. Please report any bugs on the rel="nofollow" href="https://bugs.launchpad.net/percona-server/+filebug" rel="nofollow">launchpad bug tracker

The post rel="nofollow" href="http://www.percona.com/blog/2015/02/06/percona-server-5-6-22-72-0-now-available/">Percona Server 5.6.22-72.0 is now available appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.

Jan
26
2015
--

Percona Toolkit 2.2.13 is now available

href="http://www.percona.com/blog/wp-content/uploads/2013/03/Percona_ToolkitLogoVert_RGB.png"> class="alignright wp-image-13951" style="margin: 7px;" src="http://www.percona.com/blog/wp-content/uploads/2013/03/Percona_ToolkitLogoVert_RGB-300x249.png" alt="Percona Toolkit" width="180" height="149" />Percona is pleased to announce the availability of  href="http://www.percona.com/software/percona-toolkit">Percona Toolkit 2.2.13.  Released January 26, 2015. Percona Toolkit is a collection of advanced command-line tools to perform a variety of MySQL server and system tasks that are too difficult or complex for DBAs to perform manually. Percona Toolkit, like all Percona software, is free and open source.

This release is the current GA (Generally Available) stable release in the 2.2 series. It includes multiple bug fixes for pt-table-checksum with better support for Percona XtraDB Cluster, various other fixes, as well as continued preparation for MySQL 5.7 compatibility. Full details are below. Downloads are available  href="http://www.percona.com/downloads/percona-toolkit/2.2.13/">here and from the  href="http://www.percona.com/doc/percona-server/5.5/installation.html">Percona Software Repositories.

New Features:

  • href="http://www.percona.com/doc/percona-toolkit/2.2/pt-kill.html">pt-kill now supports new --query-id option. This option can be used to print a query fingerprint hash after killing a query to enable the cross-referencing with the href="http://www.percona.com/doc/percona-toolkit/2.2/pt-query-digest.html">pt-query-digest output. This option can be used along with --print option as well.

Bugs Fixed:

  • Fixed bug rel="nofollow" href="https://bugs.launchpad.net/bugs/1408375" rel="nofollow">1408375: Percona Toolkit was vulnerable to MITM attack which could allow exfiltration of MySQL configuration information via --version-check option. This vulnerability was logged as rel="nofollow" href="http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=2015-1027" rel="nofollow">CVE 2015-1027
  • Fixed bug rel="nofollow" href="https://bugs.launchpad.net/bugs/1019479" rel="nofollow">1019479: href="http://www.percona.com/doc/percona-toolkit/2.2/pt-table-checksum.html">pt-table-checksum now works with ONLY_FULL_GROUP_BY SQL mode.
  • Fixed bug rel="nofollow" href="https://bugs.launchpad.net/bugs/1394934" rel="nofollow">1394934: running pt-table-checksum in debug mode would cause an error.
  • Fixed bug rel="nofollow" href="https://bugs.launchpad.net/bugs/1396868" rel="nofollow">1396868: regression introduced in Percona Toolkit 2.2.12 caused href="http://www.percona.com/doc/percona-toolkit/2.2/pt-online-schema-change.html">pt-online-schema-change not to honor --ask-pass option.
  • Fixed bug rel="nofollow" href="https://bugs.launchpad.net/bugs/1399789" rel="nofollow">1399789: pt-table-checksum would fail to find Percona XtraDB Cluster nodes when variable href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-system-index.html#wsrep_node_incoming_address">wsrep_node_incoming_address was set to AUTO.
  • Fixed bug rel="nofollow" href="https://bugs.launchpad.net/bugs/1321297" rel="nofollow">1321297: pt-table-checksum was reporting differences on timestamp columns with replication from 5.5 to 5.6 server version, although the data was identical.
  • Fixed bug rel="nofollow" href="https://bugs.launchpad.net/bugs/1388870" rel="nofollow">1388870: pt-table-checksum was showing differences if the master and slave were in different time zone.
  • Fixed bug rel="nofollow" href="https://bugs.launchpad.net/bugs/1402668" rel="nofollow">1402668: pt-mysql-summary would exit if Percona XtraDB Cluster was in Donor/Desynced state.
  • Fixed bug rel="nofollow" href="https://bugs.launchpad.net/bugs/1266869" rel="nofollow">1266869: href="http://www.percona.com/doc/percona-toolkit/2.2/pt-stalk.html">pt-stalk would fail to start if $HOME environment variable was not set.

Details of the release can be found in the  href="http://www.percona.com/doc/percona-toolkit/2.2/release_notes.html#v2-2-13-released-2015-01-26">release notes and the  rel="nofollow" href="https://launchpad.net/percona-toolkit/+milestone/2.2.13" rel="nofollow">2.2.13 milestone at Launchpad. Bugs can be reported on the Percona Toolkit rel="nofollow" href="https://bugs.launchpad.net/percona-toolkit/+filebug" rel="nofollow">launchpad bug tracker.

The post rel="nofollow" href="http://www.percona.com/blog/2015/01/26/percona-toolkit-2-2-13-now-available/">Percona Toolkit 2.2.13 is now available appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.