Aug
21
2017
--

Percona Server for MongoDB 3.2.16-3.6 is Now Available

Percona Server for MongoDB 3.2

Percona Server for MongoDB 3.2Percona announces the release of Percona Server for MongoDB 3.2.16-3.6 on August 21, 2017. Downloads are available here and from the Percona Software Repositories.

Percona Server for MongoDB is a highly scalable, zero-maintenance downtime database supporting the MongoDB v3.2 protocol and drivers. It extends MongoDB with MongoRocks and Percona Memory Engine storage engines, as well as several enterprise features. Percona Server for MongoDB requires no changes to MongoDB applications or code.

Note:

Percona deprecated the PerconaFT storage engine. Future releases won’t contain this engine.

This release is based on MongoDB 3.2.16 and does not include any additional changes.

Aug
01
2017
--

Percona Server for MySQL 5.6.36-82.1 is Now Available

Percona Server for MySQL 5.6

Percona Server for MySQL 5.6Percona is glad to announce the release of Percona Server for MySQL 5.6.36-82.1 on August 1, 2017 (Downloads are available here and from the Percona Software Repositories).

Based on MySQL 5.6.36, including all the bug fixes in it, Percona Server for MySQL 5.6.34-79.1 is the current GA release in the Percona Server for MySQL 5.6 series. All of Percona‘s software is open-source and free, all the details of the release can be found in the 5.6.36-82.1 milestone at Launchpad.

Please note that RHEL 5, CentOS 5 and Ubuntu versions 12.04 and older are not supported in future releases of Percona Server for MySQL and no further packages are added for these distributions.

New Features

  • Percona Server for MySQL can now be built with support of OpenSSL 1.1.
  • Percona Server for MySQL is now available on Debian 9 (stretch). The support only covers the amd64 architecture.
  • TokuDB enables to kill a query that is awaiting an FT locktree lock.

Bugs Fixed

  • Row counts in TokuDB could be lost intermittently after restarts. Bug fixed #2.
  • In TokuDB, two races in the fractal tree lock manager could significantly affect transactional throughput for some applications that used a small number of concurrent transactions. These races manifested as transactions unnecessarily waiting for an available lock. Bug fixed #3.
  • TokuDB could assert when opening a dictionary with no useful information to error log. Bug fixed #23.
  • TokuDB could assert for various reasons deserializing nodes with no useful error output. Bug fixed #24.
  • Percona Server could crash when running a query over a partitioned table that uses an index to read a range of rows if this range was not covered by any existing partition. Bug fixed #1657941 (upstream #76418).
  • With two client connections to a server (debug server build), the server could crash after one of the clients set the global option userstat and flushed the client statistics (FLUSH CLIENT_STATISTICS) and then both clients were closed. Bug fixed #1661488.
  • TokuDB did not pass cmake flags on to snappy cmake. Bug fixed #41. The progress status for partitioned TokuDB table ALTERs was misleading. Bug fixed #42.
  • When a client application is connecting to the Aurora cluster end point using SSL (--ssl-verify-server-cert or --ssl-mode=VERIFY_IDENTITY option), wildcard and SAN enabled SSL certificates were ignored. See also Compatibility Matrix. Note that the --ssl-verify-server-cert option is deprecated in Percona Server 5.7. Bug fixed #1673656 (upstream #68052).
  • Killing a stored procedure execution could result in an assert failure on a debug server build. Bug fixed #1689736 (upstream #86260).
  • It was not possible to build Percona Server on Debian 9 (stretch) due to issues with OpenSSL 1.1. Bug fixed #1702903 (upstream #83814).
  • The SET STATEMENT .. FOR statement changed the global instead of the session value of a variable if the statement occurred immediately after the SET GLOBAL or SHOW GLOBAL STATUS command. Bug fixed #1385352.
  • The synchronization between the LRU manager and page cleaner threads was not done at shutdown. Bug fixed #1689552.

Other bugs fixed: #6#44#65#1160986#1676740#1689989#1689998#1690012#1699788, and #1684601 (upstream #86016).

Compatibility Matrix

Feature YaSSL OpenSSL < 1.0.2 OpenSSL >= 1.0.2
‘commonName’ validation Yes Yes Yes
SAN validation No Yes Yes
Wildcards support No No Yes
Jul
13
2017
--

