MongoDB 3.2.10 is out and is ready for production deployment. This release contains only fixes since 3.2.9, and is a recommended upgrade for all 3.2 users.
Fixed in this release:
SERVER-12048 Calling "service mongod start" with mongod running prevents "service mongod stop" from working
SERVER-16801 Update considers a change in numerical type to be a noop
SERVER-24320 Planner can attempt to use invalid index when using plan cache due to plan cache key / MatchExpression sorting inconsistency
SERVER-25039 Aggregation can attempt to re-plan after collection has been dropped
TOOLS-1140 Tools do not respect readPreference=secondary when connecting to a mongos
All Issues:
As always, please let us know of any issues.
-- The MongoDB Team