[SERVER-38011] Support oplogReplay in count queries Created: 07/Nov/18  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Kelsey Schubert Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to TOOLS-2068 mongodump oplog delay Closed
Assigned Teams:
Query Execution
Participants:

 Description   

As discussed TOOLS-2068, users typically would expect a count to perform in equivalent or less time. With a large oplog, this can make count commands take a significant amount of time compared to a find with the same predicate.



 Comments   
Comment by Ian Whalen (Inactive) [ 09/Nov/18 ]

Likely implementation approach is to add oplogStart optimization to the aggregation framework.

Generated at Thu Feb 08 04:47:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.