-
Type:
New Feature
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Execution
-
None
-
None
-
None
-
None
-
None
-
None
-
None
even if it hasn't reached EOF or filled up the buffer. One possible implementation would be allowing callers to specify maximum time before yielding (this is different with maxTimeMs which will completely cause the command to error out).
This will allow caller to record progress (either with resume token if supported or just based on some fields from documents returned like oplog)
- is related to
-
SERVER-111929 Make resharding only skip cloning when it doesn't own any chunks
-
- Closed
-
-
SERVER-48526 Lengthy oplog scans may cause difficulty resuming change streams in a sharded cluster
-
- Backlog
-
- related to
-
SERVER-111124 Resharding Recipient That Owns No Data Never Marks Progress When Cloning
-
- Backlog
-