May
20
2015
--

Percona XtraBackup 2.3.1-beta1 is now available

href="https://www.percona.com/blog/wp-content/uploads/2013/01/Percona_XtraBackup.jpg"> class="alignright size-full wp-image-12668" src="https://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 href="https://www.percona.com/software/percona-xtrabackup">Percona XtraBackup 2.3.1-beta1 on May 20th 2015. Downloads are available from our download site href="https://www.percona.com/downloads/TESTING/XtraBackup/xtrabackup-2.3.1beta1/">here. This BETA release, will be available in Debian href="https://www.percona.com/doc/percona-xtrabackup/2.3/installation/apt_repo.html#percona-apt-testing-repository">testing and CentOS href="https://www.percona.com/doc/percona-xtrabackup/2.3/installation/yum_repo.html#testing-the-repository">testing repositories.

This is an BETA quality release and it is not intended for production. If you want a high quality, Generally Available release, the current Stable version should be used (currently href="https://www.percona.com/doc/percona-xtrabackup/2.2/release-notes/2.2/2.2.10.html">2.2.10 in the 2.2 series at the time of writing).

href="https://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.

This release contains all of the features and bug fixes in Percona XtraBackup 2.2.10, plus the following:

New Features:

  • innobackupex script has been rewritten in C and it’s set as the symlink for xtrabackup. innobackupex still supports all features and syntax as 2.2 version did, but it is now deprecated and will be removed in next major release. Syntax for new features will not be added to the innobackupex, only to the xtrabackup. xtrabackup now also copies MyISAM tables and supports every feature of innobackupex. Syntax for features previously unique to innobackupex (option names and allowed values) remains the same for xtrabackup.
  • Percona XtraBackup can now read swift parameters from a [xbcloud] section from the .my.cnf file in the users home directory or alternatively from the global configuration file /etc/my.cnf. This makes it more convenient to use and avoids passing the sensitive data, such as href="https://www.percona.com/doc/percona-xtrabackup/2.3/xbcloud/xbcloud.html#cmdoption--swift-key">--swift-key, on the command line.
  • Percona XtraBackup now supports different href="https://www.percona.com/doc/percona-xtrabackup/2.3/xbcloud/xbcloud.html#swift-auth">authentication options for Swift.
  • Percona XtraBackup now supports partial download of the cloud backup.
  • Options: --lock-wait-query-type, --lock-wait-threshold and --lock-wait-timeout have been renamed to href="https://www.percona.com/doc/percona-xtrabackup/2.3/innobackupex/innobackupex_option_reference.html#cmdoption-innobackupex--ftwrl-wait-query-type">--ftwrl-wait-query-type, href="https://www.percona.com/doc/percona-xtrabackup/2.3/innobackupex/innobackupex_option_reference.html#cmdoption-innobackupex--ftwrl-wait-threshold">--ftwrl-wait-threshold and href="https://www.percona.com/doc/percona-xtrabackup/2.3/innobackupex/innobackupex_option_reference.html#cmdoption-innobackupex--ftwrl-wait-timeout">--ftwrl-wait-timeout respectively.

Bugs Fixed:

  • innobackupex didn’t work correctly when credentials were specified in .mylogin.cnf. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1388122">#1388122.
  • Options --decrypt and --decompress didn’t work with xtrabackup binary. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1452307">#1452307.
  • Percona XtraBackup now executes an extra FLUSH TABLES before executing FLUSH TABLES WITH READ LOCK to potentially lower the impact from FLUSH TABLES WITH READ LOCK. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1277403">#1277403.
  • innobackupex didn’t read user,password options from ~/.my.cnf file. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1092235">#1092235.
  • innobackupex was always reporting the original version of the innobackup script from InnoDB Hot Backup. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1092380">#1092380.

Release notes with all the bugfixes for Percona XtraBackup 2.3.1-beta1 are available in our href="https://www.percona.com/doc/percona-xtrabackup/2.3/release-notes/2.3/2.3.1-beta1.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="https://www.percona.com/blog/2015/05/20/percona-xtrabackup-2-3-1-beta1-is-now-available/">Percona XtraBackup 2.3.1-beta1 is now available appeared first on rel="nofollow" href="https://www.percona.com/blog">MySQL Performance Blog.

May
19
2015
--

Like my MySQL QA series? Here’s how to record your own!

