[SERVER-73885] Some resharding metric counters use int32_t instead of int64_t causing an overflow Created: 10/Feb/23  Updated: 29/Oct/23  Resolved: 27/Mar/23

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 7.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Kshitij Gupta Assignee: Brett Nawrocki
Resolution: Fixed Votes: 0
Labels: sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Duplicate
duplicates SERVER-73078 Implement MovePrimaryMetrics Closed
Problem/Incident
is caused by SERVER-64376 Track and Report Parity Recipient App... Closed
Related
Assigned Teams:
Sharding NYC
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v6.3
Sprint: Sharding NYC 2023-03-20
Participants:

 Description   

These counters can overflow if the collection being resharded is large enough.

Link to counters: https://github.com/mongodb/mongo/blob/f15f2bf8958557b4e8fccc6e8e1c7c8c5834d209/src/mongo/db/s/sharding_data_transform_instance_metrics.h#L158-L161



 Comments   
Comment by Brett Nawrocki [ 16/Mar/23 ]

Fixed as part of SERVER-73078.

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