-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 4.2.22, 4.4.18, 5.0.14, 6.0.3, 6.1.0-rc4, 6.2.0-rc1
-
Component/s: None
-
Fully Compatible
-
ALL
-
v6.2, v6.1, v6.0, v5.0, v4.4, v4.2
-
Sharding EMEA 2022-12-12
-
(copied to CRM)
We recently discovered that dataSize command doesn't yield while scanning the index. This means that during its execution it will possibly block all the operations that requires exclusive access to the collection and considering that scanning the index for the entire collection can take long time this could have a huge impact on the customer workload.
Recently (SERVER-58356) we changed the yield policy to be INTERRUPT_ONLY so that we can at least kill the operation if needed.
The goal of this ticket to change the yielding policy to YIELD_AUTO for both when the command is called with estimate:true or false
- is related to
-
SERVER-58356 Cannot kill the dataSize operation
- Closed
-
SERVER-15650 Check for places where YIELD_AUTO could be enabled, but is not
- Closed
- related to
-
SERVER-71771 Defragmenter should cap chunk size estimation
- Closed