MongoDB 4.2.5 is out and is ready for production deployment. This release contains only fixes since 4.2.5, and is a recommended upgrade for all 4.2 users.
Note: The release of version 4.2.4 was skipped due to an issue encountered during the release. However, the 4.2.5 release includes the fixes made in 4.2.4.
Fixed in this release:
SERVER-46121 mongos crashes with invariant error after changing taskExecutorPoolSize
SERVER-45137 Increasing memory allocation in Top::record with high rate of collection creates and drops
SERVER-44904 Startup recovery should not delete corrupt documents while rebuilding unfinished indexes
SERVER-44260 Transaction can conflict with previous transaction on the session if the all committed point is held back
SERVER-35050 Don’t abort collection clone due to negative document count
SERVER-39112 Primary drain mode can be unnecessarily slow
As always, please let us know of any issues.
– The MongoDB Team