MongoDB 3.6.4-rc0 is released

10 views
Skip to first unread message

Kelsey T Schubert

unread,
Apr 9, 2018, 2:19:12 PM4/9/18
to mongodb-...@googlegroups.com, mongod...@googlegroups.com, mongo...@googlegroups.com, mongodb...@googlegroups.com
MongoDB 3.6.4-rc0 is out and is ready for testing. This is a release candidate containing only fixes since 3.6.3. The next stable release 3.6.4 will be a recommended upgrade for all 3.6 users.

Fixed in this release:
  • SERVER-16802 Order of balancer chunk moves depends on order of config.collections
  • SERVER-28670 Add sharding metadata refresh metrics section to serverStatus
  • SERVER-28981 Sharding balancer prefers shards in a specific order when moving chunks
  • SERVER-31399 repl.apply.batches.totalMillis does not record the time spent applying batches
  • SERVER-32210 Stepping down recipient shard's primary while migrating session information can fassert
  • SERVER-32241 applyOps reports success even when a nested applyOps fails.
  • SERVER-32677 Segmentation fault converting ReplicaSet to Replicated Shard Cluster
  • SERVER-32886 Unnecessary sleeps during chunk migration
  • SERVER-33227 Using the method `connect` in a script will as a side effect update global `db`.
  • SERVER-33483 HTTP detection no longer working
  • SERVER-33542 Using maxTime() on MongoDB 3.4 and 3.6 does not yield the same error code
  • SERVER-33569 The check for logical session existence must not allow partial results
  • SERVER-33763 3.6 drivers fail to communicate with 3.6 sharded clusters running at FCV 3.4
  • SERVER-33982 Unbounded growth of pre-allocated log files on Windows
  • WT-3972 Allow more than 64K cursors to be open on a data source simultaneously
  • WT-3938 Reduce memory usage with many tables and sessions
All Issues | Downloads

As always, please let us know of any issues.

-- The MongoDB Team

Reply all
Reply to author
Forward
0 new messages