Operational Defect Database

BugZero found this defect 2457 days ago.

MongoDB | 389625

[SERVER-29430] [v3.2] Increase awaitSecondary timeout in initial_sync_cloner_dups.js to at least 10 minutes

Last update date:

12/6/2022

Affected products:

MongoDB Server

Affected releases:

3.2.13

Fixed releases:

No fixed releases provided.

Description:

Info

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

Top User Comments


Additional Resources / Links

Share:

BugZero Risk Score

Coming soon

Status

Closed

Have you been affected by this bug?

cost-cta-background

Do you know how much operational outages are costing you?

Understand the cost to your business and how BugZero can help you reduce those costs.

Discussion

Login to read and write comments.

Have you ever...

had your data corrupted from a

VMware

bug?

Search:

...