[SERVER-79175] Improve AutoStatsTracker usage in distinct and find commands Created: 21/Jul/23 Updated: 14/Dec/23 Resolved: 14/Dec/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jordi Olivares Provencio | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | techdebt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||||||||||||||||||
| Sprint: | Execution EMEA Team 2023-09-04, Execution EMEA Team 2023-09-18, Execution EMEA Team 2023-10-02, Execution EMEA Team 2023-10-16, CAR Team 2023-11-13, CAR Team 2023-11-27 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
With the move towards using acquisitions we discovered that a lot of our current testing infrastructure relies on entries being present in the profiling collection. Previously the necessary setup was performed within the AutoGetCollectionForReadCommand family of classes. With the move towards shard role acquisitions, we had to resort to manually setting it up in the commands, resulting in very large chunks of code that are replicated on other integrations. This ticket is about finding a better way to encapsulate this pattern. |
| Comments |
| Comment by Haley Connelly [ 07/Dec/23 ] |
|
Passing this ticket to the backlog so it can be re-prioritized after the investigation. Investigation Main Takeaway:
|
| Comment by Haley Connelly [ 02/Nov/23 ] |
For example, safe_secondary_reads_drop_recreate.js relies on the find operation to utilize the AutoStatsTracker so the profiler logs when a StaleConfig is thrown for a successful find operation. |