Buy Percona ServicesBuy Now!

Percona XtraDB Cluster 5.5 getting any security support?

Lastest Forum Posts - May 19, 2017 - 7:00am
It's my understanding that XtraDB Cluster 5.5 is not "actively" developed anymore, but does this include major security patches as well? I see that there was an upgrade pushed every few months to include more recent bug and security fixes, but I can't find any information on how often, if at all they are planned to be released. If it's no longer being supported at all, I believe the 5.5 documentation should have a very clear warning message for users, since I have been searching for nearly an hour an still have no idea if 5.5 has any support, security or otherwise. MySQL 5.5 and your own Percona Server for MySQL 5.5 appear to still be receiving security updates, which would lead me (and I'd assume many other people) to believe XtraDB CLuster 5.5 would also receive those updates.

default account for ssh login on PMM-SERVER OVA.

Lastest Forum Posts - May 18, 2017 - 9:07am
Hello, I'm in need to setup the OVA image correctly with NTP and static ips. Please provide the default local account of the PMM-Server-2017-04-20-0705.ova image to login via SSH or virtualbox console. Thanks so much Didier

Percona XtraDB Cluster Update

Lastest Forum Posts - May 18, 2017 - 6:14am
Hi all,
I run a percona XtraDB cluster the actual version installed percona-xtradb-cluster-server-5.6 5.6.35-26.20-3.
The mysql version installed is 5.6.35-81.0 and it looks that some security patch are missing http://www.oracle.com/technetwork/se...l#AppendixMSQL
Is already someone of you guys concerned with this problem?
Would be appreciated if you can share how are you dealing with this issue.

Many thanks

my.cnf vars evaluated before plugin

Lastest Forum Posts - May 18, 2017 - 4:39am
MySQL fails to start on new installations if my.cnf contains an option that depends on a plugin.

Code: # my.cnf plugin-load = QUERY_RESPONSE_TIME_AUDIT=query_response_time.so;QUERY_RESPONSE_TIME_READ=query_response_time.so;QUERY_RESPONSE_TIME_WRITE=query_response_time.so; query_response_time_stats = ON [...] Code: # error.log 2017-05-18T11:08:49.356652Z 0 [ERROR] unknown variable 'query_response_time_stats=ON' It could be nice to be able to install and enable plugins in my.cnf. Is there any way to do that? Thanks!

MongoDB Authentication and Roles: Creating Your First Personalized Role

Latest MySQL Performance Blog posts - May 17, 2017 - 11:53am

In this blog post, we’ll walk through the native MongoDB authentication and roles, and learn how to create personalized roles. It is a continuation of Securing MongoDB instances.

As said before, MongoDB features a few authentication methods and built-in roles that offer great control of both who is connecting to the database and what they are allowed to do. However, some companies have their own security policies that are often not covered by default roles. This blog post explains not only how to create personalized roles, but also how to grant minimum access to a user.

Authentication Methods

SCRAM-SHA-1 and MONGODB-CR are challenge-response protocols. All the users and passwords are saved encrypted in the MongoDB instance. Challenge-response authentication methods are widely used on the internet in several server-client software. These authentication methods do not send passwords as plain text to the server when the client is starting an authentication. Each new session has a different hash/code, which stops people from getting the password when sniffing the network.

The MONGODB-CR method was deprecated in version 3.0.

The x.509 authentication is an internal authentication that allows instances and clients to communicate to each other. All certificates are signed by the same Certificate Authority and must be valid. All the network traffic is encrypted by a given key, and it is only possible to read data with a valid certificate signed by such key.

MongoDB also offers external authentications such as LDAP and Kerberos. When using LDAP, users can log in to MongoDB using their centralized passwords. The LDAP application is commonly used to manage users and passwords in wide networks. Kerberos is a service that allows users to login only once, and then generates access tickets so that the users are allowed to access other services. Some configuration is necessary to use external authentication.

Built in roles

  • read: collStats,dbHash,dbStats,find,killCursors,listIndexes,listCollections,
  • readWrite: all read privileges + convertToCapped, createCollection,dbStats, dropCollection, createIndex, dropIndex, emptycapped, insert, listIndexes,remove, renameCollectionSameDB, update.
  • readAnyDatabase: allows the user to perform read in any database except the local and the config databases.

And so on…

