[SERVER-36165] Clean up TrackingMetadata and attach it on all egress paths in mongos and mongod Created: 17/Jul/18 Updated: 06/Dec/22 Resolved: 01/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 4.1.1 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Participants: | |||||||||
| Description |
|
Currently, the TrackingMetadata is a decoration on OperationContext that contains boost::optional fields, and is attached only through the ShardRemote egress path. This ticket is to make TrackingMetadata itself a boost::optional decoration on OperationContext, and attach it in the ShardingEgressMetadataHook so it is attached on all egress paths. |
| Comments |
| Comment by Esha Maharishi (Inactive) [ 22/Aug/18 ] |
|
greg.mckeon yeah, for the time being. I have moved it back into "Open." |
| Comment by Gregory McKeon (Inactive) [ 22/Aug/18 ] |
|
esha.maharishi you've stopped work on this and |