[SERVER-64373] Implement Restoration for Parity Donor Fields in CurrentOp Created: 09/Mar/22  Updated: 06/Dec/22  Resolved: 14/Mar/22

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

Type: New Feature Priority: Major - P3
Reporter: Brett Nawrocki Assignee: [DO NOT USE] Backlog - Sharding NYC
Resolution: Won't Do Votes: 0
Labels: sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-64372 Track and Report Parity Donor Fields ... Closed
is depended on by SERVER-64392 Achieve Feature Parity Between Existi... Closed
Assigned Teams:
Sharding NYC
Participants:

 Description   

Implement restoration after step up for the following donor-only fields necessary for achieving parity with existing metrics:

  • countWritesDuringCriticalSection
  • totalCriticalSectionTimeElapsedSecs


 Comments   
Comment by Max Hirschhorn [ 14/Mar/22 ]

After the critical section is released the cleanup for resharding will completely quickly afterwards. The critical section should only be held for a short period of time (less than a few seconds) and so the need to support restoration when the odds of a failover in that window feels unnecessary.

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