# Percona Server for MySQL 5.7.21-21 Is Now Available **URL:** \ **Category:** Percona Server for MySQL 5.7\ **Created:** [April 25, 2018, 12:54am UTC](https://forums.percona.com/t/percona-server-for-mysql-5-7-21-21-is-now-available/6322 "2018-04-25T00:54:06Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![hrvojem](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/hrvojem/32/6_2.png) [@hrvojem](https://forums.percona.com/u/hrvojem)\ **Post date:** [April 25, 2018, 12:54am UTC](https://forums.percona.com/t/percona-server-for-mysql-5-7-21-21-is-now-available/6322/1 "2018-04-25T00:54:06Z")
Percona announces the GA release of [Percona Server for MySQL](https://www.percona.com/software/percona-server) 5.7.21-21 on on April 24, 2018. Download the latest version from the [Percona web site](https://www.percona.com/downloads/Percona-Server-5.7/Percona-Server-5.7.21-21/) or the Percona [Software Repositories](https://www.percona.com/doc/percona-server/5.7/installation.html#using-percona-software-repositories). You can also run Docker containers from the images in the [Docker Hub repository](https://hub.docker.com/r/percona/percona-server/). This version of Percona Server for MySQL 5.7.21 includes three new encryption features – Vault keyring plug-in, encryption for InnoDB general tablespaces, and encryption for binary log files. These new capabilities, which allow companies to immediately increase security for their existing databases, are also part of a larger project to build complete, robust, enterprise-grade encryption capabilities into Percona Server for MySQL, allowing customers and the community to satisfy their most rigorous security compliance requirements. Percona also announced the release of a new version of [Percona XtraBackup](https://www.percona.com/software/mysql-database/percona-xtrabackup) that supports backing up Percona Server for MySQL instances that have these encryption features enabled. Based on [MySQL 5.7.21](http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-21.html), including all the bug fixes in it, Percona Server for MySQL 5.7.21-21 is the current GA release in the Percona Server for MySQL 5.7 series. Percona provides completely open-source and free software. New Features: [LIST] [_]A new variable innodb\_temp\_tablespace\_encrypt is introduced to turn encryption of temporary tablespace and temporary InnoDB file-per-table tablespaces on/off. Bug fixed [#3821](https://jira.percona.com/browse/PS-3821). [_]A new variable innodb\_encrypt\_online\_alter\_logs simultaneously turns on encryption of files used by InnoDB for merge sort, online DDL logs, and temporary tables created by InnoDB for online DDL. Bug fixed [#3819](https://jira.percona.com/browse/PS-3819). [_]A new variable innodb\_encrypt\_tables can be set to ON, making InnoDB tables encrypted by default, to FORCE, disabling creation of unencrypted tables, or OFF, restoring the like-before behavior. Bug fixed [#1525](https://jira.percona.com/browse/PS-1525). [_]Query response time plugin now can be disabled at session level with use of a new variable query\_response\_time\_session\_stats. [/LIST]Bugs Fixed: [LIST] [_]Attempting to use a partially-installed query response time plugin could have caused server crash. Bug fixed [#3959](https://jira.percona.com/browse/PS-3959). [_]There was a server crash caused by a materialized temporary table from semi-join optimization with key length larger than 1000 bytes. Bug fixed [#296](https://jira.percona.com/browse/PS-296). [_]A regression in the original 5.7 port was causing integer overflow with thread\_pool\_stall\_limit variable values bigger than 2 seconds. Bug fixed [#1095](https://jira.percona.com/browse/PS-1095). [_]A memory leak took place in Percona Server when performance schema is used in conjunction with thread pooling. Bug fixed [#1096](https://jira.percona.com/browse/PS-1096). [_]A code clean-up was done to fix compilation with clang, both general warnings (bug fixed [#3814](https://jira.percona.com/browse/PS-3814), upstream [#89646](http://bugs.mysql.com/bug.php?id=89646)) and clang 6 specific warnings and errors (bug fixed [#3893](https://jira.percona.com/browse/PS-3893), upstream [#90111](http://bugs.mysql.com/bug.php?id=90111)). [_]Compilation warning was fixed for -DWITH\_QUERY\_RESPONSE\_TIME=ON CMake compilation option, which makes QRT to be linked statically. Bug fixed [#3841](https://jira.percona.com/browse/PS-3841). [_]Percona Server returned empty result for SELECT query if number of connections exceeded 65535. Bug fixed [#314](https://jira.percona.com/browse/PS-314) (upstream [#89313](http://bugs.mysql.com/bug.php?id=89313)). [_]A clean-up in Percona Server binlog-related code was made to avoid uninitialized memory comparison. Bug fixed [#3925](https://jira.percona.com/browse/PS-3925) (upstream [#90238](http://bugs.mysql.com/bug.php?id=90238)). [_]mysqldump utility with --innodb-optimize-keys option was incorrectly working with foreign keys on the same table, producing invalid SQL statements. Bugs fixed [#1125](https://jira.percona.com/browse/PS-1125) and [#3863](https://jira.percona.com/browse/PS-3863). [_]A fix of the mysqld startup script failed to detect jemalloc library location for preloading, thus not starting on systemd based machines, introduced in Percona Server [5.7.21-20](https://www.percona.com/doc/percona-server/LATEST/release-notes/Percona-Server-5.7.21-20.html#5.7.21-20), was improved to take into account previously created configuration file. Bug fixed [#3850](https://jira.percona.com/browse/PS-3850). [_]The possibility of a truncated bitmap file name was fixed in InnoDB logging subsystem. Bug fixed [#3926](https://jira.percona.com/browse/PS-3926). [_]Temporary file I/O was not instrumented for Performance Schema. Bug fixed [#3937](https://jira.percona.com/browse/PS-3937) (upstream [#90264](http://bugs.mysql.com/bug.php?id=90264)). [_]A crash in the unsafe query warning checks with views took place for UPDATE statement in case of statement binlogging format. Bug fixed [#290](https://jira.percona.com/browse/PS-290). [/LIST]MyRocks Changes: [LIST] [_]A re-implemented variable rpl\_skip\_tx\_api allows to turn on simple RocksDB write batches functionality, increasing replication performance by the transaction api skip. Bug fixed [MYR-47](https://jira.percona.com/browse/MYR-47). [_]Decoding value-less padded varchar fields could under some circumstances cause assertion and/or data corruption. Bug fixed [MYR-232](https://jira.percona.com/browse/MYR-232). [/LIST]TokuDB Changes: [LIST] [_]Two new variables introduced for the TokuDB fast updates feature, tokudb\_enable\_fast\_update and tokudb\_enable\_fast\_upsert should be now used instead of the NOAR keyword, which is now optional at compile time and off by default. Bugs fixed [#63](https://jira.percona.com/browse/TDB-63) and [#148](https://jira.percona.com/browse/TDB-148). [_]A set of compilation fixes was introduced to make TokuDB successfully build in MySQL / Percona Server 8.0. Bugs fixed [#84](https://jira.percona.com/browse/TDB-84), [#85](https://jira.percona.com/browse/TDB-85), [#114](https://jira.percona.com/browse/TDB-114), [#115](https://jira.percona.com/browse/TDB-115), [#118](https://jira.percona.com/browse/TDB-118), [#128](https://jira.percona.com/browse/TDB-128), [#139](https://jira.percona.com/browse/TDB-139), [#141](https://jira.percona.com/browse/TDB-141), and [#172](https://jira.percona.com/browse/TDB-172). [_]Conditional compilation code dependent on version ID in the TokuDB tree was separated and arranged to specific version branches. Bugs fixed [#133](https://jira.percona.com/browse/TDB-133), [#134](https://jira.percona.com/browse/TDB-134), [#135](https://jira.percona.com/browse/TDB-135), and [#136](https://jira.percona.com/browse/TDB-136). [_]ALTER TABLE … COMMENT = … statement caused TokuDB to rebuild the whole table, which is not needed, as only FRM metadata should be changed. Bug fixed [#130](https://jira.percona.com/browse/TDB-130), and [#137](https://jira.percona.com/browse/TDB-137). [_]Data race on the cache table pair attributes was fixed. [/LIST] Other bugs fixed: [#3793](https://jira.percona.com/browse/PS-3793), [#3812](https://jira.percona.com/browse/PS-3812), [#3813](https://jira.percona.com/browse/PS-3813), [#3815](https://jira.percona.com/browse/PS-3815), [#3818](https://jira.percona.com/browse/PS-3818), [#3835](https://jira.percona.com/browse/PS-3835), [#3875](https://jira.percona.com/browse/PS-3875) (upstream [#89916](http://bugs.mysql.com/bug.php?id=89916)), [#3843](https://jira.percona.com/browse/PS-3843) (upstream [#89822](http://bugs.mysql.com/bug.php?id=89822)), [#3848](https://jira.percona.com/browse/PS-3848), [#3856](https://jira.percona.com/browse/PS-3856), [#3887](https://jira.percona.com/browse/PS-3887), [MYR-160](https://jira.percona.com/browse/MYR-160), [MYR-245](https://jira.percona.com/browse/MYR-245), [#109](https://jira.percona.com/browse/TDB-109), [#111](https://jira.percona.com/browse/TDB-111),[#180](https://jira.percona.com/browse/TDB-180), [#181](https://jira.percona.com/browse/TDB-181), [#182](https://jira.percona.com/browse/TDB-182), and [#188](https://jira.percona.com/browse/TDB-188). The release notes for Percona Server for MySQL 5.7.21-20 are available in the [online documentation](https://www.percona.com/doc/percona-server/5.7/release-notes/Percona-Server-5.7.21-21.html). Please report any bugs on the [project bug tracking system](https://jira.percona.com/projects/PS).