Dec
10
2014
--

Percona XtraBackup 2.2.7 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.7 on December 10, 2014. 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:

  • Non-default value for href="http://www.percona.com/doc/percona-server/5.6/scalability/innodb_io.html#innodb_log_block_size">innodb_log_block_size variable would cause assertion when preparing the backup. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1391216">#1391216.
  • When Percona XtraBackup would run FLUSH ENGINE LOGS during the backup process on GTID master, command was recorded to the slave’s binary log as well, which lead to inconsistency between master and slave. Fixed by adding the NO_WRITE_TO_BINLOG clause to FLUSH ENGINE LOGS to avoid interfering with binary log and inconsistency with coordinates. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1394632">#1394632.
  • Exporting tables was inefficient when backup contained a large (and unrelated) change buffer. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1366065">#1366065 (Davi Arnaut).
  • innobackupex was printing the GTID even if the GTID mode was disabled which could cause confusion since it wasn’t incrementing. Now it prints only GTID when GITD mode is enabled and when GTID mode is disabled it prints only filename and position. innobackupex still prints GTID, filename and positions if MariaDB server is being backed up. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1391041">#1391041.

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

Release notes with all the bugfixes for Percona XtraBackup 2.2.7 are available in our href="http://www.percona.com/doc/percona-xtrabackup/2.2/release-notes/2.2/2.2.7.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/2014/12/10/percona-xtrabackup-2-2-7-now-available/">Percona XtraBackup 2.2.7 is now available appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.

Nov
25
2014
--

Percona XtraDB Cluster 5.6.21-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.21-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 Novmeber 25th 2014. 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. We’re also happy to announce that Ubuntu 14.10 and CentOS 7 users can download, install, and upgrade Percona XtraDB Cluster 5.6 from Percona’s software repositories.

Based on Percona Server href="http://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.21-70.1.html">5.6.21-70.1 including all the bug fixes in it, rel="nofollow" href="https://github.com/codership/galera/issues?milestone=1&page=1&state=closed" rel="nofollow">Galera Replicator 3.8, and on rel="nofollow" href="https://launchpad.net/wsrep-group/+milestone/5.6.21-25.7" rel="nofollow">Codership wsrep API 25.7, Percona XtraDB Cluster 5.6.21-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.21-25.8" rel="nofollow">5.6.21-25.8 milestone at Launchpad.

