Skip to content

Commit 74c96af

Browse files
author
Kay Kim
committed
DOCS-11809: rangeDeleterBatchDelayMS parameter
1 parent b73ab66 commit 74c96af

File tree

1 file changed

+37
-0
lines changed

1 file changed

+37
-0
lines changed

source/reference/parameters.txt

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1329,6 +1329,43 @@ Sharding Parameters
13291329

13301330
- :parameter:`ShardingTaskExecutorPoolMinSize`
13311331

1332+
1333+
.. parameter:: rangeDeleterBatchDelayMS
1334+
1335+
.. versionadded:: 3.4.17.
1336+
1337+
|mongod-only|
1338+
1339+
Type: Non-negative integer
1340+
1341+
Default: 20
1342+
1343+
The amount of time in milliseconds to wait before the next batch of
1344+
deletion during the cleanup stage of :ref:`chunk migration
1345+
<chunk-migration-procedure>` (or the :dbcommand:`cleanupOrphaned`
1346+
command).
1347+
1348+
In MongoDB 3.4, consider whether :ref:`_secondaryThrottle
1349+
<chunk-migration-replication>` is set before modifying the
1350+
:parameter:`rangeDeleterBatchDelayMS`. In MongoDB 3.4, the
1351+
:ref:`_secondaryThrottle replication delay
1352+
<chunk-migration-replication>` occurs after each document deletion
1353+
instead of after the batch deletion.
1354+
1355+
The following sets the :parameter:`rangeDeleterBatchDelayMS` to 200
1356+
milliseconds:
1357+
1358+
.. code-block:: sh
1359+
1360+
mongod --setParameter rangeDeleterBatchDelayMS=200
1361+
1362+
The parameter may also be set using the :dbcommand:`setParameter`
1363+
command:
1364+
1365+
.. code-block:: javascript
1366+
1367+
db.adminCommand( { setParameter: 1, rangeDeleterBatchDelayMS: 200 } )
1368+
13321369
.. parameter:: skipShardingConfigurationChecks
13331370

13341371
.. versionadded:: 3.4.11

0 commit comments

Comments
 (0)