[SERVER-45353] Increase AbstractOplogFetcher timeout in initial_sync_during_stepdown.js Created: 03/Jan/20  Updated: 29/Oct/23  Resolved: 06/Jan/20

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

Type: Bug Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Tess Avitabile (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2020-01-13
Participants:
Linked BF Score: 18

 Description   

initial_sync_during_stepdown.js causes the oplog query for initial sync to hang on a failpoint, which can cause it to time out. We should increase the network timeout to prevent this test from failing spuriously.

While we're here, we should ensure the test clears the logs before calling checkLog.



 Comments   
Comment by Githook User [ 06/Jan/20 ]

Author:

{'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}

Message: SERVER-45353 Increase AbstractOplogFetcher timeout in initial_sync_during_stepdown.js
Branch: master
https://github.com/mongodb/mongo/commit/a047dc462b3e9f828ad43ea1ff5c920f633b17e9

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