New Features:

  • Galera 3.8 introduces auto-eviction for nodes in the cluster experiencing network issues like packet loss. It is off by default and is turned on with href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-provider-index.html#evs.auto_evict">evs.auto_evict option. This feature requires EVS protocol version ( href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-provider-index.html#evs.version">evs.version) 1. During the EVS protocol upgrade all membership changes are communicated over EVS protocol version 0 to preserve backwards compatibility, protocol is upgraded to the highest commonly supported version when forming a new group so if there exist a single node with older version in the group, the group protocol version remains as 0 and auto-eviction is not functional. ( rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1274192">#1274192).
  • Percona XtraDB Cluster now supports backup locks in XtraBackup SST (in the default xtrabackup-v2 href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-system-index.html#wsrep_sst_method">wsrep_sst_method). href="http://www.percona.com/doc/percona-server/5.6/management/backup_locks.html">Backup locks are used in lieu of FLUSH TABLES WITH READ LOCK on the donor during SST. This should allow for minimal disruption of existing and incoming queries, even under high load. Thus, this should allow for even faster SST and node being in ‘donor/desynced’ state. This also introduces following constraints: Percona XtraDB Cluster 5.6.21 requires Percona XtraBackup 2.2.5 or higher; An older (< 5.6.21) joiner cannot SST from a newer (>= 5.6.21) donor. This is enforced through SST versioning (sent from joiner to donor during SST) and logged to error log explicitly. ( rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1390552">#1390552).
  • Percona XtraDB Cluster is now shipped with Galera MTR test suite.

Bugs Fixed:

  • 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.
  • mysqldump SST can now use username/password from href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-system-index.html#wsrep_sst_auth">wsrep_sst_auth under group of [sst] in my.cnf in order not to display the credentials in the error log. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1293798">#1293798.
  • Normal shutdown under load would cause server to remain hanging because replayer failed to finish. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1358701">#1358701.
  • href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/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.
  • 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.
  • Percona XtraDB Cluster now reads environment variables for mysqld from following files (if present): /etc/default/mysql in Debian/Ubuntu; /etc/sysconfig/mysql in CentOS 6 or lower; /etc/sysconfig/mysql in CentOS 7 with mysql.service; /etc/sysconfig/XYZ in CentOS 7 with mysql@XYZ.service (/etc/sysconfig/bootstrap is supplied by default). Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1381492">#1381492.
  • gvwstate.dat file was removed on joiner when href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/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.
  • Percona XtraDB Cluster now detects older joiners which don’t have the backup lock support. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1390552">#1390552.
  • Inserts to a table with auto-increment 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.
  • TOI now skips replication if all tables are temporary. Bugs fixed rel="nofollow" rel="nofollow" href="https://github.com/codership/mysql-wsrep/issues/11">#11 and rel="nofollow" rel="nofollow" href="https://github.com/codership/mysql-wsrep/issues/13">#13.
  • Bootstrapping a node tried to resolve gcomm address list specified in href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-system-index.html#wsrep_cluster_address">wsrep-cluster-address. Bug fixed rel="nofollow" rel="nofollow" href="https://github.com/codership/galera/issues/88">#88.
  • In case stored procedure containing a non-InnoDB statement (MyISAM) performed autocommit, that commit would be entered two times: at statement end and next time at stored procedure end. Bug fixed rel="nofollow" rel="nofollow" href="https://github.com/codership/mysql-wsrep/issues/2">#2.
  • Two appliers conflicting with local transaction and resulting later in (acceptable) BF-BF lock conflict, would cause cluster to hang when the other BF thread would not grant the lock back after its local transaction got aborted. Bug fixed rel="nofollow" rel="nofollow" href="https://github.com/codership/mysql-wsrep/issues/7">#7.

Other bugs fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1378138">#1378138, rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1377226">#1377226, rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1376965">#1376965, rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1356859">#1356859, rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1026181">#1026181, rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1367173">#1367173, rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1390482">#1390482, 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/1392369">#1392369.

Release notes for Percona XtraDB Cluster href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/release-notes/Percona-XtraDB-Cluster-5.6.21-25.8.html">5.6.21-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.

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/2014/11/25/percona-xtradb-cluster-5-6-21-25-8-now-available/">Percona XtraDB Cluster 5.6.21-25.8 is now available appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.

Nov
24
2014
--

Percona Server 5.6.21-70.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.21-70.1 on November 24, 2014. 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.21-70.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-21.html" rel="nofollow">5.6.21, including all the bug fixes in it, Percona Server 5.6.21-70.1 is the current GA release in the Percona Server 5.6 series. Percona Server is open-source and free. Complete details of this release can be found in the rel="nofollow" href="https://launchpad.net/percona-server/+milestone/5.6.21-70.1" rel="nofollow">5.6.21-70.1 milestone on Launchpad.

Bugs Fixed:

  • A slave replicating in RBR mode would crash, if a table definition between master and slave differs with an allowed conversion, and the binary log contains a table map event followed by two row log events. This bug is an upstream regression introduced by a fix for bug rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=72610">#72610. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1380010">#1380010.
  • An incorrect source code function attribute would cause MySQL to crash on an InnoDB row write, if compiled with a recent GCC with certain compilation options. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1390695">#1390695 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=74842">#74842).
  • MTR tests for Response Time Distribution were not packaged in binary packages. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1387170">#1387170.
  • The RPM packages provided for CentOS 5 were built using a debugging information format which is not supported in the gdb version included with CentOS 5.10. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1388972">#1388972.
  • A session on a server in mixed mode binlogging would switch to row-based binlogging whenever a temporary table was created and then queried. This switch would last until the session end or until all temporary tables in the session were dropped. This was unnecessarily restrictive and has been fixed so that only the statements involving temporary tables were logged in the row-based format whereas the rest of the statements would continue to use the statement-based logging. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1313901">#1313901 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=72475">#72475).

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

Release notes for Percona Server 5.6.21-70.1 are available in the  href="http://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.21-70.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/2014/11/24/percona-server-5-6-21-70-1-now-available/">Percona Server 5.6.21-70.1 is now available appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.

Nov
19
2014
--

How a set of queries can be killed in MySQL using Percona Toolkit’s pt-kill

You might have encountered situations where you had to kill some specific select queries that were running for long periods and choking the database. This post will go into more detail with an example of report query offloading.

Report query (select) offloading to a slave server is a common practice to reduce the workload of the master DB server. The long running selects will be executed in the slave for report generation. I have observed in many cases where the slave used to get delayed or the slave DB encounters a slowdown due to some heavy long-running orphaned selects from some wrong reports.

There are two main ways to kill queries in MySQL: 1. use custom scripts that match on a regular expression, or 2. use a tool written and supported by Percona that is designed to kill queries based on matching conditions. Below is one script that will help you to kill those queries. The script will take the process list from MySQL and filter the long-running select query considering the “User”, “Time” and “State” from the list. However I suggest that you use the  title="pt-kill" href="http://www.percona.com/doc/percona-toolkit/2.1/pt-kill.html" >pt-kill tool from  title="percona toolkit" href="http://www.percona.com/doc/percona-toolkit/2.2/" >Percona Toolkit which provides a more reliable choice and options based on your requirements.

Process list:

+-----+------+-----------+------+---------+------+------------------------------+-----------------------------+
| Id  | User | Host      | db   | Command | Time | State                        | Info                        |
+-----+------+-----------+------+---------+------+------------------------------+-----------------------------+
| 103 | root | localhost | test | Query   |    0 | init                         | show processlist            |
| 104 | root | localhost | test | Sleep   |  383 |                              | NULL                        |
| 106 | root | localhost | test | Query   |  377 | Waiting for table level lock | SELECT * FROM t FOR UPDATE  |
| 107 | root | localhost | test | Query   |  364 | Waiting for table level lock | insert into t value(5)      |
| 108 | rpt  | localhost | test | Query   |  345 | Waiting for table level lock | SELECT c1 FROM t FOR UPDATE |
+-----+------+-----------+------+---------+------+------------------------------+-----------------------------+

1. Shell script example:

List all queries from rpt user having query time greater than 1 minute:
[root@test3 ~]# for id in $(mysql -t -e "SHOW FULL PROCESSLIST" | /bin/awk -F "|" '($6 ~ /Query/) && (60< $7) &&
 ($3 ~ /rpt/) { print $2}'); do echo "KILL QUERY $id;"; done
KILL QUERY 108;
Kill all queries from rpt user having query time greater than 1 minute:
[root@test3 ~]# for id in $(mysql -t -e "SHOW FULL PROCESSLIST" | /bin/awk -F "|" '($6 ~ /Query/) && (60< $7) &&
 ($3 ~ /rpt/)  { print $2}'); do mysql  -e "KILL QUERY $id;"; done

2. title="pt-kill" href="http://www.percona.com/doc/percona-toolkit/2.1/pt-kill.html">Pt-kill example:

List all queries from rpt user having query time greater than 1 minute (–print):

[root@test3 ~]# pt-kill --busy-time 60 --match-command Query --user root --print --match-user rpt
--socket /tmp/mysql.sock
# 2014-11-12T03:51:01 KILL 108 (Query 485 sec) SELECT c1 FROM t FOR UPDATE
# 2014-11-12T03:51:31 KILL 108 (Query 515 sec) SELECT c1 FROM t FOR UPDATE
# 2014-11-12T03:52:01 KILL 108 (Query 545 sec) SELECT c1 FROM t FOR UPDATE

Kill all queries from rpt user having query time greater than 1 minute (–kill-query):

[root@test3 ~]# pt-kill --busy-time 60 --match-command Query --user root --print --kill-query --match-user rpt
--socket /tmp/mysql.sock
# 2014-11-12T03:53:26 KILL QUERY 108 (Query 630 sec) SELECT c1 FROM t FOR UPDATE

Process list:

+-----+------+-----------+------+---------+------+------------------------------+----------------------------+
| Id  | User | Host      | db   | Command | Time | State                        | Info                       |
+-----+------+-----------+------+---------+------+------------------------------+----------------------------+
| 103 | root | localhost | test | Query   |    0 | init                         | show processlist           |
| 104 | root | localhost | test | Sleep   |  843 |                              | NULL                       |
| 106 | root | localhost | test | Query   |  837 | Waiting for table level lock | SELECT * FROM t FOR UPDATE |
| 107 | root | localhost | test | Query   |  824 | Waiting for table level lock | insert into t value(5)     |
| 108 | rpt  | localhost | test | Sleep   |  805 |                              | NULL                       |
| 111 | root | localhost | NULL | Sleep   |   25 |                              | NULL                       |
+-----+------+-----------+------+---------+------+------------------------------+----------------------------+

 Note :  href="http://www.percona.com/doc/percona-toolkit/2.1/pt-kill.html#cmdoption-pt-kill--kill-query">–kill-query option makes class="Apple-converted-space">  href="http://www.percona.com/doc/percona-toolkit/2.1/pt-kill.html"> class="program">pt-kill class="Apple-converted-space"> kill matching queries. This requires MySQL 5.0 or newer. Unlike class="Apple-converted-space">  class="reference internal" href="http://www.percona.com/doc/percona-toolkit/2.2/pt-kill.html#cmdoption-pt-kill--kill">–kill class="Apple-converted-space"> which kills the connection for matching queries, this option only kills the query, not its connection.

title="pt-kill" href="http://www.percona.com/doc/percona-toolkit/2.1/pt-kill.html">pt-kill captures queries from SHOW PROCESSLIST, filters them, and then either kills or prints them. This is also known as a “slow query sniper” in some circles. The idea is to watch for queries that might be consuming too many resources, and kill them. For details please read the tool’s ( title="pt-kill" href="http://www.percona.com/doc/percona-toolkit/2.1/pt-kill.html">pt-kill) documentation.

The post rel="nofollow" href="http://www.percona.com/blog/2014/11/19/how-a-set-of-queries-can-be-killed-in-mysql-using-pt-kill/">How a set of queries can be killed in MySQL using Percona Toolkit’s pt-kill appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.

Nov
17
2014
--

Percona Toolkit 2.2.12 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.12.  Released on November 14, 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. Downloads are available  href="http://www.percona.com/downloads/percona-toolkit/2.2.12/">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-stalk.html">pt-stalk now gathers dmesg output from up to 60 seconds before the triggering event.

Bugs Fixed:

  • Fixed bug rel="nofollow" href="https://bugs.launchpad.net/percona-toolkit/+bug/1376561" rel="nofollow">1376561: href="http://www.percona.com/doc/percona-toolkit/2.2/pt-archiver.html">pt-archiver was not able to archive all the rows when a table had a hash partition. Fixed by implementing support for tables which have primary or unique indexes.
  • Fixed bug rel="nofollow" href="https://bugs.launchpad.net/percona-toolkit/+bug/1217466" rel="nofollow">1217466: href="http://www.percona.com/doc/percona-toolkit/2.2/pt-table-checksum.html">pt-table-checksum would refuses to run on Percona XtraDB Cluster if server_id was the same on all nodes. Fixed by using the href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-system-index.html#wsrep_node_incoming_address">wsrep_node_incoming_address as a unique identifier for cluster nodes, instead of relying on server_id.
  • Fixed bug rel="nofollow" href="https://bugs.launchpad.net/percona-toolkit/+bug/1269695" rel="nofollow">1269695: href="http://www.percona.com/doc/percona-toolkit/2.2/pt-online-schema-change.html">pt-online-schema-change documentation now contains more information about limitations on why it isn’t running ALTER TABLE for a table which has only a non-unique index.
  • Fixed bug rel="nofollow" href="https://bugs.launchpad.net/percona-toolkit/+bug/1328686" rel="nofollow">1328686: Running href="http://www.percona.com/doc/percona-toolkit/2.2/pt-heartbeat.html">pt-hearbeat with --check-read-only option would cause an error when running on server with read_only option. Tool now waits for server read_only status to be disabled before starting to run.
  • Fixed bug rel="nofollow" href="https://bugs.launchpad.net/percona-toolkit/+bug/1373937" rel="nofollow">1373937: href="http://www.percona.com/doc/percona-toolkit/2.2/pt-table-checksum.html">pt-table-checksum now supports none as valid --recursion-method when using with Percona XtraDB Cluster.
  • Fixed bug rel="nofollow" href="https://bugs.launchpad.net/percona-toolkit/+bug/1377888" rel="nofollow">1377888: Documentation was stating that href="http://www.percona.com/doc/percona-toolkit/2.2/pt-query-digest.html">pt-query-digest is able to parse a raw binary log file, while it can only parse a file which was decoded with mysqlbinlog tool before. Fixed by improving the documentation and adding a check for binary file and providing a relevant error message.

Details of the release can be found in the  href="http://www.percona.com/doc/percona-toolkit/2.2/release_notes.html#v2-2-12-released-2014-11-14">release notes and the  rel="nofollow" href="https://launchpad.net/percona-toolkit/+milestone/2.2.12" rel="nofollow">2.2.12 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/2014/11/17/percona-toolkit-2-2-12-now-available/">Percona Toolkit 2.2.12 is now available appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.

Nov
03
2014
--

Percona XtraBackup 2.2.6 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.6 on November 3, 2014. Downloads are available from our download site href="http://www.percona.com/downloads/XtraBackup/Percona-XtraBackup-2.2.6/">here and href="http://www.percona.com/doc/percona-xtrabackup/2.2/installation.html">Percona Software Repositories. We’re also happy to announce that Ubuntu 14.10 and CentOS 7 users can download, install, and upgrade Percona XtraBackup 2.2.6 from Percona’s 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.

New Features:

  • Percona XtraBackup now reads server options from SHOW VARIABLES rather than my.cnf configuration file.
  • Percona XtraBackup now has more verbose output during initial table scan (it will now print a diagnostic message before performing a tablespace scan, which may take a long time on systems with large numbers of tablespaces) and before starting a backup/apply-log/copy-back operation in innobackupex (it will now print a diagnostic message with a timestamp to make it easier for users to get duration of the operation.)

Bugs Fixed:

  • innobackupex didn’t take the default datadir, which caused backups to fail if the datadir wasn’t specified in the my.cnf configuration file. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/936934">#936934.
  • innobackupex will now fail with an error when innobackupex –slave-info is used on a multi-threaded non-GTID slave, because Exec_Master_Log_Pos cannot be trusted for a multi-threaded slave. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1372679">#1372679.
  • InnoDB log scanning failure (bug rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=60788">#60788) would cause backups to fail. Fixed by porting the fix from MySQL 5.7. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1375383">#1375383.
  • Options --apply-log and --decompress weren’t marked as mutually exclusive, ie. if they were both specified, only --decompress would work, which could lead to MySQL instance being started with an unprepared backup. Fixed by making mutually exclusive categories of options: 1. --decompress, --decrypt; 2. --copy-back; 3. --move-back; 4. --apply-log. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1376874">#1376874.
  • innobackupex wasn’t creating directories specified in innodb_data_home_dir and innodb_log_group_home_dir when --copy-back option was used. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1382347">#1382347.
  • Percona XtraBackup now supports all option modifiers supported by upstream MySQL: skip, disable, enable, maximum, loose. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/664128">#664128.
  • Percona XtraBackup would fail to perform a full backup on Percona Server 5.5 if innodb_log_file_size variable wasn’t set in the [mysqld] section of my.cnf. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1334062">#1334062.

Other bugs fixed: rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1379905">#1379905, rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1386013">#1386013, rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1072695">#1072695, rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1375241">#1375241, rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1182841">#1182841, and rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1343722">#1343722.

Release notes with all the bugfixes for Percona XtraBackup 2.2.6 are available in our href="http://www.percona.com/doc/percona-xtrabackup/2.2/release-notes/2.2/2.2.6.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/2014/11/03/percona-xtrabackup-2-2-6-is-now-available/">Percona XtraBackup 2.2.6 is now available appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.

Nov
03
2014
--

Percona Server 5.6.21-70.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.21-70.0 on October 30, 2014. 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.21-70.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. We’re also happy to announce that Ubuntu 14.10 and CentOS 7 users can download, install, and upgrade Percona Server 5.6 from Percona’s software repositories.

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

New Features:

  • Percona Server has ported new href="http://www.percona.com/doc/percona-server/5.6/management/super_read_only.html#super-read-only">super-read-only option from WebScaleSQL.
  • Percona Server has implemented href="http://www.percona.com/doc/percona-server/5.6/flexibility/csv_engine_mode.html#csv-engine-mode">CSV engine mode for standard-compliant quote and comma parsing. This feature also fixes the bug rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1316042">#1316042 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=71091">#71091).
  • Percona Server now supports rel="nofollow" rel="nofollow" href="https://github.com/Tokutek/tokudb-engine/wiki/Replication-Slave-Performance-on-TokuDB">Read Free Replication for TokuDB storage engine.
  • TokuDB storage engine package has been updated to version rel="nofollow" rel="nofollow" href="http://docs.tokutek.com/tokudb/tokudb-release-notes.html#tokudb-7-5-2">7.5.2.

Bugs Fixed:

  • Values of IP and DB fields in the Audit Log Plugin were incorrect. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1379023">#1379023.
  • Specifying the --malloc-lib during the server start would produce two LD_PRELOAD entries, if a system-wide jemalloc library was installed. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1382069">#1382069.
  • In multi-threaded slave replication setup, an incomplete log event group (the one which doesn’t end with COMMIT/ROLLBACK/XID) in a relay log could have caused a replication stall. An incomplete log event group might occur as a result of one of the following events: 1) slave crash; 2) STOP SLAVE or FLUSH LOGS command issued at a specific moment; 3) server shutdown at a specific moment. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1331586">#1331586 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=73066">#73066).
  • Purging bitmaps exactly up to the last tracked LSN would abort XtraDB changed page tracking. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1382336">#1382336.
  • mysql_install_db script would silently ignore any mysqld startup failures. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1382782">#1382782 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=74440">#74440).

