[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: |