@@ -2294,7 +2294,54 @@ Sharding Parameters
2294
2294
pools, where ``n`` is the number of cores. See
2295
2295
:parameter:`taskExecutorPoolSize`.
2296
2296
2297
- .. seealso:: :parameter:`ShardingTaskExecutorPoolMinSize`
2297
+ .. seealso::
2298
+
2299
+ :parameter:`ShardingTaskExecutorPoolMinSize`
2300
+
2301
+ .. parameter:: ShardingTaskExecutorPoolMaxSizeForConfigServers
2302
+
2303
+ .. versionadded:: 4.2.22
2304
+
2305
+ Type: integer
2306
+
2307
+ Default: -1
2308
+
2309
+ |both|
2310
+
2311
+ Optional override for :parameter:`ShardingTaskExecutorPoolMaxSize` to
2312
+ set the maximum number of outbound connections each TaskExecutor
2313
+ connection pool can open to a :ref:`configuration server
2314
+ <sharding-config-server>`.
2315
+
2316
+ When set to:
2317
+
2318
+ - ``-1``, :parameter:`ShardingTaskExecutorPoolMaxSize` is used. This
2319
+ is the default.
2320
+
2321
+ - an integer value greater than ``-1``, overrides the
2322
+ maximum number of outbound connections each TaskExecutor
2323
+ connection pool can open to a configuration server.
2324
+
2325
+ Parameter only applies to sharded deployments.
2326
+
2327
+ The following example sets
2328
+ :parameter:`ShardingTaskExecutorPoolMaxSizeForConfigServers` to ``2``
2329
+ during startup, which sets the maximum number of outbound connections
2330
+ each TaskExecutor connection pool can open to a configuration server
2331
+ to ``2``:
2332
+
2333
+ .. code-block:: bash
2334
+
2335
+ mongos --setParameter ShardingTaskExecutorPoolMaxSizeForConfigServers=2
2336
+
2337
+ During runtime, you can also set the parameter with the
2338
+ :dbcommand:`setParameter` command:
2339
+
2340
+ .. code-block:: javascript
2341
+
2342
+ db.adminCommand( { setParameter: 1, ShardingTaskExecutorPoolMaxSizeForConfigServers: 2 } )
2343
+
2344
+ .. _sharding-pool-minsize-parameters:
2298
2345
2299
2346
.. parameter:: ShardingTaskExecutorPoolMinSize
2300
2347
@@ -2334,6 +2381,49 @@ Sharding Parameters
2334
2381
2335
2382
.. seealso:: :parameter:`ShardingTaskExecutorPoolMaxSize`
2336
2383
2384
+ .. parameter:: ShardingTaskExecutorPoolMinSizeForConfigServers
2385
+
2386
+ .. versionadded:: 4.2.22
2387
+
2388
+ Type: integer
2389
+
2390
+ Default: -1
2391
+
2392
+ |both|
2393
+
2394
+ Optional override for :parameter:`ShardingTaskExecutorPoolMinSize` to
2395
+ set the minimum number of outbound connections each TaskExecutor
2396
+ connection pool can open to a :ref:`configuration server
2397
+ <sharding-config-server>`.
2398
+
2399
+ When set to:
2400
+
2401
+ - ``-1``, :parameter:`ShardingTaskExecutorPoolMinSize` is used. This
2402
+ is the default.
2403
+
2404
+ - an integer value greater than ``-1``, overrides the
2405
+ minimum number of outbound connections each TaskExecutor
2406
+ connection pool can open to a configuration server.
2407
+
2408
+ Parameter only applies to sharded deployments.
2409
+
2410
+ The following example sets
2411
+ :parameter:`ShardingTaskExecutorPoolMinSizeForConfigServers` to ``2``
2412
+ during startup, which sets the minimum number of outbound connections
2413
+ each TaskExecutor connection pool can open to a configuration server
2414
+ to ``2``:
2415
+
2416
+ .. code-block:: bash
2417
+
2418
+ mongos --setParameter ShardingTaskExecutorPoolMinSizeForConfigServers=2
2419
+
2420
+ During runtime, you can also set the parameter with the
2421
+ :dbcommand:`setParameter` command:
2422
+
2423
+ .. code-block:: javascript
2424
+
2425
+ db.adminCommand( { setParameter: 1, ShardingTaskExecutorPoolMinSizeForConfigServers: 2 } )
2426
+
2337
2427
.. parameter:: ShardingTaskExecutorPoolRefreshRequirementMS
2338
2428
2339
2429
Type: integer
0 commit comments