Other bugs fixed: rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1369950">#1369950, rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1335590">#1335590, rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1067103">#1067103, and rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1282599">#1282599.

Release notes for Percona Server 5.6.21-70.0 are available in the  href="http://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.21-70.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/2014/11/03/percona-server-5-6-21-70-0-now-available/">Percona Server 5.6.21-70.0 is now available appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.

Oct
07
2014
--

Percona Server 5.6.21-69.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.21-69.0 on October 7, 2014. 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.21-69.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-21.html" rel="nofollow">5.6.21, including all the bug fixes in it, Percona Server 5.6.21-69.0 is the current GA release in the Percona Server 5.6 series. Percona Server is open-source and free. Complete details of this release can be found in the rel="nofollow" href="https://launchpad.net/percona-server/+milestone/5.6.21-69.0" rel="nofollow">5.6.21-69.0 milestone on Launchpad.

New Features:

  • href="http://www.percona.com/doc/percona-server/5.6/diagnostics/response_time_distribution.html#response-time-distribution">Response Time Distribution feature has been from Percona Server 5.5 as a plugin.
  • TokuDB storage engine package has been updated to version rel="nofollow" href="http://docs.tokutek.com/tokudb/tokudb-release-notes.html#tokudb-7-5-0" rel="nofollow">7.5.1.

