[SERVER-42393] Race in setting failpoint during wt_file_helper.js assertStartInReplSet Created: 24/Jul/19  Updated: 29/Oct/23  Resolved: 26/Jul/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.3.1, 4.2.2

Type: Bug Priority: Major - P3
Reporter: Maria van Keulen Assignee: Maria van Keulen
Resolution: Fixed Votes: 0
Labels: test-fix
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2
Sprint: Execution Team 2019-07-29
Participants:
Linked BF Score: 21

 Description   

The wt_file_helper.js assertStartInReplSet function sets a failpoint that allows initial sync status information to be included in ReplSetGetStatus output after a successful initial sync (usually, this status information is unavailable after a successful initial sync). However, on a slow machine, the initial sync can complete before the failpoint is set, resulting in an undefined value for initialSyncStatus.

Setting this failpoint on start up of the replica set avoids this race.



 Comments   
Comment by Githook User [ 15/Nov/19 ]

Author:

{'name': 'Maria van Keulen', 'username': 'mvankeulen94', 'email': 'maria.vankeulen@mongodb.com'}

Message: SERVER-42393 Fix initial sync race in assertStartInReplSet

(cherry picked from commit 9fd91d29a22fb17017deccd92b642e3c2d494290)
Branch: v4.2
https://github.com/mongodb/mongo/commit/eca93e6211d6a9dc7893d9de8ebef8f99d6d8cc9

Comment by Matthew Russotto [ 25/Oct/19 ]

Requesting backport to 4.2 because of BF-15164; it appears this bug does not exist in 4.0 or earlier.

Comment by Githook User [ 26/Jul/19 ]

Author:

{'name': 'Maria van Keulen', 'email': 'maria@mongodb.com', 'username': 'mvankeulen94'}

Message: SERVER-42393 Fix initial sync race in assertStartInReplSet
Branch: master
https://github.com/mongodb/mongo/commit/9fd91d29a22fb17017deccd92b642e3c2d494290

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