In this tutorial, we are going to give specific privileges to a user who is allowed to only read the database, although he is allowed to write in a specific collection.

For this tutorial, we are using MongoDB 3.4 with previously configured authentication.

Steps:

  1. Create the database:
    mongo --authenticationDatbase admin -u superAdmin -p use percona db.foo.insert({x : 1}) db.foo2.insert({x : 1})
  2. Create a new user:
    > db.createUser({user : 'client_read', pwd : '123', roles : ['read']}) Successfully added user: { "user" : "client_read", "roles" : [ "read" ] }
  3. Log in with the user that has just been created and check the user access:
    ./mongo localhost/percona -u client_read -p MongoDB shell version v3.4.0-rc5 Enter password: db.foo.find() { "_id" : ObjectId("586bc2e9cac0bbb93f325d11"), "x" : 1 } db.foo2.find().count() 1 // If user try to insert documents will receive an error: > db.foo.insert({x : 2}) WriteResult({             "writeError" : {             "code" : 13,             "errmsg" : "not authorized on percona to execute command                  { insert: "foo", documents: [ { _id: ObjectId('586bc36e7b114fb2517462f3'), x: 2.0 } ], ordered: true }"             } })
  4. Log out and log in again with administrator user to create a new role for this user:
    mongo --authenticationDatabase admin -u superAdmin -p db.createRole({ role : 'write_foo2_Collection', privileges : [ {resource : {db : "percona", collection : "foo2"}, actions : ["insert","remove"]} ], roles : ["read"] }) db.updateUser('client_read', roles : ['write_foo2_Collection'])
  5. Check the new access:
    ./mongo db.auth('client_read','123') 1 > show collections foo foo2 > db.foo.find() { "_id" : ObjectId("586bc2e9cac0bbb93f325d11"), "x" : 1 } > db.foo2.insert({y : 2}) WriteResult({ "nInserted" : 1 }) > db.foo.insert({y : 2}) //does not have permission. WriteResult({       "writeError" : {             "code" : 13,             "errmsg" : "not authorized on percona to execute command { insert: "foo", documents: [ { _id: ObjectId('586bc5e26f05b3a5db849359'), y: 2.0 } ], ordered: true }"                      } })
  6. We can also add access to other database resources. Let’s suppose we would like to grant this just created user permission to execute a getLog command. This command is available in the clusterAdmin role, but we do not want to give all this role’s access to him. See https://docs.mongodb.com/v3.0/reference/privilege-actions/#authr.getLog.

    There is a caveat/detail/observation here. If we want to grant cluster privileges to a user, we should create the role in the admin database. Otherwise, the command will fail:

    db.grantPrivilegesToRole(      "write_foo2_Collection",            [                   {resource : {cluster : true}, actions : ["getLog"] }            ] ) Roles on the 'percona' database cannot be granted privileges that target other databases or the cluster :

  7. We are creating the same role in the admin database. This user only works properly if the admin database is present in a possible restore. Otherwise, the privileges fail:

    use admin db.createRole({      role : 'write_foo2_Collection_getLogs',      privileges : [                        {resource : {db : "percona", collection : "foo2"}, actions : ["insert","remove"]},                        {resource : {cluster : true}, actions : ["getLog"]}],        roles : [ {role : "read", db: "percona"}] }) use percona db.updateUser( "client_read", {      roles : [           { role : "write_foo2_Collection_getLogs", db : "admin" }                 ] } )

  8. Now the user has the same privileges as before, plus the getLog permission. We can test this user new access with:

    mongo --authenticationDatabase percona -u read_user -p db.adminCommand({getLog : 'global'}) {           "totalLinesWritten" : 287,           "log" : [.... …. }

I hope you find this post useful. Please feel free to ping me on twitter @AdamoTonete or @percona and let us know your thoughts.

READ Only user

Lastest Forum Posts - May 17, 2017 - 10:13am
Hello, Im testing the creation of a read only user. I have created the user 'r-db01' with select permissions only. In previous version of Mysql 5.5 if I connected as the ready only user, and I did "show databases;" it would only allow me to see the granted database and information_schema.

I am testing this read only user on the new 5.7 install and when I do a "show databases" as the read only user I created, I see all the databases. Did something change? Is there a new way of achieving this with 5.7?

thank you in advance.

Percona Cluster updated on debian but not used

Lastest Forum Posts - May 17, 2017 - 9:29am
Hi

i have recently update my percona cluster installation on all cluster nodes.
i have installed the percona repo for installation and updated.

apt command says that all percona components has been updated to the version 5.7.17-19.20, but when i start the mysql server, the version showed is 5.7.17-23-57 yet

anyone know why?

thanks

slow slave IO_THREAD

Lastest Forum Posts - May 17, 2017 - 5:54am
Hi All
We currently have a mysql master/slave replication set where the slave has gone into a lag of about 250 000 seconds.

We are running mysql 5.7.14 (from percona repo) and gtid and parallel master and slave processing is enabled.


During the weekend a LOT of data was processed and generated about 300Gb worth of binary logs that has to be processed, which is all good and well.

The two servers are in the same network subnet , connected via gigabit ports on the same switch.


I noticed that the slave_io_thread seems to be lagging as it is very far behind compared to the master server binary logs.

As a test, I disabled the slave sql_thread and let it only sync binary to relay logs.

Looking at the network throughput , we are only getting 6Mb/s

After it synced about 25Gb of data which took an entire night, I enabled sql_thread and within an hour it was all processed.


I initially though that this was a networking issue, however, when doing an scp from master to slave server writing to the same disk where the relay logs are located, then I get a throughput of about 75-80Mb/s


I have tried to enable slave_compressed_protocol however this made it even worse.


I can clearly see that the io_thread is the bottleneck, but I am out of ideas on how to speed this up.

Any ideas here would be greatly appreciated.

Regards

Corrupt frm after upgrade from MySQL 5.5 to MySQL 5.6 (with tokudb)

Lastest Forum Posts - May 17, 2017 - 5:46am
I am going to upgrade "mysql-5.5.41-tokudb-7.5.5-linux-x86_64" to "Percona-Server-5.6.36-rel82.0-Linux.x86_64.ssl101".
(Not dump & load , just copy datafiles to Percona server 5.6)

But partitioned table's frm can not be recognized with Percona server 5.6.

> MySQL 5.5
CREATE TABLE `partitioned` (
`c1` int(11) NOT NULL AUTO_INCREMENT,
`createDate` datetime NOT NULL,
`c2` int(11) NOT NULL,
`c3` varchar(100) DEFAULT NULL,
PRIMARY KEY (`c1`,`createDate`)
) ENGINE=TokuDB AUTO_INCREMENT=1572824 DEFAULT CHARSET=utf8mb4 ROW_FORMAT=TOKUDB_QUICKLZ
PARTITION BY RANGE COLUMNS(createDate)
(PARTITION p201502 VALUES LESS THAN ('2015-02-01 00:00:00') ENGINE = TokuDB,
PARTITION p201503 VALUES LESS THAN ('2015-03-01 00:00:00') ENGINE = TokuDB,
PARTITION p201504 VALUES LESS THAN ('2015-04-01 00:00:00') ENGINE = TokuDB,
PARTITION p201505 VALUES LESS THAN ('2015-05-01 00:00:00') ENGINE = TokuDB);

insert into part values (100, '2015-01-01 01:01:01', 100, '100');

> MySQL 5.6
show create table partitioned;
==> MySQL 5.6 complained that "mysqld: Incorrect information in file: './temp/part.frm'"
So, I created new table with same structure of 'partitioned', and copied(overwrited) frm and par files to partitioned table's (as guided from https://tokutek.atlassian.net/browse/DB-882).

After overwriting frm and par file, show create table command works properly.
But selecting data is trouble like..

mysql-5.6> select * from part;
+-----+---------------------+-----------+------+
| c1 | createDate | c2 | c3 |
+-----+---------------------+-----------+------+
| 100 | 2205-06-31 31:63:61 | 808464640 | |
+-----+---------------------+-----------+------+
1 row in set (0.00 sec)

I don't know why. but not partitioned table is working correctly. so I think it's FRM file's issue.
Looks like I can upgrade to percona server 5.6 if this frm issue can be solved.

Is there anyway to migrate FRM file of mysql 5.5 tokudb table to mysql 5.6 without dump/load .
There's huge data and no replication, so we need to upgrade percona server 5.6 without stopping service several days.

Thanks.

Percona Live Open Source Database Conference 2017 Slides and Videos Available

Latest MySQL Performance Blog posts - May 16, 2017 - 3:13pm

The slides and videos from the Percona Live Open Source Database Conference 2017 are available for viewing and download. The videos and slides cover the keynotes, breakout sessions and MySQL and MongoDB 101 sessions.

To view slides, go to the Percona Live agenda, and select the talk you want slides for from the schedule, and click through to the talk web page. The slides are available below the talk description. There is also a page with all the slides that is searchable by topic, talk title, speaker, company or keywords.

To view videos, go to the Percona Live 2017 video page. The available videos are searchable by topic, talk title, speaker, company or keywords.

There are a few slides and videos outstanding due to unforeseen circumstances. However, we will upload those as they become available.

Some examples of videos and slide decks from the Percona Live conference:

MongoDB 101: Efficient CRUD Queries in MongoDB
Adamo Tonete, Senior Technical Engineer, Percona
Video: https://www.percona.com/live/17/content/efficient-crud-queries-mongodb
Slides: https://www.percona.com/live/17/sessions/efficient-crud-queries-mongodb

MySQL 101: Choosing a MySQL High Availability Solution
Marcos Albe, Principal Technical Services Engineer, Percona
Video: https://www.percona.com/live/17/content/choosing-mysql-high-availability-solution
Slides: https://www.percona.com/live/17/sessions/choosing-mysql-high-availability-solution

Breakout Session: Using the MySQL Document Store
Mike Zinner, Sr. Software Development Director and Alfredo Kojima, Sr. Software Development Manager, Oracle
Video: https://www.percona.com/live/17/content/using-mysql-document-store
Slides: https://www.percona.com/live/17/sessions/using-mysql-document-store

Keynote: Continuent is Back! But What Does Continuent Do Anyway?
Eero Teerikorpi, Founder and CEO and MC Brown, VP Products, Continuent
Video: https://www.percona.com/live/17/content/continuent-back-what-does-continuent-do-anyway
Slides: https://www.percona.com/live/17/sessions/continuent-back-what-does-continuent-do-anyway

Please let us know if you have any issues. Enjoy the videos!

Percona Live Europe 2017: Dublin, Ireland!

This year’s Percona Live Europe will take place September 25th-27th, 2017, in Dublin, Ireland. Put it on your calendar now! Information on speakers, talks, sponsorship and registration will be available in the coming months.

We have developed multiple sponsorship options to allow participation at a level that best meets your partnering needs. Our goal is to create a significant opportunity for our partners to interact with Percona customers, other partners and community members. Sponsorship opportunities are available for Percona Live Europe 2017.

Download a prospectus here.

We look forward to seeing you there!

slow_log table is not logging

Lastest Forum Posts - May 16, 2017 - 2:31pm
Hi,
slow_log table in mysql database is not logging queries. I'm using RDS Aurora. slow_log is ON, long_query_time is set to 0.5 seconds. I'm running various queries running more than a second but the table is not logging anything. Any help is appreciated.

critical bug: pmm-client 1.1.3 mysql:queries exit with status 1

Lastest Forum Posts - May 16, 2017 - 5:18am
I'm facing trouble while upgrading

pmm-admin add mysql --user root --password password

[linux:metrics] OK, already monitoring this system.
[mysql:metrics] OK, now monitoring MySQL metrics using DSN root:***@unix(/data/mysql/mysql.sock)
[mysql:queries] Error adding MySQL queries: problem with agent registration on QAN API: exit status 1

Slave incorrectly treats some INT types as signed even if they not

Lastest Forum Posts - May 16, 2017 - 1:30am
Hi,
we are facing with strange behavior on one of our slave.

We have to change one of our columns from smallint to int in about 100 tables. Some tables have few rows but the biggest one has more than 400 000 000 rows. Some of the tables are using foreign keys. We created queries which simply modify column for tables without FK. For tables with FK, we prepared queries which remove the FK and modify columns. For each table its single query doing both. Then we prepared the single query for modifying the referenced table. The last prepared queries just add FK back. Because some tables are too big we decided to make changes on each server separately.

On each slave we ran:
Code: STOP SLAVE; SET sql_log_bin = 0; -- LOT OF QUERIES MODIFYING TABLES START SLAVE; We did this on two servers without problem. On the third server we are facing with error:

Code: Could not execute Update_rows event on table db.Item; Cannot add or update a child row: a foreign key constraint fails (`db`.`Item`, CONSTRAINT `FK_Item_1` FOREIGN KEY (`itemId`) REFERENCES `Item` (`itemId`) ON UPDATE CASCADE), Error_code: 1452; handler error HA_ERR_NO_REFERENCED_ROW; the event's master log server-bin.006694, end_log_pos 193170102 The table structure is same on master and slave:

Code: CREATE TABLE `ItemState` ( `itemStateId` int(10) unsigned NOT NULL AUTO_INCREMENT, `itemId` item(10) unsigned NOT NULL, `pid` int(10) unsigned NOT NULL, `startTime` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP, `endTime` datetime DEFAULT NULL, `errno` int(10) unsigned NOT NULL DEFAULT '0', `action` enum('d','p','def') COLLATE utf8_czech_ci NOT NULL DEFAULT 'default', `info` varbinary(30000) DEFAULT NULL COMMENT 'some comment', `mailSent` tinyint(3) unsigned NOT NULL DEFAULT '0' COMMENT 'some comment', PRIMARY KEY (`itemStateId`), KEY `itemId` (`itemId`,`action`) USING BTREE, KEY `cinn_errno_casKonec` (`action`,`errno`,`startTime`), KEY `casKonec_cinnost` (`endTime`,`action`), CONSTRAINT `FK_Table_1` FOREIGN KEY (`itemId`) REFERENCES `Item` (`itemId`) ON DELETE CASCADE ) ENGINE=InnoDB AUTO_INCREMENT=172552322 DEFAULT CHARSET=utf8 COLLATE=utf8_czech_ci ROW_FORMAT=DYNAMIC COMMENT='some comment' And the referenced row exists in the referenced table on master and slave. mysqlbinlog utility shows this in the query Code: @2=-27170 (38366) /* SHORTINT meta=0 nullable=0 is_null=0 */ It looks like that it is trying to insert signed value instead of unsigned. Can someone confirm it? What can cause this issue?

The slave is in version 5.6.36-82.0-log (but at the time of modifying tables was in version 5.6.34-79.1-log) and the master is in version 5.6.32-78.1-log. Version 5.6.34-79.1-log is also on the other two servers where is everything ok. The slave servers should have the same settings.

High open tables set.

Lastest Forum Posts - May 15, 2017 - 12:05pm
In my current database, I have 100 schema with 350 tables in each. Ive set my open table cache to 210,000 and the performance of my database has been stellar since this has been done. The problem I am running into his mysql seems to be using more memory than I allocate as per my innodb settings. So my question is does having a high open table cache cause to mysql to use more memory? I currently allocate about 230GB to innodb and my server has 512GB of ram. My db instance has been running for 30 days now and mysql is using about 340GB of memory and growing slowly.

Thanks for any information that can be provided.

Percona Server for MongoDB 3.2.13-3.3 is Now Available

Latest MySQL Performance Blog posts - May 15, 2017 - 10:55am

Percona announces the release of Percona Server for MongoDB 3.2.13-3.3 on May 15, 2017. Download the latest version from the Percona web site or 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.2 protocol and drivers. It extends MongoDB with MongoRocks, Percona Memory Engine, and PerconaFT storage engine, as well as enterprise-grade features like External Authentication, Audit Logging, Profiling Rate Limiting, and Hot Backup at no extra cost. Percona Server for MongoDB requires no changes to MongoDB applications or code.

NOTE: We deprecated the PerconaFT storage engine. It will not be available in future releases.

This release is based on MongoDB 3.2.13 and includes the following additional changes:

  • #PSMDB-127: Fixed cleanup of deleted documents and indexes for MongoRocks. When you upgrade to this release, deferred compaction may occur and cause database size to decrease significantly.
  • #PSMDB-133: Added the wiredTigerCheckpointSizeMB variable, set to 1000 in the configuration template for WiredTiger. Valid values are 32 to 2048 (2GB), with the latter being default.
  • #PSMDB-138: Implemented SERVER-23418 for MongoRocks.

Percona Server for MongoDB 3.2.13-3.3 release notes are available in the official documentation.

switch pmm clients to new pmm server

Lastest Forum Posts - May 15, 2017 - 8:04am
Hi,
i've been running new PMM server.

- both of pmm server has the same OS (suse SLES 12 sp2), username and password.
- i've changed parameters in /usr/local/percona/pmm-client/pmm.yml and restart service (pmm-admin restart)
- network check is OK:
"# pmm-admin check-network
PMM Network Status
Server Address | [correct server IP]
Client Address | [correct client IP]
* Connection: Client --> Server
-------------------- -------
SERVER SERVICE STATUS
-------------------- -------
Consul API OK
Prometheus API OK
Query Analytics API OK
Connection duration | 153.578µs
Request duration | 508.65µs
Full round trip | 662.228µs

No monitoring registered for this node identified as '[client name]'."

Which steps are missing to switch pmm clients to new server ?

Disabling xb_doublewrite

Lastest Forum Posts - May 15, 2017 - 5:07am
Hello,

My Percona 5.7.16 server creates the xb_doublewrite file at startup despite the 'innodb_doublewrite = 0' setting (running on ZFS). However, the file doesn't ever seem to be written to after the startup.

Is any way to disable creating this file at startup? I did try setting innodb_parallel_doublewrite_path to empty string, OFF, 0, etc, but it either ended with server refusing to start (empty), or the file being created (eg. 'OFF').

Thanks,
Kind regards,

Backing up and restore tokudb files on a new mysql installation

Lastest Forum Posts - May 15, 2017 - 4:08am
Hi,
In reference to my this post https://www.percona.com/forums/quest...okudb-is-buggy. Is looks like I have to restore the whole tokudb. Is there any way I can disabled innodb? So I am going to yum remove the current mysql and reinstall again. In the meantime I still have my current db directory with all the tokudb data files. So once I create the refresh installation I just create a new database and can I replace in those files and restore my db via this method?

Percona Server for MySQL 5.7.18-14 is Now Available

Lastest Forum Posts - May 15, 2017 - 1:55am
Percona announces the GA release of Percona Server for MySQL 5.7.18-14 on May 12, 2017. Download the latest version from the Percona web site or the Percona Software Repositories. You can also run Docker containers from the images in the Docker Hub repository.

Based on MySQL 5.7.18, including all the bug fixes in it, Percona Server for MySQL 5.7.18-14 is the current GA release in the Percona Server for MySQL 5.7 series. Percona’s provides completely open-source and free software. Find release details in the 5.7.18-14 milestone at Launchpad. New Features:

Bugs Fixed:

  • Deadlock could occur in I/O-bound workloads when server was using several small buffer pool instances in combination with small redo log files and variable innodb_empty_free_list_algorithm set to backoffalgorithm. Bug fixed #1651657.
  • Fixed a memory leak in Percona TokuBackup. Bug fixed #1669005.
  • Compressed columns with dictionaries could not be added to a partitioned table by using ALTER TABLE. Bug fixed #1671492.
  • Fixed a memory leak that happened in case of failure to create a multi-threaded slave worker thread. Bug fixed #1675716.
  • In-place upgrade from Percona Server 5.6 to 5.7 by using standalone packages would fail if /var/lib/mysqlwasn’t defined as the datadir. Bug fixed #1687276.
  • Combination of using any audit API-using plugin, like Audit Log Plugin and Response Time Distribution, with multi-byte collation connection and PREPARE statement with a parse error could lead to a server crash. Bug fixed #1688698 (upstream #86209).
  • Fix for a #1433432 bug caused a performance regression due to suboptimal LRU manager thread flushing heuristics. Bug fixed #1631309.
  • Creating Compressed columns with dictionaries in MyISAM tables by specifying partition engines would not result in error. Bug fixed #1631954.
  • It was not possible to configure basedir as a symlink. Bug fixed #1639735.
  • Replication slave did not report Seconds_Behind_Master correctly when running in multi-threaded slave mode. Bug fixed #1654091 (upstream #84415).
  • DROP TEMPORARY TABLE would create a transaction in binary log on a read-only server. Bug fixed #1668602(upstream #85258).
  • Processing GTIDs in the relay log that were already been executed were causing write/fsync amplification. Bug fixed #1669928 (upstream #85141).
  • Text/BLOB fields were not handling sorting of the empty string consistently between InnoDB and filesort. Bug fixed #1674867 (upstream #81810) by porting a Facebook patch for MySQL.
  • InnoDB adaptive hash index was using a partitioning algorithm which would produce uneven distribution when the server contained many tables with an identical schema. Bug fixed #1679155 (upstream #81814).
  • For plugin variables that are signed numbers, doing a SHOW VARIABLES would always show an unsigned number. Fixed by porting a Facebook patch for MySQL.
Other bugs fixed: #1629250 (upstream #83245), #1660828 (upstream #84786), #1664519 (upstream #84940), #1674299, #1670588 (upstream #84173), #1672389, #1674507, #1675623, #1650294, #1659224, #1662908, #1669002, #1671473, #1673800, #1674284, #1676441, #1676705, #1676847 (upstream #85671), #1677130 (upstream #85678), #1677162, #1677943, #1678692, #1680510 (upstream #85838), #1683993, #1684012, #1684078, #1684264, #1687386, #1687432, #1687600, and #1674281.

The release notes for Percona Server for MySQL 5.7.18-14 are available in the online documentation. Please report any bugs on the launchpad bug tracker.

Percona Server for MySQL 5.6.36-82.0 is Now Available

Lastest Forum Posts - May 15, 2017 - 1:54am
Percona announces the release of Percona Server for MySQL 5.6.36-82.0 on May 12, 2017. Download the latest version from the Percona web site or the Percona Software Repositories. You can also run Docker containers from the images in the Docker Hub repository.

Based on MySQL 5.6.36, and including all the bug fixes in it, Percona Server for MySQL 5.6.36-82.0 is the current GA release in the Percona Server for MySQL 5.6 series. Percona Server for MySQL is open-source and free – this is the latest release of our enhanced, drop-in replacement for MySQL. Complete details of this release are available in the 5.6.36-82.0 milestone on Launchpad. New Features:

Bugs Fixed:

  • Deadlock could occur in I/O-bound workloads when server was using several small buffer pool instances in combination with small redo log files and variable innodb_empty_free_list_algorithm set to backoffalgorithm. Bug fixed #1651657.
  • Querying TABLE_STATISTICS in combination with a stored function could lead to a server crash. Bug fixed #1659992.
  • tokubackup_slave_info file was created for a master server after taking the backup with Percona TokuBackup. Bug fixed #135.
  • Fixed a memory leak in Percona TokuBackup. Bug fixed #1669005.
  • Compressed columns with dictionaries could not be added to a partitioned table by using ALTER TABLE. Bug fixed #1671492.
  • Fixed a memory leak that happened in case of failure to create a multi-threaded slave worker thread. Bug fixed #1675716.
  • The combination of using any audit API-using plugin, like Audit Log Plugin and Response Time Distribution, with multi-byte collation connection and PREPARE statement with a parse error could lead to a server crash. Bug fixed #1688698 (upstream #86209).
  • Fix for a #1433432 bug in Percona Server 5.6.28-76.1 caused a performance regression due to suboptimal LRU manager thread flushing heuristics. Bug fixed #1631309.
  • Creating Compressed columns with dictionaries in MyISAM tables by specifying partition engines would not result in error. Bug fixed #1631954.
  • It was not possible to configure basedir as a symlink. Bug fixed #1639735.
  • Replication slave did not report Seconds_Behind_Master correctly when running in multi-threaded slave mode. Bug fixed #1654091 (upstream #84415).
  • DROP TEMPORARY TABLE would create a transaction in binary log on a read-only server. Bug fixed #1668602(upstream #85258).
  • Creating a compression dictionary with innodb_fake_changes enabled could lead to a server crash. Bug fixed #1629257.
Other bugs fixed: #1660828 (upstream #84786), #1664519 (upstream #84940), #1674299, #1683456, #1670588 (upstream #84173), #1672389, #1674507, #1674867, #1675623, #1650294, #1659224, #1660565, #1662908, #1669002, #1671473, #1673800, #1674284, #1676441, #1676705, #1676847 (upstream #85671), #1677130 (upstream #85678), #1677162, #1678692, #1678792, #1680510 (upstream #85838), #1683993, #1684012, #1684078, #1684264, and #1674281.

Release notes for Percona Server for MySQL 5.6.36-82.0 are available in the online documentation. Please report any bugs on the launchpad bug tracker.
Visit Percona Store


General Inquiries

For general inquiries, please send us your question and someone will contact you.