[SERVER-64379] Implement Restoration for New Donor and Recipient Fields in CurrentOp Created: 09/Mar/22  Updated: 29/Oct/23  Resolved: 22/Apr/22

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

Type: New Feature Priority: Major - P3
Reporter: Brett Nawrocki Assignee: Randolph Tan
Resolution: Fixed Votes: 0
Labels: sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-64378 Track and Report New Donor and Recipi... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding NYC 2022-04-18, Sharding 2022-05-02
Participants:
Story Points: 2

 Description   

Implement restoration after step up for the following newly added donor and recipient fields:

  • (donor) countReadsDuringCriticalSection (we aren't going to track the number of reads during the critical section in $currentOp across failover because the critical section duration is expected to be very short)
  • (recipient) countWritesToStashCollections (this will be done through a new field in the resharding oplog progress applier document)


 Comments   
Comment by Githook User [ 22/Apr/22 ]

Author:

{'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}

Message: SERVER-64379 Implement restoration of countWritesToStashCollections
Branch: master
https://github.com/mongodb/mongo/commit/983a7174c6d792049ef0f54e36a55f93801df89c

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