[SERVER-57094] Plumb through duration timestamps in resharding state machines Created: 20/May/21 Updated: 06/Dec/22 Resolved: 09/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Blake Oler | 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: |
|
||||||||||||||||||||||||
| Assigned Teams: |
Sharding NYC
|
||||||||||||||||||||||||
| Sprint: | Sharding 2021-07-12, Sharding 2021-07-26, Sharding 2021-08-09 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Blake Oler [ 23/Aug/21 ] |
|
lamont.nelson max.hirschhorn to reassign. |