mongodb · kay-kim · Apr 10, 2018 · Mar 8, 2018 · Apr 10, 2018 · Mar 9, 2018
diff --git a/config/redirects b/config/redirects
@@ -1377,6 +1377,11 @@ raw: /master/release-notes/3.0-general-improvements -> ${base}/release-notes/3.0
 [v3.6-*]: /${version}/reference/method/cursor.snapshot -> ${base}/${version}/reference/method/
 [v3.6-*]: /${version}/administration/replica-sets -> ${base}/${version}/replication
 
+[v4.0-*]: /${version}/core/security-mongodb-cr -> ${base}/${version}/core/security-scram
+[v4.0-*]: /${version}/reference/command/authSchemaUpgrade  -> ${base}/${version}/core/security-scram
+[v4.0-*]: /${version}/reference/command/copydbgetnonce  -> ${base}/${version}/reference/command/copydb
+[v4.0-*]: /${version}/source/reference/command/resync -> ${base}/${version}/core/master-slave
+
 # 2.8 compatibility
 [*]: /${version}/release-notes/2.8-downgrade -> ${base}/${version}/release-notes
 [*]: /${version}/release-notes/2.8-compatibility -> ${base}/${version}/release-notes

diff --git a/config/sphinx_local.yaml b/config/sphinx_local.yaml
@@ -79,6 +79,7 @@ theme:
     - /release-notes/3.2
     - /release-notes/3.4
     - /release-notes/3.6
+    - /release-notes/4.0
     - /security
     - /sharding
     - /changeStreams

diff --git a/source/administration/analyzing-mongodb-performance.txt b/source/administration/analyzing-mongodb-performance.txt
@@ -74,6 +74,11 @@ insufficient RAM resulting in
 Memory and the MMAPv1 Storage Engine
 ------------------------------------
 
+.. admonition:: Deprecated
+   :class: warning
+
+   .. include:: /includes/fact-4.0-mmapv1-deprecated.rst
+
 Memory Use
 ~~~~~~~~~~
 

diff --git a/source/administration/monitoring.txt b/source/administration/monitoring.txt
@@ -187,25 +187,6 @@ on your own servers. Most are open source.
 
      - **Description**
 
-   * - `Ganglia <http://sourceforge.net/apps/trac/ganglia/wiki>`_
-
-     - `mongodb-ganglia <https://github.com/quiiver/mongodb-ganglia>`_
-
-     - Python script to report operations per second, memory usage,
-       btree statistics, master/slave status and current connections.
-
-   * - Ganglia
-
-     - `gmond_python_modules <https://github.com/ganglia/gmond_python_modules>`_
-
-     - Parses output from the :dbcommand:`serverStatus` and
-       :dbcommand:`replSetGetStatus` commands.
-
-   * - `Motop <https://github.com/tart/motop>`_
-     - *None*
-
-     - Realtime monitoring tool for MongoDB servers. Shows
-       current operations ordered by durations every second.
 
    * - `mtop <https://github.com/beaufour/mtop>`_
 

diff --git a/source/administration/production-notes.txt b/source/administration/production-notes.txt
@@ -13,6 +13,11 @@ Production Notes
 This page details system configurations that affect MongoDB,
 especially when running in production.
 
+.. admonition:: Deprecated
+   :class: warning
+
+   .. include:: /includes/fact-4.0-mmapv1-deprecated.rst
+
 .. include:: /includes/fact-mms-summary.rst
 
 MongoDB Binaries
