Merge remote-tracking branch 'upstream/v5.0.10' into v5.0

Author: jeff-allen-mongo

source/administration/connection-pool-overview.txt

@@ -163,7 +163,15 @@ Settings
        *Default*: ``1``. See 
        :parameter:`ShardingTaskExecutorPoolMinSize`.  
 
-       This setting only applies to sharded deployments.
+       Parameter only applies to sharded deployments.
+
+   * - :parameter:`ShardingTaskExecutorPoolMinSizeForConfigServers`
+
+     - .. include:: /includes/ShardingTaskExecutorPoolMinSizeForConfigServers-parameter.rst
+
+       *Default*: ``-1``
+
+       .. versionadded:: 5.0.10
 
    * - :parameter:`ShardingTaskExecutorPoolMaxSize` 
 
@@ -174,8 +182,16 @@ Settings
        *Default*: 2\ :sup:`64` - 1. See 
        :parameter:`ShardingTaskExecutorPoolMaxSize`.
 
-       This setting only applies to sharded deployments.
- 
+       Parameter only applies to sharded deployments.
+
+   * - :parameter:`ShardingTaskExecutorPoolMaxSizeForConfigServers`
+
+     - .. include:: /includes/ShardingTaskExecutorPoolMaxSizeForConfigServers-parameter.rst
+
+       *Default*: ``-1``
+
+       .. versionadded:: 5.0.10
+
 .. toctree::
    :titlesonly:
    :hidden:

source/includes/ShardingTaskExecutorPoolMaxSizeForConfigServers-parameter-example.rst

@@ -0,0 +1,4 @@
+.. |parameter| replace:: :parameter:`ShardingTaskExecutorPoolMaxSize`
+.. |maximum-or-minimum| replace:: maximum
+
+.. include:: /includes/ShardingTaskExecutorPoolSizeForConfigServers-parameter-example.rst

source/includes/ShardingTaskExecutorPoolMaxSizeForConfigServers-parameter.rst

@@ -0,0 +1,4 @@
+.. |parameter| replace:: :parameter:`ShardingTaskExecutorPoolMaxSize`
+.. |maximum-or-minimum| replace:: maximum
+
+.. include:: /includes/ShardingTaskExecutorPoolSizeForConfigServers-parameter.rst

source/includes/ShardingTaskExecutorPoolMinSizeForConfigServers-parameter-example.rst

@@ -0,0 +1,4 @@
+.. |parameter| replace:: :parameter:`ShardingTaskExecutorPoolMinSize`
+.. |maximum-or-minimum| replace:: minimum
+
+.. include:: /includes/ShardingTaskExecutorPoolSizeForConfigServers-parameter-example.rst

source/includes/ShardingTaskExecutorPoolMinSizeForConfigServers-parameter.rst

@@ -0,0 +1,4 @@
+.. |parameter| replace:: :parameter:`ShardingTaskExecutorPoolMinSize`
+.. |maximum-or-minimum| replace:: minimum
+
+.. include:: /includes/ShardingTaskExecutorPoolSizeForConfigServers-parameter.rst

source/includes/ShardingTaskExecutorPoolSizeForConfigServers-parameter-example.rst

@@ -0,0 +1,4 @@
+The following example sets |parameter| to ``2`` during startup, which
+sets the |maximum-or-minimum| number of outbound connections each
+TaskExecutor connection pool can open to a configuration server to
+``2``:

source/includes/ShardingTaskExecutorPoolSizeForConfigServers-parameter.rst

@@ -0,0 +1,13 @@
+Optional override for |parameter| to set the |maximum-or-minimum| number
+of outbound connections each TaskExecutor connection pool can open to a
+:ref:`configuration server <sharding-config-server>`.
+
+When set to:
+       
+- ``-1``, |parameter| is used. This is the default.
+       
+- an integer value greater than ``-1``, overrides the
+  |maximum-or-minimum| number of outbound connections each TaskExecutor
+  connection pool can open to a configuration server.
+
+Parameter only applies to sharded deployments.

source/reference/parameters.txt