BloomAPI locks down $2.4M to fix medical record releases

 Seattle-based BloomAPI is announcing a $2.4 million seed round this morning for its solution to the broken medical records release process. It’s no secret that the entire U.S. healthcare system is held back by antiquated technology — but unlike many competitors, BloomAPI offers a solution that works with, and not against, the old-school technologies. Read More

Jun
19
2017
--

MariaDB Server 10.2 GA Release Overview

MariaDB Server 10.2

MariaDB Server 10.2This blog post looks at the recent MariaDB Server 10.2 GA release.

Congratulations to the MariaDB Foundation for releasing a generally available (GA) stable version of MariaDB Server 10.2! We’ll definitely spend the next few weeks talking about MariaDB Server 10.2, but here’s a quick overview in the meantime. Keep in mind that when thinking about compatibility, this is meant to be the equivalent of MySQL 5.7 (GA: October 21, 2015, with Percona Server for MySQL 5.7 GA available February 23, 2016).

Some of the highlights include:

  • Window functions – this is the first release in the MySQL ecosystem that includes Window functions and Recursive Common Table Expression. At the time of this writing, MariaDB hasn’t completed the documentation. It is worth noting that the implementation of Window functions in MariaDB Server 10.2 differs from what you see in MariaDB ColumnStore.
  • JSON functions – Many JSON functions to query, update, index and validate JSON. It’s worth noting that MariaDB Server 10.2 does not include a JSON data type as compared to MySQL 5.7). This means you can’t do CREATE TABLE t1 (jdoc JSON) – instead you need to use a VARCHAR or TEXT column. There are also other differences that produce different result sets, and seemingly no column path operator.
  • There is also support for GeoJSON functionality, but when we tried ST_AsGeoJSON (yes, documentation needs work), we noticed that the output could vary from MySQL 5.7.
  • MyRocks – MariaDB added the hot new storage engine MyRocks as an alpha. You will have to install the MyRocks engine package separably. It isn’t fully merged yet. Watch the umbrella task MDEV-9658.
  • SHOW CREATE USER – A new SHOW CREATE USER statement allows you to look at user limitation, as you can now limit users to a maximum number of queries, updates and connections per hour, as well as a maximum number of connections permitted by the user (see setting account resource limits for the MySQL 5.7 equivalent). You’ll want to read the updated documentation around CREATE USER. Don’t be surprised when you see something like “ERROR 1226 (42000): User ‘foo’ has exceeded the ‘max_user_connections’ resource (current value: 1)”. This also is an extension to ALTER USER.
  • Flashback – binary log based rollback, aka flashback, can rollback tables and databases to an older snapshot. This should help when the DBA or a user makes an error. This tool works well as long as its a DML statement. This feature came from Alibaba’s AliSQL tree.
  • Time delayed replication – new in MariaDB Server 10.2.
  • OpenSSL 1.1 – now there is support for OpenSSL 1.1, LibreSSL
  • MariaDB Connector/C – most importantly, MariaDB Connector/C replaces libmysql (see: MDEV-9055). This should be API and ABI compatible, but naturally there are some teething problems (see: MDEV-12950).
  • Amazon Key Management plugin – from a key management standpoint, the Amazon Key Management plugin is now available to use for encryption. It’s compiled and available as a package. Previously, you had to compile it yourself.

Some of the important things to take note of are:

  • As of this release, MariaDB now ships with InnoDB as the default storage engine (as opposed to Percona XtraDB). This means that from here on out, the improvements and fixes to Percona XtraDB won’t necessarily be available in MariaDB. This also means that Percona XtraDB parameters might get ignored (as reported in MDEV-12472).
  • In MySQL 5.6+, you can use SHA-256 pluggable authentication. However, this features is still not implemented in MariaDB Server 10.2 (see: MDEV-9804). You can use the ed25519 authentication plugin as a replacement, however.
  • When it comes to replication, MySQL 5.7 defaults to row-based replication. MariaDB Server 10.2 defaults to mixed-mode replication (see the discussion around this at MDEV-7635).
  • It is worth noting that in order to make MariaDB Server more “Oracle compatible,” DECIMAL now goes up to 38 decimals instead of 30 decimals. MDEV-10138 tells you what happens when you migrate from a long decimal to a default decimal type install (i.e., if you’re moving to another variant in the MySQL ecosystem).
  • If you’re familiar with how MySQL 5.7 manages passwords and a new install, the MariaDB Server 10.2 method hasn’t changed.