@@ -100,24 +105,6 @@ engine other than the one specified by :option:`--storageEngine <mongod --storag
 Concurrency
 -----------
 
-MMAPv1
-~~~~~~
-
-.. versionchanged:: 3.0
-
-   Beginning with MongoDB 3.0, :ref:`MMAPv1 <storage-mmapv1>` provides
-   *collection-level locking*: All collections have a unique
-   readers-writer lock that allows multiple clients to modify documents
-   in different collections at the same time.
-
-   For MongoDB versions 2.2 through 2.6 series, each database has a
-   readers-writer lock that allows concurrent read access to a
-   database, but gives exclusive access to a single write operation per
-   database. See the :doc:`Concurrency </faq/concurrency>` page for
-   more information. In earlier versions of MongoDB, all write
-   operations contended for a single readers-writer lock for the entire
-   :binary:`~bin.mongod` instance.
-
 .. _prod-notes-wired-tiger-concurrency:
 
 WiredTiger
@@ -132,6 +119,22 @@ can modify different documents in a collection at the same time.
    takes advantage of multiple CPU cores and how to improve operation
    throughput.
 
+MMAPv1 (*Deprecated in MongoDB 4.0*)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Beginning with MongoDB 3.0, :ref:`MMAPv1 <storage-mmapv1>` provides
+*collection-level locking*: All collections have a unique
+readers-writer lock that allows multiple clients to modify documents in
+different collections at the same time.
+
+For MongoDB versions 2.2 through 2.6 series, each database has a
+readers-writer lock that allows concurrent read access to a database,
+but gives exclusive access to a single write operation per database.
+See the :doc:`Concurrency </faq/concurrency>` page for more
+information. In earlier versions of MongoDB, all write operations
+contended for a single readers-writer lock for the entire
+:binary:`~bin.mongod` instance.
+
 Data Consistency
 ----------------
 
@@ -238,8 +241,8 @@ libraries (i.e. drivers) can run on big or little endian systems.
 Allocate Sufficient RAM and CPU
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-MMAPv1
-``````
+MMAPv1 (*Deprecated in MongoDB 4.0*)
+````````````````````````````````````
 
 Due to its concurrency model, the :ref:`MMAPv1 <storage-mmapv1>` storage engine does not
 require many CPU cores. As such, increasing the number of cores can
@@ -553,16 +556,16 @@ Set ``vm.swappiness`` to ``1``
 
 “Swappiness” is a Linux kernel setting that influences the behavior of
 the Virtual Memory manager when it needs to allocate a swap, ranging
-from ``0`` to ``100``, inclusive. 
+from ``0`` to ``100``, inclusive.
 
 - A setting of ``0`` tells the kernel to swap only to avoid
-  out-of-memory problems. 
+  out-of-memory problems.
 
 - A setting of ``100`` tells it to swap aggressively to disk.
 
-If your host runs kernel versions ``3.5`` or later, or 
-:abbr:`RHEL (Red Hat Enterprise Linux)` / CentOS kernel ``2.6.32-303`` 
-or later, setting this value to ``0`` could disable swapping. Set this 
+If your host runs kernel versions ``3.5`` or later, or
+:abbr:`RHEL (Red Hat Enterprise Linux)` / CentOS kernel ``2.6.32-303``
+or later, setting this value to ``0`` could disable swapping. Set this
 to ``1``.
 
 To see what the current swappiness level is, run:
@@ -573,7 +576,7 @@ To see what the current swappiness level is, run:
 
    60
 
-To change swappiness while the system is running, run: 
+To change swappiness while the system is running, run:
 
 .. code-block:: sh
 
@@ -645,7 +648,7 @@ For the **WiredTiger** storage engine:
   <https://www.mongodb.com/products/enterprise-grade-support>`_ can provide
   advice and guidance on non-zero readahead configurations.
 
-For the **MMAPv1** storage engine:
+For the **MMAPv1** storage engine (*Deprecated in MongoDB 4.0*):
 
 - Ensure that readahead settings for the block devices that store the
   database files are appropriate. For random access use patterns, set
@@ -722,8 +725,8 @@ cache that uses 40% or more of the total memory can lead to increased
 memory pressure and poor performance. Use ``SetSystemFileCacheSize`` to
 limit the amount of memory that the file system cache can use.
 
-MongoDB Using MMAPv1
-````````````````````
+MongoDB Using MMAPv1 (*Deprecated in MongoDB 4.0*)
+``````````````````````````````````````````````````
 
 Install Hotfix for MongoDB 2.6.6 and Later
 ++++++++++++++++++++++++++++++++++++++++++
@@ -767,7 +770,7 @@ accommodate Windows' commitment rules during peak database use.
 MongoDB on Virtual Environments
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-This section describes considerations when running MongoDB in some of 
+This section describes considerations when running MongoDB in some of
 the more common virtual environments.
 
 For all platforms, consider :ref:`virtualized-disks-scheduling`.
