[SERVER-44808] When we wait for the cloners, we also must deliver the callback to the network thread. Created: 22/Nov/19  Updated: 25/Nov/19  Resolved: 25/Nov/19

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

Type: Bug Priority: Major - P3
Reporter: Matthew Russotto Assignee: Matthew Russotto
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-44809 When we wait for the cloners, we also... Closed
Operating System: ALL
Participants:

 Description   

The interaction between the mock network thread and the cloner thread is somewhat perilous. In this case, we wait for the cloner by waiting on its future. This assures the callback has been scheduled to the mock network thread, but it has not actually been run. This results in a tiny race if the next operation is a runUntil and the scheduler is a bit slow at scheduling the callback.

Solution is to call runReadyNetworkOperations after waiting for the cloner in that case.



 Comments   
Comment by Matthew Russotto [ 25/Nov/19 ]

Closed. Not sure how I created two.

Comment by Judah Schvimer [ 25/Nov/19 ]

matthew.russotto, can this be closed as a duplicate of SERVER-44809?

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