All in all, this release took a little over a year to make (Alpha was 18 April 2016, GA was 23 May 2017). It is extremely important to read the release notes and the changelogs of each and every release, as MariaDB Server diverges from MySQL quite a bit. At Percona, we will monitor Jira closely to ensure that you always stay informed of the latest changes.

Dec
21
2012
--

Announcing Percona XtraBackup 1.6.7

Percona is glad to announce the latest stable release of Percona XtraBackup 1.6.7 on December 20th, 2012 (Downloads are available here).

This release is purely composed of bug fixes to the previous stable release of Percona XtraBackup. New users should head for Percona XtraBackup 2.0 rather than 1.6.

Bugs Fixed:

  • xtrabackup_binary was not included in tar archive when streaming, instead it was written to the current directory. This could lead to a wrong xtrabackup binary being used when preparing backups created with the --stream or --remote-host options. Bugs fixed #723318 and #787988 (Stewart Smith).
  • FLUSH TABLES WITH READ LOCK was not used when creating incremental backups, which could lead to inconsistent backups when updates to non-InnoDB tables or DDL statements on any tables occurred during the backup process. Bug fixed #771981 (Alexey Kopytov).
  • Option --safe-slave-backup was resulting in incorrect binlog info, because in some cases innobackupex confused the response from SHOW SLAVE STATUS with the one from SHOW MASTER STATUS. Bug fixed #977101 (Alexey Kopytov).
  • innodb_data_file_path was not written to backup-my.cnf, this was a regression introduced in XtraBackup 1.6.5. Bug fixed #983685 (Sergei Glushchenko).
  • Fixed spurious test suite failures with grep 2.10. Bug fixed #996483 (Alexey Kopytov).
  • When innobackupex was running with --apply-log, it was reading configuration from the server configuration file instead of backup-my.cnf in backup directory. Bug fixed #996493 (Sergei Glushchenko).
  • innobackupex could copy files to a wrong directory when merging an incremental backup to a full one. Bug fixed #1002688 (Alexey Kopytov).
  • XtraBackup binary was leaking file descriptors on --backup. This was fixed by reusing the existing file descriptor so no leak occurs. Bug fixed #713267 (Alexey Kopytov).

The full release notes and details about fixed bugs are available in the release notes.

The post Announcing Percona XtraBackup 1.6.7 appeared first on MySQL Performance Blog.

Feb
16
2011
--

Percona Server 5.5.8 Beta Release

It’s finally here! Percona Server Percona Server 5.5.8-20.0 is now available for download. This is a beta release of Percona’s enhancements to the MySQL 5.5.8 server. Here are some highlights:

  • Performance and scalability improvements throughout the server and storage engine
  • Optimizations for flash storage such as SSD, Virident, and FusionIO
  • Optimizations for cloud computing
  • The HandlerSocket plugin for NoSQL access
  • There’s an Amazon OS repository, as well as Yum and Apt repositories
  • Improvements to replication, partitioning, stored procedures
  • More diagnostics and tunability
  • More pluggability, including pluggable authentication


In addition to building on MySQL 5.5, here are the changes we’ve made from previous Percona Server releases:

New Features

Variable Changes

Other Changes

  • Additional information was added to the LOG section of the SHOW STATUS command. Bug fixed: #693269. (Yasufumi Kinoshita)
  • The SHOW PATCHES command was removed. (Vadim Tkachenko)
  • The INFORMATION_SCHEMA table XTRADB_ENHANCEMENTS was removed. (Yasufumi Kinoshita)
  • Several fields in the INFORMATION_SCHEMA table INNODB_INDEX_STATS were renamed. Bug fixed: #691777. (Yasufumi Kinoshita)
  • The XtraDB version was set to 20.0. (Aleksandr Kuzminsky)
  • Many InnoDB compilation warnings were fixed. Bug fixed:#695273. (Yasufumi Kinoshita)
  • An Amazon OS repository was created. Bug fixed: #691996. (Aleksandr Kuzminsky)

For more information, please see the following links:

Jan
11
2011
--

Percona Server 5.1.54-12.5

