Jul
21
2014
--

Percona XtraDB Cluster 5.6.19-25.6 is now available

href="http://www.mysqlperformanceblog.com/wp-content/uploads/2013/02/XtraDB-Cluster.jpg"> class="alignright size-full wp-image-12836" src="http://www.mysqlperformanceblog.com/wp-content/uploads/2013/02/XtraDB-Cluster.jpg" alt="Percona XtraDB Cluster 5.6.19-25.6" 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 July 21st 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.04 LTS users can now download, install, and upgrade Percona XtraDB Cluster 5.6 from title="Percona XtraDB Cluster 5.6 software repository" href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/installation.html#using-percona-software-repositories?id=repositories:start" >Percona’s software repositories.

Based on Percona Server href="http://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.19-67.0.html">5.6.19-67.0 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.6, and on rel="nofollow" href="https://launchpad.net/wsrep-group/+milestone/5.6.19-25.6" rel="nofollow">Codership wsrep API 25.6, Percona XtraDB Cluster 5.6.19-25.6 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.19-25.6" rel="nofollow">5.6.19-25.6 milestone at Launchpad.

New Features:

  • Percona XtraDB Cluster now supports storing the Primary Component state to disk by setting the href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-provider-index.html#pc.recovery">pc.recovery variable to true. The Primary Component can then recover automatically when all nodes that were part of the last saved state reestablish communications with each other. This feature can be used for automatic recovery from full cluster crashes, such as in the case of a data center power outage and graceful full cluster restarts without the need for explicitly bootstrapping a new Primary Component.
  • When joining the cluster, the state message exchange provides us with gcache seqno limits. That information is now used to choose a donor through IST first, and, if this is not possible, only then SST is attempted. The  href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-system-index.html#wsrep_sst_donor">wsrep_sst_donor setting is honored, though, and it is also segment aware.
  • An asynchronous replication slave thread was stopped when the node tried to apply the next replication event while the node was in non-primary state. But it would then remain stopped after the node successfully re-joined the cluster. A new variable,  href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-system-index.html#wsrep_restart_slave">wsrep_restart_slave, has been implemented which controls if the MySQL slave should be restarted automatically when the node re-joins the cluster.
  • Handling install message and install state message processing has been improved to make group forming a more stable process in cases when many nodes are joining the cluster.
  • A new href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-status-index.html#wsrep_evs_repl_latency">wsrep_evs_repl_latency status variable has been implemented which provides the group communication replication latency information.
  • Node consistency issues with foreign key grammar have been fixed. This fix introduces two new variables: href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-system-index.html#wsrep_slave_FK_checks">wsrep_slave_FK_checks and href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-system-index.html#wsrep_slave_UK_checks">wsrep_slave_UK_checks. These variables are set to TRUE and FALSE respectively by default. They control whether Foreign Key and Unique Key checking is done for applier threads.

