[SERVER-86107] Do Not Require Orphan Filtering when a Collection has No Orphans Created: 02/Feb/24 Updated: 02/Feb/24 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.4.28, 7.0.6, 5.0.25, 6.0.14 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Matt Panton | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Catalog and Routing
|
| Participants: |
| Description |
|
Today with reads that don't provide the shard key in the filter of the query will execute a orphan filtering step to ensure that the shards responding to the query are the authoritative owners of the document. MongoDB could skip the orphan filtering step if there are no orphans for the collection at the time of the query. |