Percona Server version 5.1.54-12.5 is now available for download. It is now the current stable release version.

Functionality Added or Changed

Bugs Fixed

  • Bug #689830 – The development environment tests of show_slave_status_nolock work only on statement-based replication. They were failing when row-based replication was attempted. A check is now made for the replication type to test. (Oleg Tsarev)
  • Bug #688643, Bug #691234 – Boolean command line options and configuration variables in the slow_extended patch were not being processed properly.  (Oleg Tsarev)
  • Bug #692211 – Starting the server with a non-zero innodb_auto_lru_dump value could crash the server if the dump file did not exist. (Alexey Kopytov)

For more information, please see the following links:

Dec
29
2010
--

Percona Server 5.1.53-12.4

Percona Server version 5.1.53-12.4 is now available for download. It is now the current stable release version.

Functionality Added or Changed

  •  Percona Server 5.1.53-12.4 is based on MySQL 5.1.53.
  •  New Features Added:
    • Precompiled UDFs for Maatkit (FNV and MurmurHash hash functions to provide faster checksums) are now included in distributions. Fixes feature request #689992. (Aleksandr Kuzminsky)
  •  Other Changes:
    • innodb_doublewrite_file – It’s no longer necessary to recreate your database and InnoDB system files when a dedicated file to contain the doublewrite buffer is specified. (Yasufumi Kinoyasu)

Bugs Fixed

  • Bug #643149 – Slow query log entries were not written in the usual parsing format. (Alexey Kopytov)
  • Bug #671764innochecksum wasn’t distributed with RPM and .DEB packages. (Aleksandr Kuzminsky)
  • Bug #673426 – Use of these system variables as command-line options could cause a crash or undefined behavior: log_slow_timestamp_every, log_slow_sp_statements, slow_query_log_microseconds_timestamp, use_global_long_query_time. (Oleg Tsarev)
  • Bug #673567 – Compiler could produce spurious warnings when building on non_Linux platforms. A check is now made to see if clock_gettime() is present in librt at the configure stage. If yes, -lrt is added to LIBS. (Alexey Kopytov)
  • Bug #673929 – Query cache misses were being reported for some queries when hits were actually occurring. (Oleg Tsarev)
  • Bug #676146 – The development environment test of log_slow_verbosity=innodb on a slave for row-based replication was not working correctly. (Oleg Tsarev)
  • Bug #676147, Bug #676148 – The development environment tests of options log_slow_slave_statements and use_global_long_query_time work only on statement-based replication. They were failing when row-based replication was attempted. A check is now made for the replication type to test. (Oleg Tsarev)
  • Bug #676158 – Setting the query cache size to 512M caused test failure on low memory systems. (Aleksandr Kuzminsky)
  • Bug #677407 – The innodb.innodb_information_schema test could fail sporadically due to flawed logic in the INFORMATION_SCHEMA.INNODB_LOCKS caching mechanism. (contributed by Kristian Nielsen) (Alexey Kopytov)
  • Bug #681486 – A dependency between Debian packages libmysqlclient16 and percona-server-common was removed. (Aleksandr Kuzminsky)
  • Bug #693415 – The test percona_innodb_buffer_pool_shm was failing. It should be run with the --big-test option. As the buffer pool size used in the test is 128M, the shared memory segment should be increased appropriately in order to run the test successfully. (Aleksandr Kuzminsky)
  • Bug #693814, Bug #693815, Bug #693816, Bug #693817, Bug #693819 – Tests in the test environment were updated to reflect past INFORMATION_SCHEMA changes. (Aleksandr Kuzminsky)
  • Bug #693818 – Warning and error messages for stored routines could incorrectly report row numbers due to a change in the slow_extended patch. (Alexey Kopytov)

The Release Notes for this and previous releases can be found in our Wiki.

Downloads are available here and from the Percona Software Repositories. The latest source code for Percona Server, including the development branch, can be found on Launchpad.

Please report any bugs found at Bugs in Percona Server.

For general questions, use our Percona Discussions Group, and for development questions our Percona Development Group.

For support, commercial, and sponsorship inquiries, contact Percona.


Entry posted by Fred Linhoss |
No comment

Add to: delicious | digg | reddit | netscape | Google Bookmarks

Dec
16
2010
--

