[SERVER-39353] disable chaining in rollback_test.js Created: 01/Feb/19  Updated: 29/Oct/23  Resolved: 04/Feb/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.1.8

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

Issue Links:
Related
related to SERVER-39367 lastOpCommitted being reset on restar... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2019-02-11
Participants:
Linked BF Score: 19

 Description   

A secondary that is a part of the RollbackTest fixture should not ever consider the tiebreaker node as a valid sync source. To ensure this, we should disable chaining so that secondaries only choose the primary as a sync source. 



 Comments   
Comment by Githook User [ 04/Feb/19 ]

Author:

{'name': 'Pavi Vetriselvan', 'email': 'pvselvan@umich.edu', 'username': 'pvselvan'}

Message: SERVER-39353 disable chaining in rollback_test.js
Branch: master
https://github.com/mongodb/mongo/commit/18dde98af61a71b1bc5ec990c2184c5725d9b0c0

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