[SERVER-54149] Oplog fetcher mock needs to delay its destruction until it is no longer being called from the test Created: 29/Jan/21  Updated: 29/Oct/23  Resolved: 03/Feb/21

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

Type: Bug Priority: Major - P3
Reporter: Matthew Russotto Assignee: Matthew Russotto
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: Repl 2021-02-08
Participants:
Linked BF Score: 0

 Description   

The test code may have an unowned reference to the OplogFetcherMock. If the mock is destroyed while the test code is enqueuing a batch (e.g. because the batch is invalid), the test will crash. We should delay destruction of the mock until the call is finished.

Making sure the unowned reference remains valid between calls is up to the test code itself, however.



 Comments   
Comment by Githook User [ 03/Feb/21 ]

Author:

{'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}

Message: SERVER-54149 Oplog fetcher mock needs to delay its destruction until it is no longer being called from the test
Branch: master
https://github.com/mongodb/mongo/commit/be490056343fed47cb1afe5c3b27c0247fe2da2a

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