Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 6.1.1, 4.4.19, 5.0.14, 6.0.4, 6.2.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- sharding-nyc-subteam3

Backwards Compatibility:
Fully Compatible
Backport Requested:

v6.1, v6.0, v5.0, v4.4
Sprint:
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
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

Assignee:: Adi Zaimi
Reporter:: Garaudy Etienne
Participants:: Adi Zaimi, Garaudy Etienne, Githook User
Votes:: 0 Vote for this issue
Watchers:: 7 Start watching this issue

Created:: Jul 05 2022 08:50:46 PM UTC
Updated:: Oct 29 2023 09:36:00 PM UTC
Resolved:: Oct 10 2022 03:28:48 PM UTC
Confidence Status Last Update:: 22/Sep/22 7:37 PM