Percona Server 5.1.53-11.7

Percona Server version 5.1.53-11.7 is now available for download.

The main purpose of this release is to update the current Percona stable release to the latest version of MySQL 5.1.

Functionality Added or Changed

  •  Percona Server 5.1.53-11.7 is now based on MySQL 5.1.53.
  •  New Features Added: None
  •  Other Changes: None

Bugs Fixed

  • Bug #643149 – Slow query log entries were not being done in the usual parsing format. (Alexey Kopytov)
  • Bug #677407 – The innodb.innodb_information_schema test could fail sporadically due to flawed logic in the INFORMATION_SCHEMA.INNODB_LOCKS caching mechanism. (Alexey Kopytov)

Release Notes for this and previous releases can be found in our Wiki.

Downloads are available here and from the Percona release repositories. The latest source code for Percona Server, including the development branch, can be found on Launchpad.

Please report any bugs found at Bugs in Percona Server.

For general questions, use our Percona Discussions Group, and for development questions our Percona Development Group.

For support, commercial, and sponsorship inquiries, contact Percona.


Entry posted by Fred Linhoss |
2 comments

Add to: delicious | digg | reddit | netscape | Google Bookmarks

Dec
13
2010
--

Percona Server 5.1.52-12.3

Percona Server version 5.1.52-12.3 is now available for download.

The main purpose of this release is to update the current Percona release candidate to the latest version of MySQL 5.1. The release also includes the HandlerSocket plugin, which provides NoSQL features in Percona Server.

Functionality Added or Changed

  • Percona Server 5.1.52-12.3 is now based on MySQL 5.1.52.
  • New Features Added:
    • HandlerSocket plugin support has been added to all RPM and Debian packages. This is an experimental feature. (Inada Naoki, DeNA Co., Ltd.)
    • show_slave_status_nolock – Allows examination of slave status even when a lock prevents SHOW SLAVE STATUS from operating. (Oleg Tsarev)
    •  innodb_fast_shutdown – Sleeping threads could cause a delay of up to 10 seconds during InnoDB shutdown. The sleeping state of threads was made interruptible to avoid this. (contributed by Kristian Nielsen) (Alexey Kopytov)
  • Other Changes: None

Bugs Fixed

  • Bug #640576 – The false error “innodb_extra_undoslots option is disabled but it was enabled before” was sometimes reported after upgrading from MySQL 5.0. (Yasufumi Kinoyasu)
  • Bug #643463 – Shutting down XtraDB could take up to 10 seconds, even when there was no actual work to do. (Fix contributed by Kristian Nielsen) (Alexey Kopytov)
  • Bug #663757 – On the FreeBSD platform, the “gcc atomic built-in” function isn’t provided, so response_time_distribution now uses the native atomic API on FreeBSD. (Oleg Tsarev)
  • Bug #673426 – Use of some system variables as command-line options caused a crash or undefined behavior. (Oleg Tsarev)
  • Bug #673562 – Debug build was broken due a to failing compile-time assertion in mysqld.cc. (Alexey Kopytov)
  • Bug #673567 – Compiler could produce spurious warnings when building on non-Linux platforms. A check is now made to see if clock_gettime() is present in librt at the configure stage. If yes, -lrt is added to LIBS. (Alexey Kopytov)
  • Bug #673929 – Query cache misses were being reported for some queries when hits were actually occurring. (Oleg Tsarev)
  • Bug #676146 – The development environment test of log_slow_verbosity=innodb on a slave for row-based replication was not working correctly. (Oleg Tsarev)
  • Bug #676147 – The development environment test of option log_slow_slave_statements for row-based replication was not working correctly. (Oleg Tsarev)
  • Bug #676148 – Similar to Bug #676147. A check is now made for the replication type to test. (Oleg Tsarev)

The Release Notes for this and previous releases can be found in our Wiki.

Downloads are available here and from the Percona Release Candidates Repository. The latest source code for Percona Server, including the development branch, can be found on LaunchPAD.

Please report any bugs found at Bugs in Percona Server.

For general questions, use our Percona Discussions Group, and for development questions our Percona Development Group.

For support, commercial, and sponsorship inquiries, contact Percona.


Entry posted by Fred Linhoss |
2 comments

Add to: delicious | digg | reddit | netscape | Google Bookmarks

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