remove connPoolMaxShardedConnsPerHost from 5.0+ (#6053) (#6220)

* remove connPoolMaxShardedConnsPerHost from 5.0+

* three other parameters were also removed

* add other removed params to deprecated list

* remove file and folder that have not been used by the platform for 10 years

Author: MongoCaleb

source/includes/5.0-changes/removed-parameters.rst

@@ -20,3 +20,19 @@ MongoDB 5.0 removes the following server parameters:
         parameter. In 5.0+, collection and index creation inside of
         transactions is always enabled. You can no longer use the server
         parameter to disable this behavior.
+
+    * - ``connPoolMaxShardedConnsPerHost``
+
+      - MongoDB 5.0 removes the ``connPoolMaxShardedConnsPerHost`` server
+        parameter.
+
+    * - ``connPoolMaxShardedInUseConnsPerHost``
+
+      - MongoDB 5.0 removes the ``connPoolMaxShardedInUseConnsPerHost`` server
+        parameter.
+
+    * - ``shardedConnPoolIdleTimeoutMinutes``
+
+      - MongoDB 5.0 removes the ``shardedConnPoolIdleTimeoutMinutes`` server
+        parameter.
+

source/reference/parameters.txt

@@ -1122,74 +1122,21 @@ General Parameters
         }
       )
 
-.. parameter:: connPoolMaxShardedConnsPerHost
-
-   *Default*: 200
-
-   |both|
-
-   Sets the maximum size of the legacy connection pools for communication to the
-   shards. The size of a pool does not prevent the creation of
-   additional connections, but *does* prevent the connection pools from
-   retaining connections above this limit.
-
-   .. note::
-
-      The parameter is separate from the connections in TaskExecutor
-      pools. See :parameter:`ShardingTaskExecutorPoolMaxSize`.
-
-   Increase the :parameter:`connPoolMaxShardedConnsPerHost` value
-   **only** if the number of connections in a connection pool has a
-   high level of churn or if the total number of created connections
-   increase.
-
-   You can only set :parameter:`connPoolMaxShardedConnsPerHost` during
-   startup in the config file or on the command line. For example:
-
-   .. code-block:: bash
-
-      mongos --setParameter connPoolMaxShardedConnsPerHost=250
-
-
-.. parameter:: connPoolMaxShardedInUseConnsPerHost
-
-   |both|
-
-   Sets the maximum number of in-use connections at any given time for
-   the legacy sharded cluster connection pools.
-
-   By default, the parameter is unset.
-
-   You can only set :parameter:`connPoolMaxShardedConnsPerHost` during
-   startup in the config file or on the command line. For example:
-
-   .. code-block:: bash
-
-      mongos --setParameter connPoolMaxShardedInUseConnsPerHost=100
-
-   .. seealso::
-
-      :parameter:`connPoolMaxShardedConnsPerHost`
-
-.. parameter:: shardedConnPoolIdleTimeoutMinutes
+.. parameter:: httpVerboseLogging
 
    |both|
-
-   Sets the time limit that a connection in the legacy sharded cluster
-   connection pool can remain idle before being closed.
-
+   
+   Adds more verbose tracing for curl on Linux and macOS. Has no affect on Windows.
+    
    By default, the parameter is unset.
 
-   You can only set :parameter:`shardedConnPoolIdleTimeoutMinutes` during
+   You can only set ``httpVerboseLogging`` during
    startup in the config file or on the command line. For example:
 
    .. code-block:: bash
 
-      mongos --setParameter shardedConnPoolIdleTimeoutMinutes=10
+      mongos --setParameter httpVerboseLogging=true
 
-   .. seealso::
-
-      :parameter:`connPoolMaxShardedConnsPerHost`
 
 .. parameter:: connPoolMaxConnsPerHost
 
@@ -1257,10 +1204,6 @@ General Parameters
 
       mongos --setParameter globalConnPoolIdleTimeoutMinutes=10
 
-   .. seealso::
-
-      :parameter:`connPoolMaxShardedConnsPerHost`
-
 .. parameter:: cursorTimeoutMillis
 
    *Default*: 600000 (10 minutes)