[SERVER-29430] [v3.2] Increase awaitSecondary timeout in initial_sync_cloner_dups.js to at least 10 minutes Created: 02/Jun/17  Updated: 06/Dec/22  Resolved: 31/May/18

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

Type: Bug Priority: Major - P3
Reporter: William Schultz (Inactive) Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-26357 3.0 - increase timeouts for test noPa... Closed
Assigned Teams:
Replication
Operating System: ALL
Backport Requested:
v3.0
Participants:
Linked BF Score: 0

 Description   

The initial_sync_cloner_dups.js test waits for a secondary node to complete initial sync here, but there have been instances, such as in BF-5576 of this initial sync taking longer than the prescribed timeout of 2 minutes, due to slow mmap flushing. These timeouts should be increased to at least 10 minutes to account for these kinds of scenarios.

This only applies to 3.2, since later versions of this test just use the default timeout of replsettest.js


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