Buy Percona ServicesBuy Now!

Percona Server for MongoDB 3.4.13-2.11 Is Now Available

 | March 5, 2018 |  Posted In: Events and Announcements, Percona Server for MongoDB, Percona Software


Percona Server for MongoDB 3.4Percona announces the release of Percona Server for MongoDB 3.4.13-2.11 on March 5, 2018. Download the latest version from the Percona web site or the Percona Software Repositories.

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

Percona Server for MongoDB extends MongoDB Community Edition functionality by including the Percona Memory Engine and MongoRocks storage engines, as well as several enterprise-grade features:

Percona Server for MongoDB requires no changes to MongoDB applications or code.

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

  • PSMDB-191: Fixed a bug in MongoRocks engine initialization code which caused wrong initialization of _maxPrefix value. This could lead to reuse of dropped prefix and accidental removal of data from the collection using a reused prefix.In some specific conditions, data records could disappear at an arbitrary moment of time from the collections or indexes created after server restart.This could happen as the result of the following sequence of events:
    • User deletes one or more indexes or collections. These should be the ones using maximum existing prefixes values.
    • User shuts down the server before MongoRocks compaction thread executes compactions of deleted ranges.
    • User restarts the server and creates new collections. Due to the bug, those new collections and their indexes may get the same prefix values which were deleted and not yet compacted. The user inserts some data into the new collections.
    • After the server restart MongoRocks compaction thread continues executing compactions of the deleted ranges and this process may eventually delete data from the collections sharing prefixes with deleted ranges.
  • PSMDB-164: MongoRocks would fail to repair if metadata was inconsistent with dropped idents.
  • SERVER-30790: ServerStatus on MongoRocks is now accessing the storage engine without any locks.

Leave a Reply