[SERVER-64380] Track and Report New Coordinator Fields in CurrentOp Created: 09/Mar/22 Updated: 03/May/22 Resolved: 03/May/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: | Randolph Tan |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | sharding-nyc-subteam1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Sharding NYC 2022-05-16 | ||||||||
| Participants: | |||||||||
| Story Points: | 3 | ||||||||
| Description |
|
Add members to ShardingDataTransformInstanceMetrics to track the below newly added coordinator-only fields. These fields should also be reported when serializing the CurrentOp report. Fields:
|
| Comments |
| Comment by Randolph Tan [ 03/May/22 ] |
|
Looks like these fields are already implemented by the following tickets: |