[SERVER-48069] Switch OplogApplierImplTest to use WiredTiger Created: 09/May/20  Updated: 14/May/20  Resolved: 14/May/20

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

Type: Bug Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Lingzhi Deng
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Operating System: ALL
Sprint: Repl 2020-05-18
Participants:
Linked BF Score: 0

 Description   

ephemeralForTest cursors are not thread_safe (SERVER-42213). So fillWriterVectors could race with oplog insertions when trying to readTransactionOperationsFromOplogChain. We switched idempotency tests to use WiredTiger in SERVER-45288. I think we may need to do the same for all OplogApplierImplTest in general.

We should be careful with oplog visibility issues though after switching to WiredTiger. SERVER-42925 fixed oplog visiblity issues in idempotency tests by introducing an oplogDiskLocRegister call to update the oplog visibility timestamp after applying each batch. But in non-idempotency tests like this one, we call applyOplogBatch directly which I believe doesn't update the oplog visibility timestamp.



 Comments   
Comment by Lingzhi Deng [ 14/May/20 ]

Marking this as "Won't fix" for now given the low value and the relatively high risk of destabilizing older versions builds.

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