DOCS-13728 remove ServiceExecutorAdaptive

source/reference/configuration-file-settings-command-line-options-mapping.txt

@@ -64,10 +64,6 @@ and :binary:`~bin.mongos` command-line options.
      - | :option:`mongod --port`
        | :option:`mongos --port`
 
-   * - :setting:`net.serviceExecutor`
-     - | :option:`mongod --serviceExecutor`
-       | :option:`mongos --serviceExecutor`
-
    * - :setting:`net.tls.allowConnectionsWithoutCertificates`
      - | :option:`mongod --tlsAllowConnectionsWithoutCertificates`
        | :option:`mongos --tlsAllowConnectionsWithoutCertificates`
@@ -484,6 +480,9 @@ and :binary:`~bin.mongos` command-line options.
 
 ChangeLog
 ---------
+Starting in version 5.0:
+  MongoDB removes the ``--serviceExecutor`` command-line option and the
+  corresponding ``net.serviceExecutor`` configuration option.
 
 Starting in version 4.4:
    MongoDB removes the ``--noIndexBuildRetry`` command-line option and

source/reference/configuration-options.txt

@@ -832,6 +832,11 @@ Core Options
    MongoDB 4.2 deprecates ``ssl`` options in favor of ``tls`` options with
    identical functionality. 
 
+.. versionchanged:: 5.0
+
+   MongoDB removes the ``net.serviceExecutor`` configuration option and the
+   corresponding ``--serviceExecutor`` command-line option.
+
 .. code-block:: yaml
 
    net:
@@ -863,7 +868,6 @@ Core Options
          FIPSMode: <boolean>
       compression:
          compressors: <string>
-      serviceExecutor: <string>
 
 .. setting:: net.port
 
@@ -2162,41 +2166,6 @@ Core Options
    .. include:: /includes/fact-networkMessageCompressors.rst
 
 
-.. setting:: net.serviceExecutor
-
-   *Type*: string
-
-   *Default*: synchronous
-
-   .. versionadded:: 3.6
-
-   Determines the threading and execution model :binary:`~bin.mongos` or :binary:`~bin.mongod` uses to
-   execute client requests. The ``--serviceExecutor`` option accepts one
-   of the following values:
-
-   .. list-table::
-      :header-rows: 1
-      :widths: 20 40
-
-      * - Value
-
-        - Description
-
-      * - ``synchronous``
-
-        - The :binary:`~bin.mongos` or :binary:`~bin.mongod` uses synchronous networking and manages its
-          networking thread pool on a per connection basis. Previous
-          versions of MongoDB managed threads in this way.
-
-      * - ``adaptive``
-
-        - The :binary:`~bin.mongos` or :binary:`~bin.mongod` uses the new experimental asynchronous
-          networking mode with an adaptive thread pool which manages
-          threads on a per request basis. This mode should have more
-          consistent performance and use less resources when there are
-          more inactive connections than database requests.
-
-
 ``security`` Options
 ~~~~~~~~~~~~~~~~~~~~
 

source/reference/program/mongod.txt

@@ -57,6 +57,11 @@ Options
    - MongoDB removes the ``--noIndexBuildRetry`` command-line option
      and the corresponding ``storage.indexBuildRetry`` option.
 
+.. admonition:: Starting in version 5.0
+
+   - MongoDB removes the ``--serviceExecutor`` command-line option and the
+     corresponding ``net.serviceExecutor`` configuration option.
+
 Core Options
 ~~~~~~~~~~~~
 
@@ -773,39 +778,6 @@ Core Options
 
 
 
-.. option:: --serviceExecutor <string>
-
-   *Default*: synchronous
-
-   .. versionadded:: 3.6
-
-   Determines the threading and execution model :program:`mongod` uses to
-   execute client requests. The ``--serviceExecutor`` option accepts one
-   of the following values:
-
-   .. list-table::
-      :header-rows: 1
-      :widths: 20 40
-
-      * - Value
-
-        - Description
-
-      * - ``synchronous``
-
-        - The :program:`mongod` uses synchronous networking and manages its
-          networking thread pool on a per connection basis. Previous
-          versions of MongoDB managed threads in this way.
-
-      * - ``adaptive``
-
-        - The :program:`mongod` uses the new experimental asynchronous
-          networking mode with an adaptive thread pool which manages
-          threads on a per request basis. This mode should have more
-          consistent performance and use less resources when there are
-          more inactive connections than database requests.
-
-
 .. option:: --outputConfig
 
 

source/reference/program/mongos.txt

@@ -59,6 +59,11 @@ Options
 
    - .. include:: /includes/extracts/4.2-changes-options-tlsClusterCAFile.rst
 
+.. admonition:: Starting in version 5.0
+
+   - MongoDB removes the ``--serviceExecutor`` command-line option and the
+     corresponding ``net.serviceExecutor`` configuration option.
+
 .. |tlsClusterCAFile| replace:: :option:`--tlsClusterCAFile <mongos --tlsClusterCAFile>`
 
 Core Options
@@ -591,39 +596,6 @@ Core Options
    .. include:: /includes/fact-networkMessageCompressors.rst
 
 
-.. option:: --serviceExecutor <string>
-
-   *Default*: synchronous
-
-   .. versionadded:: 3.6
-
-   Determines the threading and execution model :program:`mongos` uses to
-   execute client requests. The ``--serviceExecutor`` option accepts one
-   of the following values:
-
-   .. list-table::
-      :header-rows: 1
-      :widths: 20 40
-
-      * - Value
-
-        - Description
-
-      * - ``synchronous``
-
-        - The :program:`mongos` uses synchronous networking and manages its
-          networking thread pool on a per connection basis. Previous
-          versions of MongoDB managed threads in this way.
-
-      * - ``adaptive``
-
-        - The :program:`mongos` uses the new experimental asynchronous
-          networking mode with an adaptive thread pool which manages
-          threads on a per request basis. This mode should have more
-          consistent performance and use less resources when there are
-          more inactive connections than database requests.
-
-
 .. option:: --timeZoneInfo <path>
 
    .. include:: /includes/fact-timeZoneInfo.rst

source/release-notes/5.0-compatibility.txt

@@ -67,6 +67,9 @@ General Changes
   stages </reference/operator/aggregation-pipeline>` allowed in a single
   pipeline is limited to 1000.
 
+- MongoDB 5.0 removes the ``--serviceExecutor`` command-line option and
+  the corresponding ``net.serviceExecutor`` configuration option.
+
 Deprecations
 ~~~~~~~~~~~~