-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Labels:None
Description
Added a new server parameter called oplogFetcherUsesExhaust which can be set at startup. It will set whether oplog fetching will use exhaust cursors or not.
This ticket should also cover what this means; i.e. streaming replication vs oplog batches.
Description of Linked Ticket
As a part of this ticket, we should investigate whether we can set the socket timeout on the connection before the cursor is initialized (and the find command is run) and after the cursor is initialized. If possible, this would allow us to set a timeout for when the find is running and a separate getMore timeout.
We should also implement logic to create a new cursor when an error is encountered.
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
- documents
-
SERVER-45468 Create a DBClientCursor in the new oplog fetcher
- Closed
- is related to
-
DOCS-14315 Investigate changes in SERVER-54939: Investigate secondary batching behavior in v4.4
- Closed