This documentation is for the end of life version of Percona Server for MongoDB and is no longer supported. You may want to see the current documentation.
Percona Server for MongoDB 4.0.5-2¶
- Date
February 18, 2019
- Download
- Installation
Percona announces the GA release of Percona Server for MongoDB 4.0.5-2 on February 18, 2019. Download the latest version from the Percona website or the Percona software repositories.
Percona Server for MongoDB is an enhanced, open source, and highly-scalable database that is a fully-compatible, drop-in replacement for MongoDB 4.0 Community Edition. It supports MongoDB 4.0 protocols and drivers.
Percona Server for MongoDB extends the functionality of the MongoDB 4.0 Community Edition by including the Percona Memory Engine storage engine, encrypted WiredTiger storage engine, audit logging, External LDAP Authentication with SASL, hot backups, and enhanced query profiling. Percona Server for MongoDB requires no changes to MongoDB applications or code.
This release includes all features of MongoDB 4.0 Community Edition 4.0. Most notable among these are:
Note that the MMAPv1 storage engine is deprecated in MongoDB 4.0 Community Edition 4.0.
In Percona Server for MongoDB 4.0.5-2, data at rest encryption becomes GA. The data at rest encryption feature now covers the temporary files used for external sorting and the rollback files. You can decrypt and examine the contents of the rollback files using the new perconadecrypt command line tool.
In this release, Percona Server for MongoDB supports the ngram
full-text search
engine. Thanks to Sunguck Lee (@SunguckLee) for this contribution. To enable the ngram full-text search engine, create an index
passing ngram to the default_language
parameter:
mongo > db.collection.createIndex({name:"text"}, {default_language: "ngram"})
New Features¶
PSMDB-276: perconadecrypt tool is now available for decrypting the encrypted rollback files.
PSMDB-250: The Ngram full-text search engine has been added to Percona Server for MongoDB. Thanks to Sunguck Lee (@SunguckLee) for this contribution.
Bugs Fixed¶
PSMDB-234: It was possible to use a key file for encryption the owner of which was not the owner of the
mongod
process.PSMDB-273: When using data at rest encryption, temporary files for external sorting and rollback files were not encrypted
PSMDB-257: MongoDB could not be started with a group-readable key file owned by root.
PSMDB-272:
mongos
could crash when running thecreateBackup
command.
Other bugs fixed: PSMDB-247