@@ -127,18 +127,28 @@ you may prefer to include a pause in-between iterations.
127
127
Alternatively, to mitigate the impact of :dbcommand:`cleanupOrphaned`,
128
128
you may prefer to run the command at off peak hours.
129
129
130
- It is also possible to tune the performance impact of :dbcommand:`cleanupOrphaned`
131
- with two server parameters :parameter:`rangeDeleterBatchSize`
132
- and :parameter:`rangeDeleterBatchDelayMS`
130
+ It is also possible to tune the performance impact of
131
+ :dbcommand:`cleanupOrphaned` with the parameters,
132
+ :parameter:`rangeDeleterBatchSize` and
133
+ :parameter:`rangeDeleterBatchDelayMS`. For example:
133
134
134
- To limit the number of documents deleted per batch, you can set
135
- `rangeDeleterBatchSize` to a small value such as `32 `.
135
+ - To limit the number of documents deleted per batch, you can set
136
+ :parameter: `rangeDeleterBatchSize` to a small value such as ``32` `.
136
137
137
- To add an additional delay between batch deletions, you can set
138
- `rangeDeleterBatchDelayMS` above the current default of `20` milliseconds.
138
+ - To add an additional delay between batch deletions, you can set
139
+ :parameter:`rangeDeleterBatchDelayMS` above the current default of
140
+ ``20`` milliseconds.
139
141
140
- Note that these affect all range deletion including normal
141
- :doc:`chunk migration</core/sharding-balancer-administration/#chunk-migration-procedure>`.
142
+ .. note::
143
+
144
+ Changing :parameter:`rangeDeleterBatchSize` and
145
+ :parameter:`rangeDeleterBatchDelayMS` affect all range deletion,
146
+ including normal :ref:`chunk
147
+ migration<chunk-migration-procedure>`.
148
+
149
+ If you are temporarily modifying one or both of these parameters to
150
+ run :dbcommand:`cleanupOrphaned`, return to their previous values
151
+ after you run :dbcommand:`cleanupOrphaned`.
142
152
143
153
.. _cleanupOrphaned-determine-range:
144
154
0 commit comments