[SERVER-40095] disable chaining in rollback_wt_cache_full.js Created: 12/Mar/19  Updated: 29/Oct/23  Resolved: 13/Mar/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.1.9

Type: Bug Priority: Major - P3
Reporter: Benety Goh Assignee: Gregory Wlodarek
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: Storage NYC 2019-03-25
Participants:
Linked BF Score: 19

 Description   

rollback_wt_cache_full.js may fail during the CommonOps phase because a secondary is not syncing from the primary but rather from a secondary that has oplog application disabled. We should disable chaining in the ReplSetTest configuration. See SERVER-39353.



 Comments   
Comment by Githook User [ 13/Mar/19 ]

Author:

{'name': 'Gregory Wlodarek', 'username': 'GWlodarek', 'email': 'gregory.wlodarek@mongodb.com'}

Message: SERVER-40095 Disable chaining in rollback_wt_cache_full.js
Branch: master
https://github.com/mongodb/mongo/commit/49ce360e77d4fe92e83a5a8091772d283e68d7ef

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