MongoDB 3.4.11 is released

12 views
Skip to first unread message

Ramon Fernandez

unread,
Jan 31, 2018, 3:44:24 PM1/31/18
to mongodb-...@googlegroups.com, mongod...@googlegroups.com, mongodb-dev, mongodb...@googlegroups.com

MongoDB 3.4.11 is out and is ready for production deployment. This release contains only fixes since 3.4.10, and is a recommended upgrade for all 3.4 users. 


Fixed in this release:

  • SERVER-19605 Oplog timeout should be configurable
  • SERVER-19919 Chunks that exceed 250000 docs but are under half chunk size get marked as jumbo
  • SERVER-21011 Certain queries against compound 2d/text indexes are incorrectly covered, return incorrect results
  • SERVER-29293 Recipient shard fails to abort migration on stepdown
  • SERVER-29423 Sharding balancer may schedule multiple migrations with the same source or destination
  • SERVER-29921 Mongo connection uri doesn't support @ character in database name
  • SERVER-30449 ProjectionSpecValidator is O(N**2) in number of fields in the projection
  • SERVER-31101 WT table not dropped after collection is dropped due to long-running OperationContext
  • SERVER-31225 The mongod process forks before listening for connections
  • SERVER-32001 Unindexing a key in a partial unique index may cause server crash
  • SERVER-32048 Updates using a numeric path component may cause index entries not to be created
  • SERVER-32286 Remove Type=forking from Debian SystemD service file
  • WT-3079 Make sure eviction visits all trees
  • WT-3248 Performance degradation in workload with large overflow items

All Issues | Downloads 


As always, please let us know of any issues. 


-- The MongoDB Team 




Reply all
Reply to author
Forward
0 new messages