-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
v6.1, v6.0, v5.0, v4.4
-
Sharding 2022-07-25, Sharding 2022-08-08, Sharding 2022-08-22, Sharding 2022-09-05, Sharding 2022-09-19, Sharding 2022-10-03, Sharding 2022-10-17
Before we do updateMany without shard key, we would like to see if we can constrain the problem space.
We need to know how many users are using updateMany and DeleteMany across replica sets and sharded clusters.
- related to
-
SERVER-72815 Extend serverstatus to track Document count and Duration for updateMany and deleteMany
- Closed