@@ -2325,7 +2325,54 @@ Sharding Parameters
2325
2325
pools, where ``n`` is the number of cores. See
2326
2326
:parameter:`taskExecutorPoolSize`.
2327
2327
2328
- .. seealso:: :parameter:`ShardingTaskExecutorPoolMinSize`
2328
+ .. seealso::
2329
+
2330
+ :parameter:`ShardingTaskExecutorPoolMinSize`
2331
+
2332
+ .. parameter:: ShardingTaskExecutorPoolMaxSizeForConfigServers
2333
+
2334
+ .. versionadded:: 4.2.22
2335
+
2336
+ Type: integer
2337
+
2338
+ Default: -1
2339
+
2340
+ |both|
2341
+
2342
+ Optional override for :parameter:`ShardingTaskExecutorPoolMaxSize` to
2343
+ set the maximum number of outbound connections each TaskExecutor
2344
+ connection pool can open to a :ref:`configuration server
2345
+ <sharding-config-server>`.
2346
+
2347
+ When set to:
2348
+
2349
+ - ``-1``, :parameter:`ShardingTaskExecutorPoolMaxSize` is used. This
2350
+ is the default.
2351
+
2352
+ - an integer value greater than ``-1``, overrides the
2353
+ maximum number of outbound connections each TaskExecutor
2354
+ connection pool can open to a configuration server.
2355
+
2356
+ Parameter only applies to sharded deployments.
2357
+
2358
+ The following example sets
2359
+ :parameter:`ShardingTaskExecutorPoolMaxSizeForConfigServers` to ``2``
2360
+ during startup, which sets the maximum number of outbound connections
2361
+ each TaskExecutor connection pool can open to a configuration server
2362
+ to ``2``:
2363
+
2364
+ .. code-block:: bash
2365
+
2366
+ mongos --setParameter ShardingTaskExecutorPoolMaxSizeForConfigServers=2
2367
+
2368
+ During runtime, you can also set the parameter with the
2369
+ :dbcommand:`setParameter` command:
2370
+
2371
+ .. code-block:: javascript
2372
+
2373
+ db.adminCommand( { setParameter: 1, ShardingTaskExecutorPoolMaxSizeForConfigServers: 2 } )
2374
+
2375
+ .. _sharding-pool-minsize-parameters:
2329
2376
2330
2377
.. parameter:: ShardingTaskExecutorPoolMinSize
2331
2378
@@ -2365,6 +2412,49 @@ Sharding Parameters
2365
2412
2366
2413
.. seealso:: :parameter:`ShardingTaskExecutorPoolMaxSize`
2367
2414
2415
+ .. parameter:: ShardingTaskExecutorPoolMinSizeForConfigServers
2416
+
2417
+ .. versionadded:: 4.2.22
2418
+
2419
+ Type: integer
2420
+
2421
+ Default: -1
2422
+
2423
+ |both|
2424
+
2425
+ Optional override for :parameter:`ShardingTaskExecutorPoolMinSize` to
2426
+ set the minimum number of outbound connections each TaskExecutor
2427
+ connection pool can open to a :ref:`configuration server
2428
+ <sharding-config-server>`.
2429
+
2430
+ When set to:
2431
+
2432
+ - ``-1``, :parameter:`ShardingTaskExecutorPoolMinSize` is used. This
2433
+ is the default.
2434
+
2435
+ - an integer value greater than ``-1``, overrides the
2436
+ minimum number of outbound connections each TaskExecutor
2437
+ connection pool can open to a configuration server.
2438
+
2439
+ Parameter only applies to sharded deployments.
2440
+
2441
+ The following example sets
2442
+ :parameter:`ShardingTaskExecutorPoolMinSizeForConfigServers` to ``2``
2443
+ during startup, which sets the minimum number of outbound connections
2444
+ each TaskExecutor connection pool can open to a configuration server
2445
+ to ``2``:
2446
+
2447
+ .. code-block:: bash
2448
+
2449
+ mongos --setParameter ShardingTaskExecutorPoolMinSizeForConfigServers=2
2450
+
2451
+ During runtime, you can also set the parameter with the
2452
+ :dbcommand:`setParameter` command:
2453
+
2454
+ .. code-block:: javascript
2455
+
2456
+ db.adminCommand( { setParameter: 1, ShardingTaskExecutorPoolMinSizeForConfigServers: 2 } )
2457
+
2368
2458
.. parameter:: ShardingTaskExecutorPoolRefreshRequirementMS
2369
2459
2370
2460
Type: integer
0 commit comments