[SERVER-53911] Increment countWritesDuringCriticalSection Created: 20/Jan/21  Updated: 06/Dec/22  Resolved: 09/Jun/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: Lamont Nelson Assignee: [DO NOT USE] Backlog - Sharding NYC
Resolution: Duplicate Votes: 0
Labels: PM-234, PM-234-M3, PM-234-T-autocommits, sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-56499 Start resharding metrics on reshardin... Closed
Duplicate
duplicates SERVER-64372 Track and Report Parity Donor Fields ... Closed
Related
related to SERVER-53258 [Resharding] Reject writes in opObser... Closed
Assigned Teams:
Sharding NYC
Sprint: Sharding 2021-07-12, Sharding 2021-07-26
Participants:

 Description   

Should increment the relevant statistic in ReshardingMetrics repository.



 Comments   
Comment by Max Hirschhorn [ 29/Jul/21 ]

junhson.jean-baptiste, when I had chatted with Lamont about this ticket before we were thinking to increment the countWritesDuringCriticalSection metric when this uassert() would throw and the critical section is being held for a resharding operation rather than a chunk migration. Whether the critical section is held for a resharding operation can be known from whether currentMetadata has "reshardingFields" set.

Generated at Thu Feb 08 05:32:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.