Bugs Fixed:

  • Fixed the race condition in Foreign Key processing that could cause assertion. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1342959" rel="nofollow">#1342959.
  • The restart sequence in scripts/mysql.server would fail to capture and return if the start call failed to start the server. As a result, a restart could occur that failed upon start-up, and the script would still return 0 as if it worked without any issues. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1339894" rel="nofollow">#1339894.
  • Updating a unique key value could cause the server to hang if a slave node had enabled parallel slaves. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1280896" rel="nofollow">#1280896.
  • Percona XtraDB Cluster has implemented threadpool scheduling fixes. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1333348" rel="nofollow">#1333348.
  • garbd was returning an incorrect return code, ie. when garbd was already started, return code was 0. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1308103" rel="nofollow">#1308103.
  • rsync SST would silently fail on joiner when the rsync server port was already taken. Bug fixed href="http://www.mysqlperformanceblog.com/2014/07/21/percona-xtradb-cluster-5-6-19-25-6-now-available/wsrep_sst_rsync%20would%20silently%20fail%20on%20joiner%20when%20rsync%20server%20port%20was%20already%20taken.%20Bug%20fixed%20#1099783.">#1099783.
  • When href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-provider-index.html#gmcast.listen_addr">gmcast.listen_addr was configured to a certain address, the local connection point for outgoing connections was not bound to the listen address. This would happen if the OS has multiple interfaces with IP addresses in the same subnet. The OS would pick the wrong IP for a local connection point and other nodes would see connections originating from an IP address which was not listened to. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1240964" rel="nofollow">#1240964.
  • An issue with re-setting galera provider (in href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-system-index.html#wsrep_provider_options">wsrep_provider_options) has been fixed. Bug fixed #1260283.
  • Variable wsrep_provider_options couldn’t be set in runtime if no provider was loaded. Bug fixed #1260290.
  • Percona XtraDB Cluster couldn’t be built with Bison 3.0. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1262439" rel="nofollow">#1262439.
  • MySQL wasn’t handling exceeding the max writeset size wsrep error correctly. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1270920" rel="nofollow">#1270920.
  • Fixed the issue which caused a node to hang/fail when SELECTs/SHOW STATUS was run after FLUSH TABLES WITH READ LOCK was used on a node with wsrep_causal_reads set to 1 while there was a DML on other nodes. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1271177" rel="nofollow">#1271177.
  • Lowest group communication layer (evs) would fail to handle the situation properly when a large number of nodes would suddenly start recognizing each other. Bugs fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1271918" rel="nofollow">#1271918 and rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1249805" rel="nofollow">#1249805.
  • Percona XtraBackup SST would fail if the progress option was used with a large number of files. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1294431" rel="nofollow">#1294431.

NOTE: When performing an upgrade from an older 5.6 version on Debian/Ubuntu systems, in order to upgrade the Galera package correctly, you’ll need to href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/installation/apt_repo.html#apt-pinning-the-packages">pin the Percona repository and run: apt-get install percona-xtradb-cluster-56. This is required because older Galera deb packages have an incorrect version number. The correct href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/wsrep-status-index.html#wsrep_provider_version">wsrep_provider_version after upgrade should be 3.6(r3a949e6).

This release contains 50 fixed bugs. The complete list of fixed bugs can be found in our href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/release-notes/Percona-XtraDB-Cluster-5.6.19-25.6.html">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.19-25.6.html">5.6.19-25.6 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!

Percona XtraDB Cluster href="http://www.percona.com/doc/percona-xtradb-cluster/5.6/errata.html">Errata can be found in our documentation.

The post rel="nofollow" href="http://www.mysqlperformanceblog.com/2014/07/21/percona-xtradb-cluster-5-6-19-25-6-now-available/">Percona XtraDB Cluster 5.6.19-25.6 is now available appeared first on rel="nofollow" href="http://www.mysqlperformanceblog.com/">MySQL Performance Blog.

Jul
10
2014
--

Percona Toolkit 2.2.9 is now available

href="http://www.mysqlperformanceblog.com/wp-content/uploads/2013/03/Percona_ToolkitLogoVert_RGB.png"> class="alignright wp-image-13951" style="margin: 7px;" src="http://www.mysqlperformanceblog.com/wp-content/uploads/2013/03/Percona_ToolkitLogoVert_RGB-300x249.png" alt="Percona Toolkit" width="180" height="149" />Percona is glad to announce the release of  href="http://www.percona.com/software/percona-toolkit">Percona Toolkit 2.2.9 on July 10, 2014 (downloads are available  href="http://www.percona.com/downloads/percona-toolkit/2.2.9/">here and from the  href="http://www.percona.com/doc/percona-server/5.5/installation.html">Percona Software Repositories). This release is the current GA (Generally Available) stable release in the 2.2 series.

Bugs Fixed:

  • Fixed bug rel="nofollow" href="https://bugs.launchpad.net/bugs/1335960" rel="nofollow">1335960: href="http://www.percona.com/doc/percona-toolkit/2.2/pt-query-digest.html">pt-query-digest could not parse the binlogs from MySQL 5.6 because the binlog format was changed.
  • Fixed bug rel="nofollow" href="https://bugs.launchpad.net/bugs/1315130" rel="nofollow">1315130: href="http://www.percona.com/doc/percona-toolkit/2.2/pt-online-schema-change.html">pt-online-schema-change did not find child tables as expected. It could incorrectly locate tables – tables which reference a table with the same name in a different schema, and could miss tables referencing the altered table – if they were in a different schema..
  • Fixed bug rel="nofollow" href="https://bugs.launchpad.net/bugs/1335322" rel="nofollow">1335322: href="http://www.percona.com/doc/percona-toolkit/2.2/pt-stalk.html">pt-stalk would fail when variable or threshold was a non-integer.
  • Fixed bug rel="nofollow" href="https://bugs.launchpad.net/bugs/1258135" rel="nofollow">1258135: href="http://www.percona.com/doc/percona-toolkit/2.2/pt-deadlock-logger.html">pt-deadlock-logger was inserting older deadlocks into the deadlock table even if it was already there, therby creating unnecessary noise. For example, if the deadlock happened 1 year ago, and MySQL keeps it in the memory, pt-deadlock-logger would INSERT it into percona.deadlocks table every minute until server was restarted. This was fixed by comparing with the last deadlock fingerprint before issuing the INSERT query.
  • Fixed bug rel="nofollow" href="https://bugs.launchpad.net/bugs/1329422" rel="nofollow">1329422: href="http://www.percona.com/doc/percona-toolkit/2.2/pt-online-schema-change.html">pt-online-schema-change foreign-keys-method=none can break FK constraints in a way that is hard to recover from. Although this method of handling foreign key constraints is provided so that the database administrator can disable the tool’s built-in functionality if desired, a warning and confirmation request when using alter-foreign-keys-method “none” has been added to warn users when using this option.

Percona Toolkit is free and open-source. Details of the release can be found in the  href="http://www.percona.com/doc/percona-toolkit/2.2/release_notes.html#v2-2-9-released-2014-07-08">release notes and the  rel="nofollow" href="https://launchpad.net/percona-toolkit/+milestone/2.2.9" rel="nofollow">2.2.9 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.mysqlperformanceblog.com/2014/07/10/percona-toolkit-2-2-9-now-available/">Percona Toolkit 2.2.9 is now available appeared first on rel="nofollow" href="http://www.mysqlperformanceblog.com/">MySQL Performance Blog.

Jul
09
2014
--

TokuDB gotchas: slow INFORMATION_SCHEMA TABLES

We are using title="Percona Server 5.6.19-67.0 with TokuDB (GA) now available" href="http://www.mysqlperformanceblog.com/2014/07/01/percona-server-5-6-19-67-0-with-tokudb-ga-now-available/" >Percona Server + TokuDB engine extensively in href="https://cloud.percona.com/" >Percona Cloud Tools and getting real usage operational experience with this engine. So I want to share some findings we came across, in hope it may help someone in their work with TokuDB.

So, one problem I faced is that SELECT * FROM INFORMATION_SCHEMA.TABLES is quite slow when I have thousands tables in TokuDB. How slow? For example…

select * from information_schema.tables limit 1000;
...
1000 rows in set (18 min 31.93 sec)

This is very similar to what InnoDB faced a couple years back. InnoDB solved it by adding rel="nofollow" href="http://dev.mysql.com/doc/refman/5.1/en/innodb-parameters.html#sysvar_innodb_stats_on_metadata" >variable innodb_stats_on_metadata.

So what happens with TokuDB? There is an explanation from Rich Prohaska at Tokutek: “Tokudb has too much overhead for table opens. TokuDB does a calculation on the table when it is opened to see if it is empty. This calculation can be disabled when ‘tokudb_empty_scan=disabled‘. ”

So let’s see what we have with tokudb_empty_scan=disabled

select * from information_schema.tables limit 1000;
...
1000 rows in set (3 min 4.59 sec)

An impressive improvement, but still somewhat slow. Tokutek promises a fix to improve it in the next TokuDB 7.2 release.

The post rel="nofollow" href="http://www.mysqlperformanceblog.com/2014/07/09/tokudb-gotchas-slow-information_schema-tables/">TokuDB gotchas: slow INFORMATION_SCHEMA TABLES appeared first on rel="nofollow" href="http://www.mysqlperformanceblog.com/">MySQL Performance Blog.

Jul
02
2014
--

Percona Server 5.5.38-35.2 is now available

href="http://www.mysqlperformanceblog.com/wp-content/uploads/2014/05/percona_server.jpeg"> class="alignright size-thumbnail wp-image-22759" src="http://www.mysqlperformanceblog.com/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.38-35.2 on July 2, 2014 (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). Based on  rel="nofollow" href="http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-38.html" rel="nofollow">MySQL 5.5.38, including all the bug fixes in it, Percona Server 5.5.38-35.2 is now the current stable release in the 5.5 series. All of Percona‘s software is open-source and free, all the details of the release can be found in the  rel="nofollow" href="https://launchpad.net/percona-server/+milestone/5.5.38-35.2" rel="nofollow">5.5.38-35.2 milestone at Launchpad.

Bugs Fixed:

  • Fixed the duplicate string in InnoDB version number. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1328421">#1328421.
  • An uninitialized memory use in href="http://www.percona.com/doc/percona-server/5.5/diagnostics/user_stats.html#user-stats">User Statistics has been fixed. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1167486">#1167486.

Release notes for Percona Server 5.5.38-35.2 are available in our href="http://www.percona.com/doc/percona-server/5.5/release-notes/Percona-Server-5.5.38-35.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="http://www.mysqlperformanceblog.com/2014/07/02/percona-server-5-5-38-35-2-now-available/">Percona Server 5.5.38-35.2 is now available appeared first on rel="nofollow" href="http://www.mysqlperformanceblog.com/">MySQL Performance Blog.

Jul
01
2014
--

Percona Server 5.6.19-67.0 with TokuDB (GA) now available

href="http://www.mysqlperformanceblog.com/wp-content/uploads/2014/05/percona_server.jpeg"> class="alignright size-thumbnail wp-image-22759" src="http://www.mysqlperformanceblog.com/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.19-67.0 on July 1, 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.19-67.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-19.html" rel="nofollow">5.6.19, including all the bug fixes in it, Percona Server 5.6.19-67.0 is the current GA release in the Percona Server 5.6 series. All of Percona’s software 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.19-67.0" rel="nofollow">5.6.19-67.0 milestone on Launchpad.

New Features:

  • Percona has merged a contributed patch by Kostja Osipov implementing the 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 feature. This feature fixes the upstream bugs: rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=1118">#1118 and rel="nofollow" rel="nofollow" href="http://bugs.mysql.com/bug.php?id=67806">#67806.
  • TokuDB storage engine support is now considered general availability (GA) quality. The TokuDB storage engine from Tokutek improves scalability and the operational efficiency of MySQL with faster performance and increased compression. It is available as a separate package and can be installed along with the Percona Server by following title="TokuDB installation for Percona Server 5.6" href="http://www.percona.com/doc/percona-server/5.6/tokudb/tokudb_installation.html">the instructions in the release documentation.
  • Percona Server now supports the MTR --valgrind option for a server that is either statically or dynamically linked with jemalloc.

Bugs Fixed:

  • The libperconaserverclient18.1 package was missing the library files. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1329911" rel="nofollow">#1329911.
  • Percona Server introduced a regression in href="http://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.17-66.0.html">5.6.17-66.0 when support for TokuDB storage engine was initially introduced. This regression caused spurious “wrong table structure” errors for PERFORMANCE_SCHEMA tables. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1329772" rel="nofollow">#1329772.
  • Race condition in group commit code could lead to a race condition in PFS instrumentation code resulting in a server crash. Bug fixed rel="nofollow" href="https://bugs.launchpad.net/percona-server/+bug/1309026" rel="nofollow">#1309026 (upstream rel="nofollow" href="http://bugs.mysql.com/bug.php?id=72681" rel="nofollow">#72681).

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

NOTE: There was no Percona Server 5.6.18 release because there was no MySQL Community Server 5.6.18 release. That version number was used for a MySQL Enterprise Edition release to address the href="http://www.percona.com/resources/ceo-customer-advisory-heartbleed">OpenSSL “Heartbleed” issue.

Release notes for Percona Server 5.6.19-67.0 are available in the  href="http://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.19-67.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.mysqlperformanceblog.com/2014/07/01/percona-server-5-6-19-67-0-with-tokudb-ga-now-available/">Percona Server 5.6.19-67.0 with TokuDB (GA) now available appeared first on rel="nofollow" href="http://www.mysqlperformanceblog.com/">MySQL Performance Blog.

Jun
12
2014
--

Announcing Percona XtraBackup 2.2.3 GA

href="http://www.mysqlperformanceblog.com/wp-content/uploads/2013/01/Percona_XtraBackup.jpg"> class="alignleft size-full wp-image-12668" alt="Percona XtraBackup for MySQL" src="http://www.mysqlperformanceblog.com/wp-content/uploads/2013/01/Percona_XtraBackup.jpg" width="229" height="87" /> Percona is glad to announce the release of Percona XtraBackup 2.2.3 on June 12th 2014. Downloads are available from our download site href="http://www.percona.com/downloads/XtraBackup/XtraBackup-2.2.3/">here and href="http://www.percona.com/doc/percona-xtrabackup/2.2/installation.html">Percona Software Repositories.

href="http://www.percona.com/software/percona-xtrabackup">Percona XtraBackup enables 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 backup. The new 2.2.3 GA version offers improved performance, enterprise-grade security, and lower resource usage.

This release is the first GA (Generally Available) stable release in the 2.2 series.

New Features:

  • Percona XtraBackup implemented support for href="http://www.percona.com/doc/percona-server/5.6/management/backup_locks.html#backup-locks">Backup Locks.
  • Percona XtraBackup can now store href="http://www.percona.com/doc/percona-xtrabackup/2.2/innobackupex/storing_history.html#storing-history">backup history on the server itself in a special table created for that purpose.
  • Percona XtraBackup has been rebased on MySQL 5.6.17.

Bugs Fixed:

  • Fixed the InnoDB redo log incompatibility with 5.1/5.5 server and compressed tables which was introduced by the upstream fix in MySQL 5.6.11 that could make InnoDB crash on recovery when replaying redo logs created on earlier versions. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1255476">#1255476.
  • Percona XtraBackup did not flush the InnoDB REDO log buffer before finalizing the log copy. This would only become a problem when the binary log coordinates were used after restoring from a backup: the actual data files state after recovery could be inconsistent with the binary log coordinates. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1320685">#1320685.
  • innobackupex now sets wsrep_causal_reads to 0 before executing FLUSH TABLES WITH READ LOCK if the server is a member of the Galera cluster. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1320441">#1320441.
  • storage/innobase/xtrabackup/CMakeLists.txt now honors the XB_DISTRIBUTION environment variable when configuring innobackupex.pl to innobackupex. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1320441">#1320856.
  • Percona XtraBackup does not add XtraDB-specific fields when preparing a /> backup of an upstream MySQL server. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/988310">#988310.
  • Information about backup type and parameters is now stored in the /> xtrabackup_info file in the backup directory. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1133017">#1133017.
  • When backup locks are used, xtrabackup_slave_info should be written under BINLOG lock instead of TABLE lock. Bug fixed rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+bug/1328532">#1328532.

Release notes with all the bugfixes for Percona XtraBackup 2.2.3 are available in our href="http://www.percona.com/doc/percona-xtrabackup/2.2/release-notes/2.2/2.2.3.html">online documentation. Bugs can be reported on the rel="nofollow" rel="nofollow" href="https://bugs.launchpad.net/percona-xtrabackup/+filebug">launchpad bug tracker.

The post rel="nofollow" href="http://www.mysqlperformanceblog.com/2014/06/12/announcing-percona-xtrabackup-2-2-3-ga/">Announcing Percona XtraBackup 2.2.3 GA appeared first on rel="nofollow" href="http://www.mysqlperformanceblog.com/">MySQL Performance Blog.

Jun
11
2014
--

Percona Server 5.6.17-66.0 is now available

 

href="http://www.mysqlperformanceblog.com/wp-content/uploads/2014/05/percona_server.jpeg"> class="alignleft size-thumbnail wp-image-22759" src="http://www.mysqlperformanceblog.com/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.17-66.0 on June 11, 2014. Downloads are available href="http://www.percona.com/downloads/Percona-Server-5.6/Percona-Server-5.6.17-66.0/" >here and from the Percona href="http://www.percona.com/doc/percona-server/5.6/installation.html#using-percona-software-repositories">Software Repositories.

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

 

New Features:

  • MySQL benchmarks (sql-bench directory in the MySQL distribution) has been made compatible with the TokuDB storage engine.
  • Percona Server has ported MariaDB code enhancement for href="http://www.percona.com/doc/percona-server/5.6/management/start_transaction_with_consistent_snapshot.html#start-transaction-with-consistent-snapshot">start transaction with consistent snapshot. This enhancement makes binary log positions consistent with InnoDB transaction snapshots.
  • TokuDB Storage engine is now available as a separate package that can be href="http://www.percona.com/doc/percona-server/5.6/tokudb/tokudb_installation.html">installed along with the Percona Server 5.6.17-66.0. This feature is currently considered Release Candidate quality.
  • Percona Server has implemented ability to href="http://www.percona.com/doc/percona-server/5.6/management/start_transaction_with_consistent_snapshot.html#snapshot-cloning">clone a snapshot created by START TRANSACTION WITH CONSISTENT SNAPSHOT in another session.
  • Percona Server 5.6 now includes href="http://www.percona.com/doc/percona-server/5.6/performance/handlersocket.html#handlersocket-page">HandlerSocket in addition to Percona Server 5.5.

Bugs Fixed:

  • Fix for href="https://bugs.launchpad.net/percona-server/+bug/1225189" rel="nofollow">#1225189 introduced a regression in Percona Server href="http://www.percona.com/doc/percona-server/5.6/release-notes/Percona-Server-5.6.13-61.0.html">5.6.13-61.0 which could lead to an error when running mysql_install_db. Bug fixed href="https://bugs.launchpad.net/percona-server/+bug/1314596" rel="nofollow">#1314596.
  • InnoDB could crash if workload contained writes to compressed tables. Bug fixed href="https://bugs.launchpad.net/percona-server/+bug/1305364" rel="nofollow">#1305364.
  • GUI clients such as MySQL Workbench could not authenticate with a user defined with auth_pam_compat plugin. Bug fixed href="https://bugs.launchpad.net/percona-server/+bug/1166938" rel="nofollow">#1166938.
  • Help in Percona Server 5.6 command line client was linking to Percona Server 5.1 manual. Bug fixed href="https://bugs.launchpad.net/percona-server/+bug/1198775" rel="nofollow">#1198775.
  • InnoDB redo log resizing could crash when href="http://www.percona.com/doc/percona-server/5.6/management/changed_page_tracking.html">XtraDB changed page tracking was enabled. Bug fixed #1204072.
  • href="http://www.percona.com/doc/percona-server/5.6/management/audit_log_plugin.html">Audit Log wasn’t parsing escape characters correctly in the OLD format. Bug fixed #1313696.
  • Percona Server version was reported incorrectly in Debian/Ubuntu packages. Bug fixed href="https://bugs.launchpad.net/percona-server/+bug/1319670" rel="nofollow">#1319670.

Other bugs fixed: href="https://bugs.launchpad.net/percona-server/+bug/1318537" rel="nofollow">#1318537 (upstream href="http://bugs.mysql.com/bug.php?id=72615" rel="nofollow">#72615), href="https://bugs.launchpad.net/percona-server/+bug/1318874" rel="nofollow">#1318874, href="https://bugs.launchpad.net/percona-server/+bug/1285618" rel="nofollow">#1285618, href="https://bugs.launchpad.net/percona-server/+bug/1272732" rel="nofollow">#1272732, href="https://bugs.launchpad.net/percona-server/+bug/1314568" rel="nofollow">#1314568, href="https://bugs.launchpad.net/percona-server/+bug/1271178" rel="nofollow">#1271178, and href="https://bugs.launchpad.net/percona-server/+bug/1323014" rel="nofollow">#1323014.

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

The post rel="nofollow" href="http://www.mysqlperformanceblog.com/2014/06/11/percona-server-5-6-17-66-0-now-available/">Percona Server 5.6.17-66.0 is now available appeared first on rel="nofollow" href="http://www.mysqlperformanceblog.com/">MySQL Performance Blog.

Jun
04
2014
--

Why did we develop percona-agent in Go?

We recently open-sourced our href="https://github.com/percona/percona-agent" rel="nofollow">percona-agent and if you check out the source code, you’ll find that it is written in the Go programming language (aka href="http://golang.org/" rel="nofollow">Golang). For those not up to speed, the percona-agent is a real-time client-side agent for href="https://cloud.percona.com/" >Percona Cloud Tools.

Our requirements are quite demanding for our agents. This one is software that works on a real production server, so it must be fast, reliable, lightweight and easy to distribute. Surprisingly enough, binaries compiled by Go fit these characteristics.

There are of course alternatives that we considered. On the scripting side: Perl, Python, PHP, Ruby et al. These are not necessarily fast, and the distribution is also interesting. We have enough experience with href="http://www.percona.com/software/percona-toolkit" >Percona Toolkit and Perl’s “modules dependencies hell.”

On a high-end level side, there is C / C++ and I am sure we could produce an efficient agent. However we also have experience in the distribution of href="http://www.percona.com/software/percona-server" >Percona Server / href="http://www.percona.com/software/percona-xtradb-cluster" >Percona XtraDB Cluster / href="http://www.percona.com/software/percona-xtrabackup" >Percona XtraBackup. Well, I have had enough with different versions of Ubuntus, Red Hats, CentOSes and the rest of the flavors of Linux.

And, yeah, there is Java, but let me just say that we are not the Java sort of developers.

So what is so charming about Go? Go feels like a scripting language, but produces executable binaries. I see it as having the ability to attack performance issues on two sides. First is the performance of software developers: They are more productive working with scripting-like languages. Second is the performance of a final product: Native self-executable binaries are more efficient than a script running through a interpreter.

It is worth noting that href="http://golang.org/pkg/" rel="nofollow">included batteries (a set of href="http://golang.org/pkg/" rel="nofollow">packages that are coming with Go) are excellent, and in many cases that will be just enough to get you going and produce software that is quite complex. And if that is not enough, there is also a list of href="https://code.google.com/p/go-wiki/wiki/Projects" rel="nofollow">packages and projects for Go.

Of course, there are some limitations you will find in Go (some of them are temporary I hope). These are:

1. The list of supported platforms is limited… FreeBSD (release 8 and above), Linux (ARM not supported), Mac OS X and Windows. There are no packages for Solaris yet. /> 2. A good MySQL driver is still a work in progress. the most advanced is href="https://github.com/go-sql-driver/mysql" rel="nofollow">Go-MySQL-Driver /> 3. Go comes with built-in testing capabilities, but our testing enthusiast, href="http://www.percona.com/about-us/our-team/daniel-nichter" >Daniel, says it is not enough to build a complicated testing suite. /> 4. There is no support of “generics” (or “templates” if you are in C++ world). Basically it means that if you developed a data structure that works with integers, you will need to copy-paste-replace to make it working with floats. Yes, there are workarounds like using a “parent-to-everything” type “interface{}”, but often it is not efficient and just looks ugly.

There is also no automatic type-conversion between int and floats, so if you need to do complex math which involves ints and floats, you may end up with a lot back-and-forth conversions, i.e. int(math.Floor(t.epsilon*float64(t.count*2)))

To finish, I would like to invite you to my webinar, href="http://www.percona.com/resources/mysql-webinars/monitoring-all-yes-all-mysql-metrics-percona-cloud-tools" >“Monitoring All (Yes, All!) MySQL Metrics with Percona Cloud Tools” on Wednesday, June 25 at 10 a.m. Pacific Daylight Time, where I will talk on the new features in href="https://cloud.percona.com/" >Percona Cloud Tools, including our new percona-agent.

The post rel="nofollow" href="http://www.mysqlperformanceblog.com/2014/06/04/develop-percona-agent-go/">Why did we develop percona-agent in Go? appeared first on rel="nofollow" href="http://www.mysqlperformanceblog.com/">MySQL Performance Blog.

Jun
04
2014
--

Percona Toolkit 2.2.8 is now available

href="http://www.mysqlperformanceblog.com/wp-content/uploads/2013/03/Percona_ToolkitLogoVert_RGB.png"> class="alignright wp-image-13951" style="margin: 7px;" src="http://www.mysqlperformanceblog.com/wp-content/uploads/2013/03/Percona_ToolkitLogoVert_RGB-300x249.png" alt="Percona Toolkit" width="180" height="149" />

Percona is glad to announce the release of  href="http://www.percona.com/software/percona-toolkit">Percona Toolkit 2.2.8 on June 4th, 2014 (Downloads are available  href="http://www.percona.com/downloads/percona-toolkit/2.2.8/">here and from the  href="http://www.percona.com/doc/percona-server/5.5/installation.html">Percona Software Repositories). This release is the current GA (Generally Available) stable release in the 2.2 series.

New Features:

  • pt-agent has been replaced by percona-agent. More information on percona-agent can be found in the href="http://www.mysqlperformanceblog.com/2014/05/23/3-minute-mysql-monitor/">Introducing the 3-Minute MySQL Monitor blog post.
  • href="http://www.percona.com/doc/percona-toolkit/2.2/pt-slave-restart.html">pt-slave-restart now supports MySQL 5.6 global transaction IDs.
  • href="http://www.percona.com/doc/percona-toolkit/2.2/pt-table-checksum.html">pt-table-checksum now has new –plugin option which is similar to href="https://www.percona.com/doc/percona-toolkit/2.2/pt-online-schema-change.html#cmdoption-pt-online-schema-change--plugin">pt-online-schema-change –plugin

Bugs Fixed:

  • Fixed bug href="https://bugs.launchpad.net/bugs/1254233" rel="nofollow">#1254233: href="http://www.percona.com/doc/percona-toolkit/2.2/pt-mysql-summary.html">pt-mysql-summary was showing blank InnoDB section for MySQL 5.6 because it was using have_innodb variable which was removed in MySQL 5.6.
  • Fixed bug href="https://bugs.launchpad.net/bugs/965553" rel="nofollow">#965553: href="http://www.percona.com/doc/percona-toolkit/2.2/pt-query-digest.html">pt-query-digest didn’t fingerprint true/false literals correctly.
  • Fixed bug href="https://bugs.launchpad.net/bugs/1286250" rel="nofollow">#1286250: href="http://www.percona.com/doc/percona-toolkit/2.2/pt-online-schema-change.html">pt-online-schema-change was requesting password twice.
  • Fixed bug href="https://bugs.launchpad.net/bugs/1295667" rel="nofollow">#1295667: href="http://www.percona.com/doc/percona-toolkit/2.2/pt-deadlock-logger.html">pt-deadlock-logger was logging incorrect timestamp because tool wasn’t aware of the time zones.
  • Fixed bug href="https://bugs.launchpad.net/bugs/1304062" rel="nofollow">#1304062: when multiple tables were specified with href="http://www.percona.com/doc/percona-toolkit/2.2/pt-table-checksum.html#cmdoption-pt-table-checksum--ignore-tables">pt-table-checksum –ignore-tables, only one of them would be ignored.

All Percona software is free and open-source. Details of the release can be found in the  href="http://www.percona.com/doc/percona-toolkit/2.2/release_notes.html#v2-2-7-rele8sed-2014-06-04">release notes and the  href="https://launchpad.net/percona-toolkit/+milestone/2.2.8" rel="nofollow">2.2.8 milestone at Launchpad. Bugs can be reported on the Percona Toolkit href="https://bugs.launchpad.net/percona-toolkit/+filebug" rel="nofollow">launchpad bug tracker.

The post rel="nofollow" href="http://www.mysqlperformanceblog.com/2014/06/04/percona-toolkit-2-2-8-now-available/">Percona Toolkit 2.2.8 is now available appeared first on rel="nofollow" href="http://www.mysqlperformanceblog.com/">MySQL Performance Blog.

Jun
03
2014
--

Percona Server 5.5.37-35.1 is now available

href="http://www.mysqlperformanceblog.com/wp-content/uploads/2014/05/percona_server.jpeg"> class="alignright size-thumbnail wp-image-22759" src="http://www.mysqlperformanceblog.com/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.37-35.1 on June 3rd, 2014 (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). Based on  href="http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-37.html" rel="nofollow">MySQL 5.5.37, including all the bug fixes in it, Percona Server 5.5.37-35.1 is now the current stable release in the 5.5 series. All of Percona‘s software is open-source and free, all the details of the release can be found in the  href="https://launchpad.net/percona-server/+milestone/5.5.37-35.1" rel="nofollow">5.5.37-35.1 milestone at Launchpad.

Bugs Fixed:

  • InnoDB could crash if workload contained writes to compressed tables. Bug fixed href="https://bugs.launchpad.net/percona-server/+bug/1305364" rel="nofollow">#1305364.
  • GUI clients such as MySQL Workbench could not authenticate with a user defined with auth_pam_compat plugin. Bug fixed href="https://bugs.launchpad.net/percona-server/+bug/1166938" rel="nofollow">#1166938.
  • Help in Percona Server 5.5 command line client was linking to Percona Server 5.1 manual. Bug fixed href="https://bugs.launchpad.net/percona-server/+bug/1198775" rel="nofollow">#1198775.
  • href="http://www.percona.com/doc/percona-server/5.5/management/audit_log_plugin.html">Audit Log wasn’t parsing escape characters correctly in the OLD format. Bug fixed href="https://bugs.launchpad.net/percona-server/+bug/1313696" rel="nofollow">#1313696.
  • Percona Server version was reported incorrectly in Debian/Ubuntu packages. Bug fixed href="https://bugs.launchpad.net/percona-server/+bug/1319670" rel="nofollow">#1319670.

Other bugs fixed: href="https://bugs.launchpad.net/percona-server/+bug/1272732" rel="nofollow">#1272732, href="https://bugs.launchpad.net/percona-server/+bug/1219833" rel="nofollow">#1219833, href="https://bugs.launchpad.net/percona-server/+bug/1271178" rel="nofollow">#1271178, and href="https://bugs.launchpad.net/percona-server/+bug/1314568" rel="nofollow">#1314568.

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

The post rel="nofollow" href="http://www.mysqlperformanceblog.com/2014/06/03/percona-server-5-5-37-35-1-now-available/">Percona Server 5.5.37-35.1 is now available appeared first on rel="nofollow" href="http://www.mysqlperformanceblog.com/">MySQL Performance Blog.

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