[SERVER-26930] backup_restore.js should await replication after fsm clients have stopped and hidden node has become secondary Created: 07/Nov/16  Updated: 05/Apr/17  Resolved: 25/Jan/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.4.3, 3.5.3

Type: Bug Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-26918 backup_restore.js - nodes should agre... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: Repl 2017-01-23, Repl 2017-02-13
Participants:
Linked BF Score: 0

 Description   

This fixes issues in test runs where there is an election after stopping the FSM clients.

In addition, we should consider disabling chaining in this test.



 Comments   
Comment by Githook User [ 08/Feb/17 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-26930 wait for nodes to agree on primary after shutting down FSM and CRUD clients

(cherry picked from commit 4e127648494ef32a1e77c2b4941673c1b99c62c8)
Branch: v3.4
https://github.com/mongodb/mongo/commit/cb816075d042914444016966061290dd13f03965

Comment by Githook User [ 25/Jan/17 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-26930 wait for nodes to agree on primary after shutting down FSM and CRUD clients
Branch: master
https://github.com/mongodb/mongo/commit/4e127648494ef32a1e77c2b4941673c1b99c62c8

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