MongoDB 3.2.18 is released

34 views
Skip to first unread message

Ramon Fernandez

unread,
Nov 29, 2017, 1:59:17 PM11/29/17
to mongodb-...@googlegroups.com, mongod...@googlegroups.com, mongodb-dev, mongodb...@googlegroups.com
MongoDB 3.2.18 is out and is ready for production deployment. This release contains only fixes since 3.2.17, and is a recommended upgrade for all 3.2 users. 


This release includes fixes for multiple issues where files corresponding to dropped collections and indexes may not be removed from disk until a server restart. 


Fixed in this release:

  • SERVER-29287  Upgrade pcre to 8.41
  • SERVER-31101  WT table not dropped after collection is dropped due to long-running OperationContext
  • SERVER-31149  Enable recovery progress messages
  • SERVER-31587  ReplBatcher has a long-running OperationContext
  • SERVER-31589  A primary's SyncSourceFeedback only renews an OperationContext on role changes.
  • SERVER-31590  WT yieldAndAwaitOplogDeletionRequest holds onto an OperationContext while blocking for an infrequent trigger
  • SERVER-32030  SyncTail::oplogApplication uses a long-running OperationContext (3.2/3.4) 

All Issues | Downloads 


As always, please let us know of any issues. 


-- The MongoDB Team 




Reply all
Reply to author
Forward
0 new messages