[SERVER-28719] Use a rescheduling fail point instead of blocking on a condition variable in certain replication unit tests Created: 10/Apr/17  Updated: 06/Dec/17  Resolved: 10/Apr/17

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

Type: Task Priority: Major - P3
Reporter: Andy Schwerin Assignee: Andy Schwerin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

There are a handful of replication unit tests that depend on heartbeat-reconfigures executing in a separate thread from the rest of the tasks managed by the replication task executor (ReplicationExecutor). This task is to update the support code and the tests to not rely on this implementation behavior.



 Comments   
Comment by Githook User [ 10/Apr/17 ]

Author:

{u'name': u'Andy Schwerin', u'email': u'Andy Schwerin schwerin@mongodb.com'}

Message: SERVER-28719 Use a rescheduling fail point instead of blocking on a condition variable in some unit tests.
Branch: master
https://github.com/mongodb/mongo/commit/3dfb9f67d20188042ce019d2720593935da27b33

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