Bugs Fixed:

  • href="http://www.percona.com/doc/percona-server/5.6/management/backup_locks.html#backup-locks">Backup Locks did not guarantee consistent SHOW SLAVE STATUS information with binary log disabled. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1358836" rel="nofollow">#1358836.
  • href="http://www.percona.com/doc/percona-server/5.6/management/audit_log_plugin.html#audit-log-plugin">Audit Log Plugin would rotate the audit log in middle of an audit message. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1363370" rel="nofollow">#1363370.
  • When the binary log is enabled on a replication slave, SHOW SLAVE STATUS performed under an active BINLOG lock could lead to a deadlock. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1372806" rel="nofollow">#1372806.
  • Fixed a memory leak in href="http://www.percona.com/doc/percona-server/5.6/diagnostics/scalability_metrics_plugin.html#scalability-metrics-plugin">Metrics for scalability measurement. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1334570" rel="nofollow">#1334570.
  • Fixed a memory leak if href="http://www.percona.com/doc/percona-server/5.6/management/secure_file_priv_extended.html#secure-file-priv-extended">secure-file-priv option was used with no argument. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1334719" rel="nofollow">#1334719.
  • LOCK TABLES FOR BACKUP is now incompatible with LOCK TABLES, FLUSH TABLES WITH READ LOCK, and FLUSH TABLES FOR EXPORT in the same connection. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1360064" rel="nofollow">#1360064.

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

