[SERVER-67048] Replace ShardingDataTransformCumulativeMetrics DeregistrationFunction with ScopeGuard Created: 06/Jun/22 Updated: 27/Oct/23 Resolved: 26/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor - P4 |
| Reporter: | Brett Nawrocki | Assignee: | [DO NOT USE] Backlog - Sharding NYC |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | neweng, sharding-nyc-subteam1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding NYC
|
||||||||
| Participants: | |||||||||
| Description |
|
Currently, ShardingDataTransformCumulativeMetrics::registerInstanceMetrics() returns a lambda which must be later called by the instance metrics in order to deregister itself from the cumulative metrics. Instead, return a ScopeGuard created from that lambda so that the intent is more clear. |
| Comments |
| Comment by Randolph Tan [ 26/Jul/22 ] |
|
Ticket is now obsolete after changes in |