[SERVER-34236] Move configureFailpoint to replica set startup in read_committed_no_snapshots.js Created: 30/Mar/18  Updated: 29/Oct/23  Resolved: 07/May/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Vesselina Ratcheva (Inactive) Assignee: Vesselina Ratcheva (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 2018-04-09, Repl 2018-04-23, Repl 2018-05-07, Repl 2018-05-21
Participants:
Linked BF Score: 46

 Description   

It is currently possible that the no-snapshot secondary actually does manage to take a snapshot in between when the primary is elected and when the failpoint is triggered. We should have it start with the failpoint already turned on instead.



 Comments   
Comment by Githook User [ 07/May/18 ]

Author:

{'email': 'vesselina.ratcheva@10gen.com', 'name': 'Vesselina Ratcheva', 'username': 'vessy-mongodb'}

Message: SERVER-34236 Move configureFailpoint to replica set startup in read_committed_no_snapshots.js
Branch: master
https://github.com/mongodb/mongo/commit/79da069140feb5a62cb46640267c887d19d63e6c

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