Feb
08
2016
--

Percona Server 5.7.10-2 second RC available

percona_server

Percona Server 5.7.10-2Percona is glad to announce the second release candidate of Percona Server 5.7.10-2 on February 8, 2016. Download the latest version from the Percona web site or from the Percona Software Repositories.

Based on MySQL 5.7.10, including all the bug fixes in it, Percona Server 5.7.10-2 is the current Release Candidate release in the Percona Server 5.7 series. All of Percona’s software is open-source and free, all the details of the release can be found in the 5.7.10-2 milestone at Launchpad.

New Features:

  • Complete list of changes between Percona Server 5.6 and 5.7 can be seen in Changed in Percona Server 5.7.
  • 5.7 binlog group commit algorithm is now supported in TokuDB as well.
  • New TokuDB index statistics reporting has been implemented to be compatible with the changes implemented in upstream 5.7. Following the InnoDB example, the default value for tokudb_cardinality_scale_percent has been changed from 50% to 100%. Implementing this also addresses a server crash deep in the optimizer code.

Known Issues:

  • In Percona Server 5.7 super_read_only feature has been replaced with the upstream implementation. There are currently two known issues compared to Percona Server 5.6 implementation:
    • Bug #78963, super_read_only aborts STOP SLAVE if variable relay_log_info_repository is set to TABLE which could lead to a server crash in Debug builds.
    • Bug #79328, super_read_only set as a server option has no effect.
  • InnoDB crash recovery might fail if innodb_flush_method is set to ALL_O_DIRECT. The workaround is to set this variable to a different value before starting up the crashed instance (bug #1529885).

Bugs Fixed:

  • Clustering secondary index could not be created on a partitioned TokuDB table. Bug fixed #1527730 (#720).
  • Percona TokuBackup was failing to compile with Percona Server 5.7. Bug fixed #123.
  • Granting privileges to a user authenticating with PAM Authentication Plugin could lead to a server crash. Bug fixed #1521474.
  • TokuDB status variables were missing from Percona Server 5.7.10-1. Bug fixed #1527364 (#923).
  • Attempting to rotate the audit log file would result in audit log file name foo.log.%u (literally) instead of a numeric suffix. Bug fixed #1528603.
  • Adding an index to an InnoDB temporary table while expand_fast_index_creation was enabled could lead to server assertion. Bug fixed #1529555.
  • TokuDB would not be upgraded on Debian/Ubuntu distributions while performing an upgrade from Percona Server 5.6 to Percona Server 5.7 even if explicitly requested. Bug fixed #1533580.
  • Server would assert when both TokuDB and InnoDB tables were used within one transaction on a replication slave which has binary log enabled and slave updates logging disabled. Bug fixed #1534249 (upstream bug #80053).
  • MeCab Full-Text Parser Plugin has not been included in the previous release. Bug fixed #1534617.
  • Fixed server assertion caused by Performance Schema memory key mix-up in SET STATEMENT ... FOR ... statements. Bug fixed #1534874.
  • Setting the innodb_sched_priority_purge (available only in debug builds) while purge threads were stopped would cause a server crash. Bug fixed #1368552.
  • Enabling TokuDB with ps_tokudb_admin script inside the Docker container would cause an error due to insufficient privileges even when running as root. In order for this script to be used inside docker containers this error has been changed to a warning that a check is impossible. Bug fixed #1520890.
  • Write-heavy workload with a small buffer pool could lead to a deadlock when free buffers are exhausted. Bug fixed #1521905.
  • InnoDB status will start printing negative values for spin rounds per wait, if the wait number, even though being accounted as a signed 64-bit integer, will not fit into a signed 32-bit integer. Bug fixed #1527160 (upstream #79703).
  • Percona Server 5.7 couldn’t be restarted after TokuDB has been installed with ps_tokudb_admin script. Bug fixed #1527535.
  • Fixed memory leak when utility_user is enabled. Bug fixed #1530918.
  • Page cleaner worker threads were not instrumented for Performance Schema. Bug fixed #1532747 (upstream bug #79894).
  • Busy server was preferring LRU flushing over flush list flushing too strongly which could lead to performance degradation. Bug fixed #1534114.
  • libjemalloc.so.1 was missing from a binary tarball. Bug fixed #1537129.
  • When cmake/make/make_binary_distribution workflow was used to produce binary tarballs it would produce tarballs with mysql-... naming instead of percona-server-.... Bug fixed #1540385.
  • Added proper memory cleanup if for some reason a table is unable to be opened from a dead closed state. This prevents an assertion from happening the next time the table is attempted to be opened. Bug fixed #917.
  • Variable tokudb_support_xa has been modified to prevent setting it to anything but ON/ENABLED and to print a SQL warning anytime an attempt is made to change it, just like innodb_support_xa. Bug fixed #928.

Other bugs fixed: #1179451, #1534246, #1524763, #1525109 (upstream #79569), #1530102, #897, #898, #899, #900, #901, #902, #903, #905, #906, #907, #908, #909, #910, #911, #912, #913, #915, #919, and #904.

Release notes for Percona Server 5.7.10-2 are available in the online documentation. Please report any bugs on the launchpad bug tracker .

Jan
29
2016
--

Percona XtraDB Cluster 5.6.28-25.14 is now available

How to calculate the correct size of Percona XtraDB Cluster's gcache

Percona XtraDB Cluster 5.6.26-25.12Percona is glad to announce the new release of Percona XtraDB Cluster 5.6 on January 29, 2016. Binaries are available from the downloads area or from our software repositories.

Percona XtraDB Cluster 5.6.28-25.14 is now the current release, based on the following:

All of Percona software is open-source and free, and all the details of the release can be found in the 5.6.28-25.14 milestone at Launchpad.

For more information about relevant Codership releases, see this announcement.

Bugs Fixed:

  • 1494399: Fixed issue caused by replication of events on certain system tables (for example, mysql.slave_master_info, mysql.slave_relay_log_info). Replication in the Galera eco-system is now avoided when bin-logging is disabled for said tables.
    NOTE: As part of this fix, when bin-logging is enabled, replication in the Galera eco-system will happen only if BINLOG_FORMAT is set to either ROW or STATEMENT. The recommended format is ROW, while STATEMENT is required only for the pt-table-checksum tool to operate correctly. If BINLOG_FORMAT is set to MIXED, replication of events in the Galera eco-system tables will not happen even with bin-logging enabled for those tables.
  • 1522385: Fixed GTID holes caused by skipped replication. A slave might ignore an event replicated from master, if the same event has already been executed on the slave. Such events are now propagated in the form of special GTID events to maintain consistency.
  • 1532857: The installer now creates a /var/lib/galera/ directory (assigned to user nobody), which can be used by garbd in the event it is started from a directory that garbd cannot write to.

Known Issues:

  • 1531842: Two instances of garbd cannot be started from the same working directory. This happens because each instance creates a state file (gvwstate.dat) in the current working directory by default. Although garbd is configured to use the base_dir variable, it was not registered due to a bug. Until garbd is fixed, you should start each instance from a separate working directory.

Help us improve our software quality by reporting any bugs you encounter using our bug tracking system. As always, thanks for your continued support of Percona!

Jan
12
2016
--

Percona Server 5.6.28-76.1 is now available

Percona Server 5.6.28-76.1Percona is glad to announce the release of Percona Server 5.6.28-76.1 on January 12, 2016. Download the latest version from the Percona web site or from the Percona Software Repositories.

Based on MySQL 5.6.28, including all the bug fixes in it, Percona Server 5.6.28-76.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 5.6.28-76.1 milestone on Launchpad.

Bugs Fixed:

  • Clustering secondary index could not be created on a partitioned TokuDB table. Bug fixed #1527730 (DB-720).
  • When enabled, super-read-only option could break statement-based replication while executing a multi-table update statement on a slave. Bug fixed #1441259.
  • Running OPTIMIZE TABLE or ALTER TABLE without the ENGINE clause would silently change table engine if enforce_storage_engine variable was active. This could also result in system tables being changed to incompatible storage engines, breaking server operation. Bug fixed #1488055.
  • Setting the innodb_sched_priority_purge variable (available only in debug builds) while purge threads were stopped would cause a server crash. Bug fixed #1368552.
  • Small buffer pool size could cause XtraDB buffer flush thread to spin at 100% CPU. Bug fixed #1433432.
  • Enabling TokuDB with ps_tokudb_admin script inside the Docker container would cause an error due to insufficient privileges even when running as root. In order for this script to be used inside Docker containers this error has be been changed to a warning that a check is impossible. Bug fixed #1520890.
  • InnoDB status will start printing negative values for spin rounds per wait, if the wait number, even though being accounted as a signed 64-bit integer, will not fit into a signed 32-bit integer. Bug fixed #1527160 (upstream #79703).

Other bugs fixed: #1384595 (upstream #74579), #1384658 (upstream #74619), #1471141 (upstream #77705), #1179451, #1524763 and #1530102.

Release notes for Percona Server 5.6.28-76.1 are available in the online documentation. Please report any bugs on the launchpad bug tracker .

Jan
12
2016
--

Percona Server 5.5.47-37.7 is now available

Percona Server 5.5.47-37.7
Percona is glad to announce the release of Percona Server 5.5.47-37.7 on January 12, 2016. Based on MySQL 5.5.47, including all the bug fixes in it, Percona Server 5.5.47-37.7 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 5.5.47-37.7 milestone on Launchpad. Downloads are available here and from the Percona Software Repositories.

Bugs Fixed:

  • Running OPTIMIZE TABLE or ALTER TABLE without the ENGINE clause would silently change table engine if enforce_storage_engine variable was active. This could also result in system tables being changed to incompatible storage engines, breaking server operation. Bug fixed #1488055.

Other bugs fixed: #1179451, #1524763, and #1530102.

Release notes for Percona Server 5.5.47-37.7 are available in our online documentation. Bugs can be reported on the launchpad bug tracker.

Jan
11
2016
--

Percona XtraDB Cluster 5.6.27-25.13 is now available

Percona XtraBackup Logo

Percona XtraDB Cluster 5.6.26-25.12Percona is glad to announce the new release of Percona XtraDB Cluster 5.6 on January 11, 2016. Binaries are available from the downloads area or from our software repositories.

Percona XtraDB Cluster 5.6.27-25.13 is now the current release, based on the following:

All of Percona software is open-source and free, and all the details of the release can be found in the 5.6.26-25.12 milestone at Launchpad.

For more information about relevant Codership releases, see this announcement.

NOTE: Due to new dependency on libnuma1 package in Debian/Ubuntu, please run one of the following commands to upgrade the percona-xtradb-cluster-server-56 package:

  • aptitude safe-upgrade
  • apt-get dist-upgrade
  • apt-get install percona-xtradb-cluster-server-5.6

New Features:

  • There is a new script for building Percona XtraDB Cluster from source. For more information, see Compiling and Installing from Source Code.
  • wsrep_on is now a session only variable. That means toggling it will not affect other clients connected to said node. Only the session/client modifying it will be affected. Trying to toggle wsrep_on in the middle of a transaction will now result in an error. Trx will capture the state of wsrep_on during start and will continue to use it. Start here means when the first logical changing statement is executed within transaction context.

Bugs Fixed:

  • #1261688 and #1292842: Fixed race condition when two skipped replication transactions were rolled back, which caused [ERROR] WSREP: FSM: no such a transition ROLLED_BACK ->ROLLED_BACK with LOAD DATA INFILE
  • #1362830: Corrected xtrabackup-v2 script to consider only the last specified log_bin directive in my.cnf. Multiple log_bin directives caused SST to fail.
  • #1370532: Toggling wsrep_desync while node is paused is now blocked.
  • #1404168: Removed support for innodb_fake_changes variable.
  • #1455098: Fixed failure of LDI on partitioned table. This was caused by partitioned table handler disabling bin-logging and Native Handler (InnoDB) failing to generate needed bin-logs eventually causing skipping of statement replication.
  • #1503349: garbd now uses default port number if it is not specified in sysconfig.
  • #1505184: Corrected wsrep_sst_auth script to ensure that user name and password for SST is passed to XtraBackup through internal command-line invocation. ps -ef doesn’t list these credentials so passing it internally is fine, too.
  • #1520491: FLUSH TABLE statements are not replicated any more, because it lead to an existing upstream fix pending deadlock error. This fix also takes care of original fix to avoid increment of local GTID.
  • #1528020: Fixed async slave thread failure caused by redundant updates of mysql.event table with the same value. Redundant updates are now avoided and will not be bin-logged.
  • Fixed garb init script causing new UUIDs to be generated every time it runs. This error was due to missing base_dir configuration when gardb didn’t have write-access to current working directory. garbd will now try to use cwd. Then it will try to use /var/lib/galera (like most Linux daemons). If it fails to use or create /var/lib/galera, it will throw a fatal error.
  • Fixed replication of DROP TABLE statement with a mix of temporary and non-temporary tables (for example, DROP TABLE temp_t1, non_temp_t2), which caused errorneous DROP TEMPORARYTABLE stmt on replicated node. Corrected it by detecting such scenarios and creating temporary table on the replicated node, which is then dropped by follow-up DROP statement. All this workload should be part of same unit as temporary tables are session-specific.
  • Fixed error when wsrep_cluster_name value over 32 characters long caused gmcast message to exceed maximum length. Imposed a limit of 32 character on wsrep_cluster_name.
  • Added code to properly handle default values for wsrep_* variables, which caused an error/crash.
  • Fixed error when a CREATE TABLE AS SELECT (CTAS) statement still tried to certify a transaction on a table without primary key even if certification of tables without primary key was disabled. This error was caused by CTAS setting trx_id (fake_trx_id) to execute SELECT and failing to reset it back to -1 during INSERT as certification is disabled.
  • Fixed crashing of INSERT .... SELECT for MyISAM table with wsrep_replicate_myisam set to ON. This was caused by TOI being invoked twice when source and destination tables were MyISAM.
  • Fixed crash when caching write-set data beyond configured limit. This was caused by TOI flow failing to consider/check error resulting from limit enforcement.
  • Fixed error when loading MyISAM table from schema temporary table (with wsrep_replicate_myisam set to ON). This was caused by temporary table lookup being done usingget_table_name(), which could be misleading as table_name for temporary tables is set to temporary generated name. Original name of the table is part of table_alias. The fix corrected condition to consider both table_name and alias_name.
  • Fixed error when changing wsrep_provider in the middle of a transaction or as part of a procedure/trigger. This is now blocked to avoid inconsistency.
  • Fixed TOI state inconsistency caused by DELAYED_INSERT on MyISAM table (TOI_END was not called). Now the DELAYED_ qualifier will be ignored and statement will be interpreted as normal INSERT.
  • Corrected locking semantics for FLUSH TABLES WITH READ LOCK (FTWRL). It now avoids freeing inheritted lock if follow-up FLUSH TABLE statement fails. Only frees self-acquired lock.
  • Fixed crash caused by GET_LOCK + wsrep_drupal_282555_workaround. GET_LOCK path failed to free all instances of user-level locks after it inherited multiple-user-locks from Percona Server. The cleanup code now removes all possible references of locks.
  • Fixed cluster node getting stuck in Donor/Desync state after a hard recovery, because of an erroneous type cast in source code.
  • Corrected DDL and DML semantics for MyISAM:
    • DDL (CREATE/DROP/TRUNCATE) on MyISAM will be replicated irrespective of wsrep_replicate_miysam value
    • DML (INSERT/UPDATE/DELETE) on MyISAM will be replicated only if wsrep_replicate_myisam is enabled
    • SST will get full transfer irrespective of wsrep_replicate_myisam value (it will get MyISAM tables from donor if any)
    • Difference in configuration of pxc-cluster node on enforce_storage_engine front may result in picking up different engine for same table on different nodes
    • CREATE TABLE AS SELECT (CTAS) statements use non-TOI replication and are replicated only if there is involvement of InnoDB table that needs trx (involvement of MyISAM table will cause CTAS statement to skip replication)

Known Issues:

  • 1330941: Conflict between wsrep_OSU_method set to RSU and wsrep_desync set to ON was not considered a bug.
  • 1443755: Causal reads introduces surprising latency in single node clusters.
  • 1522385: Holes are introduced in Master-Slave GTID eco-system on replicated nodes if any of the cluster nodes are acting as asynchronous slaves to an independent master.
  • SST fails with innodb_data_home_dir/innodb_log_home_dir. This is a bug in Percona XtraBackup. It should be fixed in the next 2.3.2 release. Until then, please use 2.2.12 that doesn’t have this issue.
  • Enabling wsrep_desync (from previous OFF state) will wait until previous wsrep_desync=OFF operation is completed.

Help us improve our software quality by reporting any bugs you encounter using our bug tracking system. As always, thanks for your continued support of Percona!

Jan
04
2016
--

Percona Server for MongoDB 3.0.8-1.2 is now available

psmdb-logo

Percona Server for MongoDBPercona is pleased to announce the release of Percona Server for MongoDB 3.0.8-1.2 on January 4, 2016. Download the latest version from the Percona web site or from the Percona Software Repositories.

Percona Server for MongoDB is an enhanced, open source, fully compatible, highly scalable, zero-maintenance downtime database supporting the MongoDB v3.0 protocol and drivers. Based on MongoDB 3.0.8, it extends MongoDB with MongoRocks and PerconaFT storage engines, as well as features like external authentication and audit logging. Percona Server for MongoDB requires no changes to MongoDB applications or code.

 


New Features:

  • Added support for Ubuntu 15.10 (Wily Werewolf)
  • Contains all changes and fixes from MongoDB 3.0.8

Percona Server for MongoDB 3.0.8-1.2 release notes are available in the official documentation.

Dec
17
2015
--

Percona XtraBackup 2.3.3 is now available

Percona XtraBackup 2.3.3 for MySQL Percona is glad to announce the release of Percona XtraBackup 2.3.3 on December 17th, 2015. Downloads are available from our download site or Percona Software Repositories.

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 is the current GA (Generally Available) stable release in the 2.3 series.

Bugs Fixed:

  • Database directories were not removed if DROP DATABASE happened during the backup. Bug fixed #1461735.
  • Backup would fail if Store backup history on the server feature was enabled and backup was taken from server without binary log enabled. Bug fixed #1509812.
  • Percona XtraBackup now fails with descriptive error message if --defaults-extra-file option is not specified first. Bug fixed #1511451.
  • Backup would fail if --rsync option was used without specifying temporary folder. Bug fixed #1511701.
  • Fixed Percona XtraBackup crash which happened when it was used for SST on MariaDB Galera Cluster caused by double free of datadir variable. Bug fixed #1512281.
  • --move-back option did not respect the innodb_log_group_home_dir and innodb_data_home_dir options which caused ib_logfiles and data files not to be moved back to correct location. Bug fixed #1512616.
  • xtrabackup_binlog_info was not updated correctly when applying incremental backups. Bug fixed #1523687.
  • When using a --defaults-file option Percona XtraBackup would complain about datadir being mismatched if it wasn’t explicitly set in the defaults file. Bug fixed #1508448.
  • Fixed build issues by adding missing check in cmake script for xxd presence. Bug fixed #1511267.
  • Percona XtraBackup would terminate backup process without error if --slave-info option was used on a server not running as a replication slave. Bug fixed #1513520.
  • innobackupex when used with --stream option would create an empty directory with a timestamp as a name. Bug fixed #1520569.

Other bugs fixed #1523728 and #1507238.

Release notes with all the bugfixes for Percona XtraBackup 2.3.3 are available in our online documentation. Bugs can be reported on the launchpad bug tracker.

The post Percona XtraBackup 2.3.3 is now available appeared first on MySQL Performance Blog.

Dec
14
2015
--

Percona Server 5.7.10-1 first RC available

Percona Server 5.7.10-1Percona is glad to announce the first release candidate of Percona Server 5.7.10-1 on December 14, 2015. Download the latest version from the Percona web site or from the Percona Software Repositories.

This release contains all the bug fixes from latest Percona Server 5.6 release (currently Percona Server 5.6.27-76.0).

New Features:

  • Percona Server 5.7.10-1 is not available on RHEL 5 family of Linux distributions and Debian 6 (squeeze).
  • Complete list of changes between Percona Server 5.6 and 5.7 can be seen in Changed in Percona Server 5.7.

Known Issues:

  • MeCab Full-Text Parser Plugin has not been included in this release.
  • PAM Authentication Plugin currently isn’t working correctly.
  • Variables innodb_show_verbose_locks and innodb_show_locks_help are not working correctly.
  • In Percona Server 5.7 super_read_only feature has been replaced with upstream implementation. There are currently two known issues compared to Percona Server 5.6 implementation:
    • Bug #78963, super_read_only aborts STOP SLAVE if variable relay_log_info_repository is set to TABLE which could lead to a server crash in Debug builds.
    • Bug #79328, super_read_only set as a server option has no effect.
  • Using primary key with a BLOB in TokuDB table could lead to a server crash (bug #916).
  • Using XA transactions with TokuDB could lead to a server crash (bug #900).
  • To install TokuDB on CentOS/RHEL 7 you’ll need to add the line LD_PRELOAD=/usr/lib64/libjemalloc.so.1 to /etc/sysconfig/mysql before running the ps_tokudb_admin script
  • Percona Tokubackup has not been included in this release.

Bugs Fixed:

  • Running ALTER TABLE without specifying the storage engine (without ENGINE= clause) or OPTIMIZE TABLE when enforce_storage_engine was enabled could lead to unrequested and unexpected storage engine changes. If done for a system table, it would circumvent regular system table storage engine compatibility checks, resulting in crashes or otherwise broken server operation. Bug fixed #1488055.
  • Some transaction deadlocks did not increase the INFORMATION_SCHEMA.INNODB_METRICS lock_deadlocks counter. Bug fixed #1466414 (upstream #77399).
  • Removed excessive locking during the buffer pool resize when checking whether AHI is enabled. Bug fixed #1525215 (upstream #78894).
  • Removed unnecessary code in InnoDB error monitor thread. Bug fixed #1521564 (upstream #79477).

Other bugs fixed: #371752 (upstream #45379), #1441362 (upstream #56155), #1385062 (upstream #74810), #1519201 (upstream #79391), #1515602, #1506697 (upstream #57552), #1501089 (upstream #75239), #1447527 (upstream #75368), #1384658 (upstream #74619), #1384656 (upstream #74584), and #1192052.

Release notes for Percona Server 5.7.10-1 are available in the online documentation. Please report any bugs on the launchpad bug tracker .

The post Percona Server 5.7.10-1 first RC available appeared first on MySQL Performance Blog.

Dec
13
2015
--

Percona Server for MongoDB 3.0.7-1.0 is now available

psmdb-logoPercona is pleased to announce the GA release of Percona Server for MongoDB 3.0.7-1.0 on December 14, 2015. Download the latest version from the Percona web site or from the Percona Software Repositories.

Percona Server for MongoDB is an enhanced, open source, fully compatible, highly scalable, zero-maintenance downtime database supporting the MongoDB v3.0 protocol and drivers. Based on MongoDB 3.0.7, it extends MongoDB with MongoRocks and PerconaFT storage engines, as well as features like external authentication and audit logging. Percona Server for MongoDB requires no changes to MongoDB applications or code.

 

NOTE: The MongoRocks engine included in this release is based on RocksDB 4.0.0. For more information, see the RocksDB changelog.


 

New Features:

  • Percona TokuBackup is an integrated open-source hot backup system for MongoDB servers running the PerconaFT storage engine (including Percona Server for MongoDB)
  • Concurrency optimization for lock-managed storage engines, such as PerconaFT. Pre-locking document ranges on index scans greatly improves performance of such engines.

Bug Fixes:

  • PSMDB-18: Changed the default data directory (dbpath) to /var/lib/mongo for RHEL/CentOS.
  • PSMDB-28: Fixed an Invariant failure when creating a sparse index with the WiredTiger storage engine.

Build and Packaging Fixes:

  • BLD-331: Fixed the service mongod stop command for Debian.
  • BLD-332: Fixed logic for percona-server-mongodb-helper.sh script to correctly handle Transparent Huge Pages.
  • BLD-343: Added the postrm script with appropriate logic to handle proper data files removal when running apt-get purge.
  • BLD-344: Switched to new YAML configuration format.
  • BLD-369: Changed the mongod installation path to /usr/bin.
  • Fixed the mongod system group creation command.

PerconaFT Fixes:

  • FT-456: Serialized FT fanout to disk
  • FT-675: Removed unnecessary assertion on setlocale() success in ctest suite
  • FT-681: Fixed transactional inconsistency with rollback
  • FT-682: Reduced the amount of malloc_usable_size() calls
  • FT-684: Implemented a logical row count mechanism to make the estimated number of rows reflect the actual number of rows in heavily used tables
  • FT-685: Introduced branch prediction macros
  • FT-688: Changed licensing and naming from Tokutek to Percona
  • FT-690: Fixed reserved_filenum overflow
  • FT-692: Added a dummy field to make sizeof(DB_LSN) equal in C and C++
  • FT-699: Added and replaced field initializers that caused build fails
  • FT-702: Replaced the ZERO_COND_INITIALIZER definition with an empty brace pair intializer to stop build fails
  • Fixed memory leak due to data race in context status initialization
  • Fixed memory leak found with address sanitizer
  • Fixed assert in circular buffer assert caused by race
  • Improved database creation time
  • Implemented grabbing of evictor mutex when signaling the evictor condition variable

Percona Server for MongoDB 3.0.7-1.0 release notes are available in the official documentation.

The post Percona Server for MongoDB 3.0.7-1.0 is now available appeared first on MySQL Performance Blog.

Dec
04
2015
--

Percona Server 5.6.27-76.0 is now available

Percona ServerPercona is glad to announce the release of Percona Server 5.6.27-76.0 on December 4, 2015. Download the latest version from the Percona web site or from the Percona Software Repositories.

Based on MySQL 5.6.27, including all the bug fixes in it, Percona Server 5.6.27-76.0 is the current GA release in the Percona Server 5.6 series. Percona Server is open-source and free – and this is the latest release of our enhanced, drop-in replacement for MySQL. Complete details of this release can be found in the 5.6.27-76.0 milestone on Launchpad.

New Features:

  • SHOW SLAVE STATUS NOLOCK syntax in 5.6 has been undeprecated. Both SHOW SLAVE STATUS NOLOCK and SHOW SLAVE STATUS NONBLOCKING are now supported. Percona Server originally used SHOW SLAVE STATUS NOLOCK syntax for this feature. As of 5.6.20-68.0 release, Percona Server implements SHOW SLAVE STATUS NONBLOCKING syntax, which comes from early MySQL 5.7. Current MySQL 5.7 does not have this syntax and regular SHOW SLAVE STATUS is non-blocking.
  • TokuDB tables can now be automatically analyzed in the background based on a measured change in data.
  • Percona Server has implemented new tokudb_strip_frm_data variable which can be used to assist in TokuDB data recovery. WARNING: Use this variable only if you know what you’re doing otherwise it could lead to data loss.

Bugs Fixed:

  • Setting the tokudb_backup_last_error_string and tokudb_backup_last_error values manually could cause server assertion. Bug fixed #1512464.
  • Fixed invalid memory accesses when mysqldump was running with --innodb-optimize-keys option. Bug fixed #1517444.
  • Fixed incorrect filename specified in storage/tokudb/PerconaFT/buildheader/CMakeLists.txt which could cause subsequent builds to fail. Bug fixed #1510085 (Sergei Golubchik).
  • Fixed multiple issues with TokuDB CMake scripts. Bugs fixed #1510092, #1509219 and #1510081 (Sergei Golubchik).
  • An upstream fix for upstream bug #76135 might cause server to stall or hang. Bug fixed #1519094 (upstream #79185).
  • ps_tokudb_admin now prevents Percona TokuBackup activation if there is no TokuDB storage engine on the server. Bug fixed #1520099.
  • Percona TokuBackup plugin now gets removed during the TokuDB storage engine uninstall process. Bug fixed #1520472.
  • New --defaults-file option has been implemented for ps_tokudb_admin to specify the MySQL configuration file if it’s not in the default location. Bug fixed #1517021.

Other bugs fixed: #1425480, #1517523, #1515741 and #1513178.

Release notes for Percona Server 5.6.27-76.0 are available in the online documentation. Please report any bugs on the launchpad bug tracker .

The post Percona Server 5.6.27-76.0 is now available appeared first on MySQL Performance Blog.