DOCS-14036 New server parameter shutdownTimeoutMillisForSignaledShutdown

source/reference/parameters.txt

@@ -2673,6 +2673,35 @@ Sharding Parameters
 
       - :parameter:`maxTimeMSForHedgedReads`
 
+.. parameter:: mongosShutdownTimeoutMillisForSignaledShutdown
+
+   .. versionadded:: 5.0
+
+   *Type*: integer
+
+   *Default*: 15000
+
+   |mongos-only|
+
+   Specifies the time (in milliseconds) to wait for any ongoing database
+   operations to complete before initiating a shutdown of
+   :binary:`~bin.mongos`.
+
+   For example, to set the time to 250 milliseconds, you can issue the
+   following during startup:
+
+   .. code-block:: sh
+
+      mongos --setParameter mongosShutdownTimeoutMillisForSignaledShutdown=250
+
+   Or if using the :dbcommand:`setParameter` command in a
+   :binary:`~bin.mongo` shell connected to a running
+   :binary:`~bin.mongos`:
+
+   .. code-block:: javascript
+
+      db.adminCommand( { setParameter: 1, mongosShutdownTimeoutMillisForSignaledShutdown: 250 } )
+
 .. parameter:: replMonitorMaxFailedChecks
 
    *Available in MongoDB 3.2 only*

source/release-notes/5.0.txt

@@ -129,6 +129,14 @@ Networking
 General Improvements
 --------------------
 
+``mongosShutdownTimeoutMillisForSignaledShutdown`` Parameter
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Starting in MongoDB 5.0, the new parameter
+:parameter:`mongosShutdownTimeoutMillisForSignaledShutdown` specifies
+the time in milliseconds to wait for any ongoing database operations to
+complete before initiating a shutdown of :binary:`~bin.mongos`.
+
 ``reIndex`` Behavior Change
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~