[SERVER-43694] Change waitForState to awaitSecondaryNodes in initial_sync_write_conflict.js Created: 27/Sep/19  Updated: 29/Oct/23  Resolved: 04/Oct/19

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

Type: Bug Priority: Major - P3
Reporter: Jason Chan Assignee: Jason Chan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2
Sprint: Repl 2019-10-07
Participants:

 Description   

We should change the call from replSet.waitforState to replSet.awaitSecondaryNodes() in initial_sync_write_conflict.js. replSet.waitForState queries the primary to check the states of the nodes in the replica set which could be stale. In this test, it is possible that the secondary has just restarted and is going through startup but waitForState returns that the secondary has reached SECONDARY state.



 Comments   
Comment by Githook User [ 11/Oct/19 ]

Author:

{'name': 'Jason Chan', 'username': 'jasonjhchan', 'email': 'jason.chan@mongodb.com'}

Message: SERVER-43694 Change waitForState to awaitSecondaryNodes in initial_sync_write_conflict.js

(cherry picked from commit c0da48bb14fe1329e375265be0f731baa9f07577)
Branch: v4.2
https://github.com/mongodb/mongo/commit/87a606d9d6075e0484f4e40047156b4b4916380c

Comment by Githook User [ 04/Oct/19 ]

Author:

{'username': 'jasonjhchan', 'email': 'jason.chan@mongodb.com', 'name': 'Jason Chan'}

Message: SERVER-43694 Change waitForState to awaitSecondaryNodes in initial_sync_write_conflict.js
Branch: master
https://github.com/mongodb/mongo/commit/c0da48bb14fe1329e375265be0f731baa9f07577

Comment by Steven Vannelli [ 30/Sep/19 ]

jason.chan please create the backport tickets as needed for this one

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