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.

Jan
14
2015
--

Percona XtraBackup 2.2.8 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.8 on January 14, 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.

New Features:

  • Percona XtraBackup has been rebased on MySQL 5.6.22.

Bugs Fixed:

  • Incremental backups would fail if the number of undo tablespaces ( rel="nofollow" href="https://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_undo_tablespaces" rel="nofollow">innodb_undo_tablespaces) was more than 1. This was caused by innobackupex removing the undo tablespaces during the prepare phase. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1363234" rel="nofollow">#1363234.
  • Fixed multiple memory leaks detected by AddressSanitizer. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1395143" rel="nofollow">#1395143.
  • innobackupex could fail when preparing backup that was taken from Percona Server 5.5 with log files ( rel="nofollow" href="http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_log_file_size" rel="nofollow">innodb_log_file_size) bigger than 4G. The root cause was that the last checkpoint LSN offset in log group is stored at different offsets in ibdata1 for Percona Server 5.5 and MySQL 5.6 when the total size of log files is greater than 4G. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1403237" rel="nofollow">#1403237.
  • Percona XtraBackup out-of-source builds failed. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1402450" rel="nofollow">#1402450.

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

Jan
12
2015
--

Percona Server 5.6.22-71.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-71.0 on January 12, 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-71.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-71.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-71.0" rel="nofollow">5.6.22-71.0 milestone on Launchpad.

New Features:

  • Percona Server has implemented improved slow log reporting for queries in href="http://www.percona.com/doc/percona-server/5.6/diagnostics/slow_extended.html#improved-sp-reporting">stored procedures.
  • TokuDB storage engine package has been updated to version rel="nofollow" href="http://docs.tokutek.com/tokudb/tokudb-release-notes.html#tokudb-version-7-x" rel="nofollow">7.5.4. Percona Server with an older version of TokuDB could hit an early scaling limit when the binary log was enabled. TokuDB 7.5.4 fixes this problem by using the hints supplied by the binary log group commit algorithm to avoid fsync’ing its recovery log during the commit phase of the 2 phase commit algorithm that MySQL uses for transactions when the binary log is enabled.

Bugs Fixed:

  • Debian and Ubuntu init scripts no longer have a hardcoded server startup timeout. This has been done to accommodate situations where server startup takes a very long time, for example, due to a crash recovery or buffer pool dump restore. Bugs fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1072538" rel="nofollow">#1072538 and rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1328262" rel="nofollow">#1328262.
  • A read-write workload on compressed InnoDB tables might have caused an assertion error. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1268656" rel="nofollow">#1268656.
  • Selecting from href="http://www.percona.com/doc/percona-server/5.6/diagnostics/misc_info_schema_tables.html#GLOBAL_TEMPORARY_TABLES">GLOBAL_TEMPORARY_TABLES table while running an online ALTER TABLE in parallel could lead to server crash. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1294190" rel="nofollow">#1294190.
  • A wrong stack size calculation could lead to a server crash when Performance Schema tables were storing big amount of data or in case of server being under highly concurrent load. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1351148" rel="nofollow">#1351148 (upstream rel="nofollow" href="http://bugs.mysql.com/bug.php?id=73979" rel="nofollow">#73979).
  • A query on an empty table with a BLOB column may crash the server. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1384568" rel="nofollow">#1384568 (upstream rel="nofollow" href="http://bugs.mysql.com/bug.php?id=74644" rel="nofollow">#74644).
  • A read-write workload on compressed InnoDB tables might have caused an assertion error. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1395543" rel="nofollow">#1395543.
  • If href="http://www.percona.com/doc/percona-server/5.6/performance/handlersocket.html#handlersocket-page">HandlerSocket was enabled, the server would hang during shutdown. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1397859" rel="nofollow">#1397859.
  • The default MySQL configuration file, my.cnf, was not installed during a new installation on CentOS. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1405667" rel="nofollow">#1405667.
  • The query optimizer did not pick a covering index for some ORDER BY queries. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1394967" rel="nofollow">#1394967 (upstream rel="nofollow" href="http://bugs.mysql.com/bug.php?id=57430" rel="nofollow">#57430).
  • SHOW ENGINE INNODB STATUS was displaying two identical TRANSACTIONS sections. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1404565" rel="nofollow">#1404565.
  • A race condition in href="http://www.percona.com/doc/percona-server/5.6/scalability/multiple_user_level_locks.html#multiple-user-level-locks">Multiple user level locks per connection implementation could cause a deadlock. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1405076" rel="nofollow">#1405076.