NOTE: Automatic upgrade for Percona Server with TokuDB on Debian/Ubuntu distribution will cause an error. In order to upgrade you’ll need to force the upgrade with “apt-get install -f” or remove the percona-server-tokudb-5.6 before upgrading and install it after the server package upgrade is done.

Release notes for Percona Server 5.6.21-69.0 are available in the  href="http://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.21-69.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/2014/10/07/percona-server-5-6-21-69-0-now-available/">Percona Server 5.6.21-69.0 is now available appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.

Oct
07
2014
--

Percona Server 5.5.40-36.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.40-36.1 on October 7, 2014. Based on rel="nofollow" href="http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-40.html" rel="nofollow">MySQL 5.5.40 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.40-36.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.40-36.1" rel="nofollow">5.5.34-36.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:

  • href="http://www.percona.com/doc/percona-server/5.5/management/audit_log_plugin.html#audit-log-plugin">Audit Log Plugin would rotate the audit log in middle of an audit message. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1363370" rel="nofollow">#1363370.
  • Fixed a memory leak in href="http://www.percona.com/doc/percona-server/5.5/diagnostics/scalability_metrics_plugin.html#scalability-metrics-plugin">Metrics for scalability measurement. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1334570" rel="nofollow">#1334570.
  • Fixed a memory leak if href="http://www.percona.com/doc/percona-server/5.5/management/secure_file_priv_extended.html#secure-file-priv-extended">secure-file-priv option was used with no argument. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1334719" rel="nofollow">#1334719.

