[SERVER-45468] Create a DBClientCursor in the new oplog fetcher Created: 09/Jan/20  Updated: 29/Oct/23  Resolved: 04/Feb/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.3.4

Type: Task Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Samyukta Lanka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-13389 Investigate changes in SERVER-45468: ... Closed
Duplicate
is duplicated by SERVER-44712 Add a server parameter switch to cont... Closed
Related
is related to SERVER-46053 NewOplogFetcher should send term/last... Closed
is related to SERVER-46054 Incorrect invariant in NewOplogFetche... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2020-02-10
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 04/Feb/20 ]

Author:

{'name': 'Samyukta Lanka', 'username': 'lankas', 'email': 'samy.lanka@mongodb.com'}

Message: SERVER-45468 Create a DBClientCursor in the new oplog fetcher
Branch: master
https://github.com/mongodb/mongo/commit/eac7c6e8efe97299cddbd106d9ea4b2ed90e846d

Generated at Thu Feb 08 05:08:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.