[SERVER-73832] Consider replacing the use of ClusterAggregate::runAggregate in the PeriodicShardedIndexConsistencyChecker with Pipeline::makePipeline Created: 09/Feb/23 Updated: 12/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Cheahuychou Mao | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Cluster Scalability
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
The PeriodicShardedIndexConsistencyChecker is currently the only user of ClusterAggregate::runAggregate on mongod. Given the issues and complications described in SERVER-66270, SERVER-66271 and HELP-33769, we should consider replacing it with Pipeline::makePipeline instead (similar to what the SamplingBasedSplitPolicy does). |