-
Type: Task
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Sharding NYC
-
Sharding 2021-07-12, Sharding 2021-07-26, Sharding 2021-08-09
In each of the resharding machines, before starting or ending a specific metrics time interval (example here), make sure that a state transition that updates a state also persists that timestamp to disk. For the recipient specifically, that will involve plumbing through the state transition code here until creating a new entry for the setBuilder here.
It will be easiest to start with the coordinator or recipient to figure out the pattern needed. I'm specifically requesting to give me a standalone committable patch set for each machine, to make it easier to review and to ensure that the pattern-matching will be done correctly for subsequent machines.
- depends on
-
SERVER-57266 Create IDL representations for resharding metrics time intervals.
- Closed
- duplicates
-
SERVER-64372 Track and Report Parity Donor Fields in CurrentOp
- Closed
-
SERVER-64374 Track and Report Parity Recipient Copying Fields in CurrentOp
- Closed
-
SERVER-64376 Track and Report Parity Recipient Applying Fields in CurrentOp
- Closed