id="attachment_29937" style="width: 310px" class="wp-caption alignleft"> href="https://www.percona.com/blog/wp-content/uploads/2015/05/5_Professional-Recording-Template-1280x720.png" > class="wp-image-29937 size-medium" title="Professional Screen Recording / Screencast Template 1280x720" src="https://www.percona.com/blog/wp-content/uploads/2015/05/5_Professional-Recording-Template-1280x720-300x169.png" alt="Professional Screen Recording / Screencast Template 1280x720" width="300" height="169" /> class="wp-caption-text">Professional Screen Recording / Screencast Template 1280×720

Whilst not directly related to MySQL, it may be helpful to post (and open source at the same time) the HD screen recording/screencast template I’ve been using to create the href="https://www.percona.com/blog/2015/03/17/free-mysql-qa-and-bash-linux-training-series/" >MySQL QA series.

If you’ve never recorded a screencast before, or if you’d like to improve your screen recordings, this short blog post will get you started/help you along the way!

 

Here’s what you need; /> 1. Software Budget: $0. Really! All required software is free, provided you have Microsoft Windows to use it on! /> 2. A reasonable quality headset. I can recommend (and use) a Microsoft LifeChat LX-3000 or similar (~$40) /> 3. The attached template (right-click the image above and select ‘Save Link/Image As…’ or similar)

Here’s how to get started; /> 1. Install Microsoft Visual C++ 2010 Redistributable Package (x86) from rel="nofollow" href="https://www.microsoft.com/en-us/download/details.aspx?id=5555" rel="nofollow">here. /> 2. Install CamStudio 2.7 or higher. CamStudio can be downloaded from rel="nofollow" href="http://camstudio.org/" rel="nofollow">http://camstudio.org/ /> 3. Install CamStudioCodec 1.5 or higher (a good quality codec, available from the same website as in step 2). /> 4. Use a 1600×900 or higher screen resolution to match the template size (or you can also edit the template). /> 5. Set the href="https://www.percona.com/blog/wp-content/uploads/2015/05/5_Professional-Recording-Template-1280x720.png" >Professional Screen Recording / Screencast Template (right click & save) as your background. /> 6. Make the settings/follow the instructions as per the template (tip: read everything first before you start). /> 7. You can scale your to-be-recorded window to match the black frame (and one of the settings as shown in the template makes CamStudio match the recording size exactly to that frame). The black frame ensures that any slight pixel-mismatch still shows nicely in the resulting video. /> 8. You may like to install a screen marking tool like rel="nofollow" href="http://stefanstools.sourceforge.net/DemoHelper.html" rel="nofollow">DemoHelper or rel="nofollow" href="http://www.screenmarker.com/" rel="nofollow">ScreenMarker.

If you followed the steps above you will have already covered the blue (top right) “Installation/use” steps nr’s 1-5, and you can now continue with the red steps 1-8 (and read the additional blue tips 1-4).

There’s quite a bit to it, but if you get it setup right the quality will be great!

I hope to see more technical how-to video’s on this and other blogs in the future!

Enjoy!

The post rel="nofollow" href="https://www.percona.com/blog/2015/05/19/like-my-mysql-qa-series-heres-how-to-record-your-own/">Like my MySQL QA series? Here’s how to record your own! appeared first on rel="nofollow" href="https://www.percona.com/blog">MySQL Performance Blog.

May
08
2015
--

Percona Server 5.6.24-72.2 is now available

href="https://www.percona.com/blog/wp-content/uploads/2014/05/percona_server.jpeg"> class="alignright size-thumbnail wp-image-22759" src="https://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="https://www.percona.com/software/percona-server">Percona Server 5.6.24-72.2 on May 8, 2015. Download the latest version from the title="Percona Server 5.6" href="https://www.percona.com/downloads/Percona-Server-5.6/Percona-Server-5.6.24-72.2/" >Percona web site or from the Percona href="https://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-24.html" rel="nofollow">5.6.24, including all the bug fixes in it, Percona Server 5.6.24-72.2 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.24-72.2" rel="nofollow">5.6.24-72.2 milestone on Launchpad.

New Features:

  • TokuDB storage engine package has been updated to version rel="nofollow" rel="nofollow" href="https://github.com/Tokutek/tokudb-engine/wiki/Release-Notes-for-TokuDB-7.5.7">7.5.7.