@@ -2128,6 +2128,39 @@ If you attempt to update ``disableSplitHorizonIPCheck`` at runtime,
 
       mongod --setParameter maxSessions=1000
 
+.. parameter:: oplogBatchDelayMillis
+
+   .. versionadded:: 5.0.10
+
+   |both|
+
+   *Type*: integer
+
+   *Default*: 0
+
+   The number of milliseconds to delay applying batches of oplog
+   operations on secondary nodes. By default, ``oplogBatchDelayMillis``
+   is ``0``, meaning oplog batches are applied with no delay. When there
+   is no delay, MongoDB may apply frequent, small oplog batches to
+   secondaries.
+
+   Increasing ``oplogBatchDelayMillis`` causes MongoDB to apply oplog
+   batches less frequently on secondaries, with each batch containing
+   larger amounts of data. This reduces :abbr:`IOPS (Input/Output
+   Operations Per Second)` on secondaries, but adds latency for writes
+   with write concern :writeconcern:`"majority"`.
+
+   You can only set ``oplogBatchDelayMillis`` at startup. You cannot set
+   ``oplogBatchDelayMillis`` during runtime.
+
+   For example, run the following command to set the
+   ``oplogBatchDelayMillis`` for a :binary:`~bin.mongod` instance to 20
+   milliseconds:
+
+   .. code-block:: bash
+
+      mongod --setParameter oplogBatchDelayMillis=20
+
 .. parameter:: TransactionRecordMinimumLifetimeMinutes
 
    .. versionadded:: 3.6
@@ -2831,7 +2864,7 @@ Sharding Parameters
    and :method:`delete <db.collection.deleteOne>` operations.
 
    For example, to set the maximum percentage to 20, you can issue the
-   followingduring startup:
+   following during startup:
 
    .. code-block:: bash
 
@@ -3169,6 +3202,33 @@ Sharding Parameters
 
       :parameter:`ShardingTaskExecutorPoolMinSize`
 
+.. parameter:: ShardingTaskExecutorPoolMaxSizeForConfigServers
+
+   .. versionadded:: 5.0.10
+
+   Type: integer
+
+   Default: -1
+
+   |both|
+
+   .. include:: /includes/ShardingTaskExecutorPoolMaxSizeForConfigServers-parameter.rst
+
+   .. include:: /includes/ShardingTaskExecutorPoolMaxSizeForConfigServers-parameter-example.rst
+
+   .. code-block:: bash
+
+      mongos --setParameter ShardingTaskExecutorPoolMaxSizeForConfigServers=2
+
+   During runtime, you can also set the parameter with the
+   :dbcommand:`setParameter` command:
+
+   .. code-block:: javascript
+
+      db.adminCommand( { setParameter: 1, ShardingTaskExecutorPoolMaxSizeForConfigServers: 2 } )
+
+.. _sharding-pool-minsize-parameters:
+
 .. parameter:: ShardingTaskExecutorPoolMinSize
 
    Type: integer
@@ -3223,6 +3283,31 @@ Sharding Parameters
       - :parameter:`ShardingTaskExecutorPoolMaxSize`
       - :parameter:`warmMinConnectionsInShardingTaskExecutorPoolOnStartup`
 
+.. parameter:: ShardingTaskExecutorPoolMinSizeForConfigServers
+
+   .. versionadded:: 5.0.10
+
+   Type: integer
+
+   Default: -1
+
+   |both|
+
+   .. include:: /includes/ShardingTaskExecutorPoolMinSizeForConfigServers-parameter.rst
+
+   .. include:: /includes/ShardingTaskExecutorPoolMinSizeForConfigServers-parameter-example.rst
+
+   .. code-block:: bash
+
+      mongos --setParameter ShardingTaskExecutorPoolMinSizeForConfigServers=2
+
+   During runtime, you can also set the parameter with the
+   :dbcommand:`setParameter` command:
+
+   .. code-block:: javascript
+
+      db.adminCommand( { setParameter: 1, ShardingTaskExecutorPoolMinSizeForConfigServers: 2 } )
+
 .. parameter:: ShardingTaskExecutorPoolRefreshRequirementMS
 
    Type: integer