[SERVER-50901] RollbackTest should wait for secondaries before doing data consistency checks Created: 12/Sep/20  Updated: 29/Oct/23  Resolved: 27/Oct/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.9.0, 4.4.3, 4.2.12

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:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.7, v4.4, v4.2
Sprint: Repl 2020-09-21, Repl 2020-10-05, Repl 2020-10-19, Repl 2020-11-02
Participants:
Linked BF Score: 11

 Description   

ReplSetTest already does this but RollbackTest should do the same (in checkDataConsistency).



 Comments   
Comment by Githook User [ 20/Nov/20 ]

Author:

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

Message: SERVER-50901 Wait for secondaries to be ready in RollbackTest.checkDataConsistency

(cherry picked from commit 2e2e949943bf3814b6b9871409d59e9641a3cd0d)
Branch: v4.4
https://github.com/mongodb/mongo/commit/04f74dce461f6ace3e9c57e4b749b8f287f5032a

Comment by Githook User [ 16/Nov/20 ]

Author:

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

Message: SERVER-50901 Wait for secondaries to be ready in RollbackTest.checkDataConsistency

(cherry picked from commit 2e2e949943bf3814b6b9871409d59e9641a3cd0d)
Branch: v4.2
https://github.com/mongodb/mongo/commit/03fb9e5576fc4aece81560ca2460116b27f0f018

Comment by Githook User [ 27/Oct/20 ]

Author:

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

Message: SERVER-50901 Wait for secondaries to be ready in RollbackTest.checkDataConsistency
Branch: master
https://github.com/mongodb/mongo/commit/2e2e949943bf3814b6b9871409d59e9641a3cd0d

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