Bugs Fixed:

  • A server binary as distributed in binary tarballs could fail to load on different systems due to an unsatisfied libssl.so.6 dynamic library dependency. This was fixed by replacing the single binary tarball with multiple tarballs depending on the OpenSSL library available in the distribution: 1) ssl100 – for all Debian/Ubuntu versions except Squeeze/Lucid (libssl.so.1.0.0 => /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007f2e389a5000)); 2) ssl098 – only for Debian Squeeze and Ubuntu Lucid (libssl.so.0.9.8 => /usr/lib/libssl.so.0.9.8 (0x00007f9b30db6000)); 3) ssl101 – for CentOS 6 and CentOS 7 (libssl.so.10 => /usr/lib64/libssl.so.10 (0x00007facbe8c4000)); 4) ssl098e – to be used only for CentOS 5 (libssl.so.6 => /lib64/libssl.so.6 (0x00002aed5b64d000)). Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1172916">#1172916.
  • Executing a stored procedure containing a subquery would leak memory. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1380985">#1380985 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=76349">#76349).
  • A slave server restart could cause a 1755 slave SQL thread error if multi-threaded slave was enabled. This is a regression introduced by fix for bug rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1331586">#1331586 in href="http://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.21-70.0.html#5.6.21-70.0">5.6.21-70.0. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1380985">#1380985.
  • A string literal containing an invalid UTF-8 sequence could be treated as falsely equal to a UTF-8 column value with no invalid sequences. This could cause invalid query results. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1247218">#1247218 by a fix ported from MariaDB ( rel="nofollow" rel="nofollow" href="https://mariadb.atlassian.net/browse/MDEV-7649">MDEV-7649).
  • Percona Server .deb binaries were built without fast mutexes. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1433980">#1433980.
  • Installing or uninstalling the href="http://www.percona.com/doc/percona-server/5.6/management/audit_log_plugin.html">Audit Log Plugin would crash the server if the href="http://www.percona.com/doc/percona-server/5.6/management/audit_log_plugin.html#audit_log_file">audit_log_file variable was pointing to an inaccessible path. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1435606">#1435606.
  • The href="http://www.percona.com/doc/percona-server/5.6/management/audit_log_plugin.html#audit_log_file">audit_log_file would point to random memory area if the href="http://www.percona.com/doc/percona-server/5.6/management/audit_log_plugin.html">Audit Log Plugin was not loaded into server, and then installed with INSTALL PLUGIN, and my.cnf contained href="http://www.percona.com/doc/percona-server/5.6/management/audit_log_plugin.html#audit_log_file">audit_log_file setting. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1437505">#1437505.
  • A specific trigger execution on the master server could cause a slave assertion error under row-based replication. The trigger would satisfy the following conditions: 1) it sets a savepoint; 2) it declares a condition handler which releases this savepoint; 3) the trigger execution passes through the condition handler. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1438990">#1438990 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=76727">#76727).
  • Percona Server client packages were built with with EditLine instead of Readline. This was causing history file produced by the client no longer easy to read. Further, a client built with EditLine could display incorrectly on PuTTY SSH client after its window resize. Bugs fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1266386">#1266386, rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1296192">#1296192 and rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1332822">#1332822 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=63130">#63130, upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=72108">#72108 and rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=69991">#69991).
  • Unlocking a table while holding the backup binlog lock would cause an implicit erroneous backup lock release, and a subsequent server crash or hang at the later explicit backup lock release request. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1371827">#1371827.
  • Initializing slave threads or executing CHANGE MASTER TO statement would crash a debug build if autocommit was disabled and at least one of slave info tables were configured as tables. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1393682">#1393682.

Other bugs fixed: rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1372263">#1372263 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=72080">#72080), rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1436138">#1436138 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=76505">#76505), rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1182949">#1182949 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=69453">#69453), rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1111203">#1111203 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=68291">#68291), and rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1384566">#1384566 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=74615">#74615).

Release notes for Percona Server 5.6.24-72.2 are available in the  href="https://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.24-72.2.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="https://www.percona.com/blog/2015/05/08/percona-server-5-6-24-72-2-is-now-available/">Percona Server 5.6.24-72.2 is now available appeared first on rel="nofollow" href="https://www.percona.com/blog">MySQL Performance Blog.

May
08
2015
--

Percona Server 5.5.43-37.2 is now available

href="https://www.percona.com/blog/wp-content/uploads/2014/05/percona_server.jpeg"> class="alignright size-thumbnail wp-image-22759" src="https://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="https://www.percona.com/software/percona-server">Percona Server 5.5.43-37.2 on May 8, 2015. Based on rel="nofollow" href="http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-43.html" rel="nofollow">MySQL 5.5.43 href="https://www.percona.com/blog/wp-content/uploads/2014/05/percona_server.jpeg">, including all the bug fixes in it, Percona Server 5.5.43-37.2 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.43-37.2" rel="nofollow">5.5.43-37.2 milestone on Launchpad. Downloads are available href="https://www.percona.com/downloads/">here and from the href="https://www.percona.com/doc/percona-server/5.5/installation.html">Percona Software Repositories.

