[SERVER-67795] Add serverstatus tracking to know how many users use updateMany and DeleteMany Created: 05/Jul/22  Updated: 29/Oct/23  Resolved: 10/Oct/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.1, 4.4.19, 5.0.14, 6.0.4, 6.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Garaudy Etienne Assignee: Adi Zaimi
Resolution: Fixed Votes: 0
Labels: sharding-nyc-subteam3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
related to SERVER-72815 Extend serverstatus to track Document... Closed
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
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 19/Apr/23 ]

Author:

{'name': 'Adi Zaimi', 'email': 'adizaimi@yahoo.com', 'username': 'adizaimi'}

Message: SERVER-72815: Track document count and duration for updateMany and deleteMany calls (v4.4)

In SERVER-67795 we added serverstatus tracking to report number of times
updateMany and DeleteMany is called. We need to extend that tracking to
include number of documents updated/deleted from those commands
(cumulative and Max documents per call), as well as the time duration of
the commands (cumulative and Max duration per call). Extended the test
to verify correct behavior for these counters.

(cherry picked from commit 1562e66daf917f5eb43a2b410541aa94c2f396c6)
Branch: v4.4
https://github.com/mongodb/mongo/commit/3f02daf00ec30b0959a9edb82ad85ef53e7d8399

Comment by Githook User [ 18/Jan/23 ]

Author:

{'name': 'Adi Zaimi', 'email': 'adizaimi@yahoo.com', 'username': 'adizaimi'}

Message: SERVER-67795: Add serverstatus counters for updateMany, deleteMany calls(v4.4)
Branch: v4.4
https://github.com/mongodb/mongo/commit/02502cf9ba7cafdfcbef7810991b3cdc8ba08c4c

Comment by Githook User [ 10/Nov/22 ]

Author:

{'name': 'Adi Zaimi', 'email': 'adizaimi@yahoo.com', 'username': 'adizaimi'}

Message: SERVER-67795: Add serverstatus counters for updateMany, deleteMany calls(6.1)
Branch: v6.1
https://github.com/mongodb/mongo/commit/553067485afc74087de94ef11298a02298524fae

Comment by Githook User [ 09/Nov/22 ]

Author:

{'name': 'Adi Zaimi', 'email': 'adizaimi@yahoo.com', 'username': 'adizaimi'}

Message: SERVER-67795: Add serverstatus counters for updateMany, deleteMany calls (v6.0)
Branch: v6.0
https://github.com/mongodb/mongo/commit/96352a08d339f7f86e3b1365b834145ce5ad08e5

Comment by Githook User [ 07/Nov/22 ]

Author:

{'name': 'Adi Zaimi', 'email': 'adizaimi@yahoo.com', 'username': 'adizaimi'}

Message: SERVER-67795: Add serverstatus counters for updateMany, deleteMany calls(v5.0)
Branch: v5.0
https://github.com/mongodb/mongo/commit/da03719499bac3cfa1888ee1fd517ac30a738cba

Comment by Githook User [ 06/Oct/22 ]

Author:

{'name': 'Adi Zaimi', 'email': 'adizaimi@yahoo.com', 'username': 'adizaimi'}

Message: SERVER-67795: Add serverstatus counters for updateMany, deleteMany calls
Branch: master
https://github.com/mongodb/mongo/commit/2dbbbfeae172ca5f0ed13b0d72ea4d45db58e738

Comment by Adi Zaimi [ 22/Sep/22 ]

I resolved to have only two variables reported, updateManyCount and deleteManyCount  (rather than four – we don't need to have separate named variables for sharded vs replicaSet).

Generated at Thu Feb 08 06:09:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.