Other bugs fixed: rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1394357" rel="nofollow">#1394357, rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1337251" rel="nofollow">#1337251, rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1399174" rel="nofollow">#1399174, rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1396330" rel="nofollow">#1396330 (upstream rel="nofollow" href="http://bugs.mysql.com/bug.php?id=74987" rel="nofollow">#74987), and rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1401776" rel="nofollow">#1401776 (upstream rel="nofollow" href="http://bugs.mysql.com/bug.php?id=75189" rel="nofollow">#75189).

Known Issues: /> If you’re upgrading TokuDB package on CentOS 5/6 you’ll need to restart the MySQL service after the upgrade, otherwise TokuDB storage engine won’t be initialized.

Release notes for Percona Server 5.6.22-71.0 are available in the  href="http://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.22-71.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/01/12/percona-server-5-6-22-71-0-now-available/">Percona Server 5.6.22-71.0 is now available appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.

Jan
12
2015
--

Percona Server 5.5.41-37.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.5.41-37.0 on January 9, 2015. Based on rel="nofollow" href="http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-41.html" rel="nofollow">MySQL 5.5.41 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.41-37.0 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.41-37.0" rel="nofollow">5.5.41-37.0 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.

New Features:

  • Percona Server has implemented href="http://www.percona.com/doc/percona-server/5.5/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 has implemented improved slow log reporting for queries in href="http://www.percona.com/doc/percona-server/5.5/diagnostics/slow_extended_55.html#improved-sp-reporting">stored procedures.

Bugs Fixed:

  • Debian and Ubuntu init scripts no longer have a hardcoded server startup timeout. This has been done to accommodate situations where server startup takes a very long time, for example, due to a crash recovery or buffer pool dump restore. Bugs fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1072538">#1072538 and rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1328262">#1328262.
  • If href="http://www.percona.com/doc/percona-server/5.5/performance/handlersocket.html">HandlerSocket was enabled, the server would hang during shutdown. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1319904">#1319904.
  • Wrong stack calculation could lead to a server crash when Performance Schema tables were storing big amount of data or in case of server being under highly concurrent load. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1351148">#1351148 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=73979">#73979).
  • Values of IP and DB fields in the href="http://www.percona.com/doc/percona-server/5.5/management/audit_log_plugin.html#audit-log-plugin">Audit Log Plugin were incorrect. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1379023">#1379023.
  • Percona Server 5.5 would fail to build with GCC 4.9.1 (such as bundled with Ubuntu Utopic) in debug configuration. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1396358">#1396358 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=75000">#75000).
  • Default MySQL configuration file, my.cnf, was not installed during the new installation on CentOS. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1405667">#1405667.
  • 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).
  • Purging bitmaps exactly up to the last tracked LSN would abort href="http://www.percona.com/doc/percona-server/5.5/management/changed_page_tracking.html#changed-page-tracking">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/1067103">#1067103, rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1394357">#1394357, rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1282599">#1282599, rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1335590">#1335590, rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/bugs/1369950">#1369950, rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1401791">#1401791 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=73281">#73281), and rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1396330">#1396330 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=74987">#74987).

(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.22-71.0.html">5.6.22-71.0.)

Release notes for Percona Server 5.5.41-37.0 are available in our href="http://www.percona.com/doc/percona-server/5.5/release-notes/Percona-Server-5.5.41-37.0.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/01/12/percona-server-5-5-41-37-0-now-available/">Percona Server 5.5.41-37.0 is now available appeared first on rel="nofollow" href="http://www.percona.com/blog">MySQL Performance Blog.

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.