Bugs Fixed:

  • A server binary as distributed in binary tarballs could fail to load on different systems due to an unsatisfied libssl.so.6 dynamic library dependency. This was fixed by replacing the single binary tarball with multiple tarballs depending on the OpenSSL library available in the distribution: 1) ssl100 – for all Debian/Ubuntu versions except Squeeze/Lucid (libssl.so.1.0.0 => /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007f2e389a5000)); 2) ssl098 – only for Debian Squeeze and Ubuntu Lucid (libssl.so.0.9.8 => /usr/lib/libssl.so.0.9.8 (0x00007f9b30db6000)); 3) ssl101 – for CentOS 6 and CentOS 7 (libssl.so.10 => /usr/lib64/libssl.so.10 (0x00007facbe8c4000)); 4) ssl098e – to be used only for CentOS 5 (libssl.so.6 => /lib64/libssl.so.6 (0x00002aed5b64d000)). Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1172916">#1172916.
  • mysql_install_db would make the server produce an “Error in my_thread_global_end(): 1 threads didn't exit” error message. While this error does not prevent mysql_install_db from completing successfully, its presence might cause any mysql_install_db-calling script to return an error as well. This is a regression introduced by backporting fix for bug rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1319904">#1319904. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1402074">#1402074.
  • A string literal containing an invalid UTF-8 sequence could be treated as falsely equal to a UTF-8 column value with no invalid sequences. This could cause invalid query results. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1247218">#1247218 by a fix ported from MariaDB ( rel="nofollow" rel="nofollow" href="https://mariadb.atlassian.net/browse/MDEV-7649">MDEV-7649).
  • Percona Server .deb binaries were built without fast mutexes. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1433980">#1433980.
  • Installing or uninstalling the href="http://www.percona.com/doc/percona-server/5.5/management/audit_log_plugin.html">Audit Log Plugin would crash the server if the href="http://www.percona.com/doc/percona-server/5.5/management/audit_log_plugin.html#audit_log_file">audit_log_file variable was pointing to an inaccessible path. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1435606">#1435606.
  • The href="http://www.percona.com/doc/percona-server/5.5/management/audit_log_plugin.html#audit_log_file">audit_log_file variable would point to random memory area if the href="http://www.percona.com/doc/percona-server/5.5/management/audit_log_plugin.html">Audit Log Plugin was not loaded into server, and then installed with INSTALL PLUGIN, and my.cnf contained href="http://www.percona.com/doc/percona-server/5.5/management/audit_log_plugin.html#audit_log_file">audit_log_file setting. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1437505">#1437505.
  • Percona Server client .deb packages were built with with EditLine instead of Readline. Further, a client built with EditLine could display incorrectly on PuTTY SSH client after its window resize. Bugs fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1266386">#1266386 and rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1332822">#1332822 (upstream rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=63130">#63130 and rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=69991">#69991).

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

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

Release notes for Percona Server 5.5.43-37.2 are available in our href="https://www.percona.com/doc/percona-server/5.5/release-notes/Percona-Server-5.5.43-37.2.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="https://www.percona.com/blog/2015/05/08/percona-server-5-5-43-37-2-is-now-available/">Percona Server 5.5.43-37.2 is now available appeared first on rel="nofollow" href="https://www.percona.com/blog">MySQL Performance Blog.

Apr
14
2015
--

Percona Toolkit 2.2.14 is now available

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

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

New Features:

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

Bugs Fixed:

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

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

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

Mar
31
2015
--

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

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

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

Bugs Fixed:

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

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

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

Mar
30
2015
--

Percona XtraDB Cluster 5.5.41-25.11 is now available

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

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

Bugs Fixed:

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

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

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

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

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

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

Mar
09
2015
--

5 free handy tools for monitoring and managing MySQL replication

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

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

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

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

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

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

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

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

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

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

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

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

Example :

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

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

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

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

Example :

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

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

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

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

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

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

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

Example :

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

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

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

Example :

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

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

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

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

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

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

Mar
05
2015
--

Percona XtraDB Cluster 5.6.22-25.8 is now available

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

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

Bugs Fixed:

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

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

Known Issue:

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

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

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

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

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

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

Mar
04
2015
--

Percona Server 5.6.23-72.1 is now available

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

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

New Features:

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

Bugs Fixed:

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

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

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

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