Release notes for Percona Server 5.5.40-36.1 are available in our href="http://www.percona.com/doc/percona-server/5.5/release-notes/Percona-Server-5.5.40-36.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.

(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.21-69.0.html">5.6.21-69.0.)

The post rel="nofollow" href="http://www.percona.com/blog/2014/10/07/percona-server-5-5-40-36-1-now-available/">Percona Server 5.5.40-36.1 is now available appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.

Oct
06
2014
--

Percona XtraBackup 2.2.5 now available (free MySQL hot backup software)

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.5 on October 2, 2014. Downloads are available from our download site href="http://www.percona.com/downloads/XtraBackup/Percona-XtraBackup-2.2.5/">here and 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.

New Features:

  • Percona XtraBackup has been rebased on MySQL 5.6.21.

Bugs Fixed:

  • The fix for bug rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1079700" rel="nofollow">#1079700 introduced a problem for users with huge numbers of InnoDB tablespaces, and the workaround of raising the open files limits didn’t work in all cases due to a limitation in the Linux kernel. A new innobackupex href="http://www.percona.com/doc/percona-xtrabackup/2.2/innobackupex/innobackupex_option_reference.html#cmdoption-innobackupex--close-files">--close-files option has been implemented to close the file handles once they are no longer accessed. NOTE: Using this option may result in a broken backup if DDL is performed on InnoDB tables during the backup procedure. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1222062" rel="nofollow">#1222062.
  • Fix for bug rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1206309" rel="nofollow">#1206309 introduced a regression in Percona XtraBackup 2.2.0 which caused Percona XtraBackup to fail to copy redo logs in random cases. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1365835" rel="nofollow">#1365835.
  • innobackupex href="http://www.percona.com/doc/percona-xtrabackup/2.2/innobackupex/innobackupex_option_reference.html#cmdoption-innobackupex--galera-info">--galera-info didn’t copy the last binlog file when it was taking a backup from server where href="http://www.percona.com/doc/percona-server/5.6/management/backup_locks.html">backup locks are supported. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1368577" rel="nofollow">#1368577.
  • xtrabackup binary would accept arguments that were not options, which could lead to unexpected results. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1367377" rel="nofollow">#1367377.
  • If innobackupex is run against MySQL 5.1 with built-in InnoDB, it will now suggest using Percona XtraBackup 2.0 or upgrading to InnoDB plugin, rather than just failing with the generic unsupported server version message. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1335101" rel="nofollow">#1335101.
  • Using the (deprecated) log parameter in mysqld section would cause backups to fail. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1347698" rel="nofollow">#1347698.
  • Percona XtraBackup now uses MySQL code to get the stack trace in case Percona XtraBackup crashes with a segmentation fault or an assertion failure. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/766305" rel="nofollow">#766305.
  • Attempt to use any of the following options without the href="http://www.percona.com/doc/percona-xtrabackup/2.2/innobackupex/innobackupex_option_reference.html#cmdoption-innobackupex--incremental">--incremental option now fails with an error message rather than creates a full backup: href="http://www.percona.com/doc/percona-xtrabackup/2.2/innobackupex/innobackupex_option_reference.html#cmdoption-innobackupex--incremental-lsn">--incremental-lsn, href="http://www.percona.com/doc/percona-xtrabackup/2.2/innobackupex/innobackupex_option_reference.html#cmdoption-innobackupex--incremental-basedir">--incremental-basedir, href="http://www.percona.com/doc/percona-xtrabackup/2.2/innobackupex/innobackupex_option_reference.html#cmdoption-innobackupex--incremental-history-name">--incremental-history-name, href="http://www.percona.com/doc/percona-xtrabackup/2.2/innobackupex/innobackupex_option_reference.html#cmdoption-innobackupex--incremental-history-uuid">--incremental-history-uuid. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1213778" rel="nofollow">#1213778.

Other bugs fixed: rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1367613" rel="nofollow">#1367613, rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1368574" rel="nofollow">#1368574, rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1370462" rel="nofollow">#1370462, rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1371441" rel="nofollow">#1371441, rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1373429" rel="nofollow">#1373429, rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1373984" rel="nofollow">#1373984, and rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1265070" rel="nofollow">#1265070.

Release notes with all the bugfixes for Percona XtraBackup 2.2.5 are available in our href="http://www.percona.com/doc/percona-xtrabackup/2.2/release-notes/2.2/2.2.5.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/2014/10/06/percona-xtrabackup-2-2-5-now-available/">Percona XtraBackup 2.2.5 now available (free MySQL hot backup software) appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.

Powered by WordPress | Theme: Aeros 2.0 by TheBuckmaker.com