Skip to content

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 3.6.10-3.0


February 6, 2019



Installing Percona Server for MongoDB

Percona announces the release of Percona Server for MongoDB 3.6.10-3.0 on February 6, 2019. Download the latest version from the Percona website or the Percona Software Repositories. This release is also available for Ubuntu 18.10 (Cosmic Cuttlefish).

Percona Server for MongoDB is an enhanced, open source, and highly-scalable database that is a fully-compatible, drop-in replacement for MongoDB 3.6 Community Edition. It supports MongoDB 3.6 protocols and drivers.

Percona Server for MongoDB extends Community Edition functionality by including the Percona Memory Engine storage engine, as well as several enterprise-grade features. Also, it includes MongoRocks storage engine, which is now deprecated. Percona Server for MongoDB requires no changes to MongoDB applications or code.

In Percona Server for MongoDB 3.6.10-3.0, 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 @SunguckLee on github for this contribution. To enable Ngram full text search, 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 @SunguckLee on github

Bugs Fixed

  • PSMDB-234: It was possible use a key file for encryption the owner of which was not the owner of the mongod process.

  • PSMDB-269: In some cases, hot backup was not using the correct path to the keydb directory designated for data encryption.

  • PSMDB-273: When using data at rest encryption, temporary files for external sorting and rollback files were not encrypted

  • PSMDB-272: mongos could crash when running the the createBackup command.

  • PSMDB-233: WiredTiger encryption options were silently ignored at server startup, although a storage engine different from WiredTiger was used.

  • PSMDB-257: MongoDB could not be started with a group-readable key file owned by root.

  • PSMDB-266: In some cases, it was possible to add arbitrary collections to the keydb directory which may only store encryption data.

Other bugs fixed: PSMDB-239, PSMDB-243