@@ -780,22 +783,22 @@ There are two performance configurations to consider:
 - Reproducible performance for performance testing or benchmarking, and
 - Raw maximum performance
 
-To tune performance on :abbr:`EC2 (Elastic Compute Cloud)` for either 
+To tune performance on :abbr:`EC2 (Elastic Compute Cloud)` for either
 configuration, you should:
 
 - Enable :abbr:`AWS (Amazon Web Services)`
-  `Enhanced Networking <http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enabling_enhanced_networking>`_ 
-  for your instance. Not all instance types support Enhanced Networking. 
+  `Enhanced Networking <http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enabling_enhanced_networking>`_
+  for your instance. Not all instance types support Enhanced Networking.
 
-  To learn more about Enhanced Networking, see to the 
+  To learn more about Enhanced Networking, see to the
   `AWS documentation <http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html#enabling_enhanced_networking>`_.
 
-If you are concerned more about reproducible performance on 
+If you are concerned more about reproducible performance on
 :abbr:`EC2 (Elastic Compute Cloud)`, you should also:
 
-- Use provisioned :abbr:`IOPS (Input/Output Operations Per Second)` 
-  for the storage, with separate devices for journal and data. Do not 
-  use the ephemeral (:abbr:`SSD (Solid State Disk)`) storage available 
+- Use provisioned :abbr:`IOPS (Input/Output Operations Per Second)`
+  for the storage, with separate devices for journal and data. Do not
+  use the ephemeral (:abbr:`SSD (Solid State Disk)`) storage available
   on most instance types as their performance changes moment to moment.
   (The ``i`` series is a notable exception, but very expensive.)
 

diff --git a/source/core/authentication-mechanisms.txt b/source/core/authentication-mechanisms.txt
@@ -12,13 +12,15 @@ Authentication Mechanisms
    :depth: 1
    :class: singlecol
 
+.. note::
+
+   Starting in version 4.0, MongoDB removes support for the deprecated
+   MongoDB Challenge-Response (``MONGODB-CR``) authentication mechanism.
+
 MongoDB supports the following authentication mechanisms:
 
 - :doc:`/core/security-scram` (*Default*)
 
-- :doc:`MongoDB Challenge and Response (MONGODB-CR)
-  </core/security-mongodb-cr>` (*Deprecated as of MongoDB 3.6*)
-
 - :doc:`x.509 Certificate Authentication </core/security-x.509>`.
 
 In addition, MongoDB Enterprise also provides supports for additional
@@ -30,8 +32,6 @@ additional mechanisms available in MongoDB Enterprise.
 Default Authentication Mechanism
 --------------------------------
 
-.. versionchanged:: 3.0
-
 As of MongoDB 3.0, :ref:`Salted Challenge Response Authentication
 Mechanism (SCRAM) <authentication-scram>` is the default
 authentication mechanism for MongoDB.
@@ -54,5 +54,4 @@ authentication mechanism from the command line.
       :titlesonly: 
 
       /core/security-scram
-      /core/security-mongodb-cr
       /core/security-x.509
diff --git a/source/core/authentication.txt b/source/core/authentication.txt
@@ -41,9 +41,6 @@ MongoDB supports multiple authentication mechanisms:
 
 - :ref:`authentication-scram` (*Default*)
 
-- :ref:`MongoDB Challenge and Response (MONGODB-CR)
-  <authentication-mongodb-cr>` (*Deprecated as of MongoDB 3.6*)
-
 - :ref:`x.509 Certificate Authentication <security-auth-x509>`.
 
 In addition to supporting the aforementioned mechanisms, MongoDB Enterprise

diff --git a/source/core/journaling.txt b/source/core/journaling.txt
@@ -107,6 +107,11 @@ WiredTiger will pre-allocate journal files.
 Journaling and the MMAPv1 Storage Engine
 ----------------------------------------
 
+.. note::
+
+   MongoDB 4.0 :ref:`deprecates the MMAPv1 storage engine
+   <4.0-deprecate-mmapv1>`.
+
 With :doc:`MMAPv1 </core/mmapv1>`, when a write operation occurs,
 MongoDB updates the in-memory view. With journaling enabled, MongoDB
 writes the in-memory changes first to on-disk journal files. If MongoDB