[mongodb-dev] MongoDB 3.6.4 is released

['Kelsey Schubert' via mongodb-dev]

*MongoDB 3.6.4 is out and is ready for production deployment. This release
contains only fixes since 3.6.3, and is a recommended upgrade for all 3.6
users.Fixed in this release: - SERVER-16802
<https://jira.mongodb.org/browse/SERVER-16802> Order of balancer chunk
moves depends on order of config.collections- SERVER-28670
<https://jira.mongodb.org/browse/SERVER-28670> Add sharding metadata
refresh metrics section to serverStatus- SERVER-28981
<https://jira.mongodb.org/browse/SERVER-28981> Sharding balancer prefers
shards in a specific order when moving chunks- SERVER-31399
<https://jira.mongodb.org/browse/SERVER-31399>
repl.apply.batches.totalMillis does not record the time spent applying
batches- SERVER-32210 <https://jira.mongodb.org/browse/SERVER-32210>
Stepping down recipient shard's primary while migrating session information
can fassert- SERVER-32241 <https://jira.mongodb.org/browse/SERVER-32241>
applyOps reports success even when a nested applyOps fails.- SERVER-32677
<https://jira.mongodb.org/browse/SERVER-32677> Segmentation fault
converting ReplicaSet to Replicated Shard Cluster- SERVER-32886
<https://jira.mongodb.org/browse/SERVER-32886> Unnecessary sleeps during
chunk migration- SERVER-33227
<https://jira.mongodb.org/browse/SERVER-33227> Using the method `connect`
in a script will as a side effect update global `db`.- SERVER-33483
<https://jira.mongodb.org/browse/SERVER-33483> HTTP detection no longer
working- SERVER-33542 <https://jira.mongodb.org/browse/SERVER-33542> Using
maxTime() on MongoDB 3.4 and 3.6 does not yield the same error code-
SERVER-33569 <https://jira.mongodb.org/browse/SERVER-33569> The check for
logical session existence must not allow partial results- SERVER-33763
<https://jira.mongodb.org/browse/SERVER-33763> 3.6 drivers fail to
communicate with 3.6 sharded clusters running at FCV 3.4- SERVER-33982
<https://jira.mongodb.org/browse/SERVER-33982> Unbounded growth of
pre-allocated log files on Windows- WT-3972
<https://jira.mongodb.org/browse/WT-3972> Allow more than 64K cursors to be
open on a data source simultaneously- WT-3938
<https://jira.mongodb.org/browse/WT-3938> Reduce memory usage with many
tables and sessions3.6 Release Notes
<http://docs.mongodb.org/manual/release-notes/3.6> | All Issues
<https://jira.mongodb.org/issues/?jql=project%20in%20(SERVER%2CTOOLS%2CWT)%20AND%20resolution%3D%27Fixed%27%20and%20fixversion%3D%273.6.4%27>
| Downloads <http://www.mongodb.org/downloads> For more information about
MongoDB 3.6, read the What’s New in MongoDB 3.6 white paper​
<https://www.mongodb.com/collateral/mongodb-36-whats-new>Get up to speed on
MongoDB 3.6 with the MongoDB 3.6 Online Course
<https://university.mongodb.com/courses/M036/about>As always, please let us
know of any issues. -- The MongoDB Team*