[SERVER-48185] Investigate using unittest::Barrier in MongosTopologyCoordinator unit tests Created: 13/May/20 Updated: 29/Oct/23 Resolved: 26/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Pavithra Vetriselvan | Assignee: | Pavithra Vetriselvan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2020-06-01 |
| Participants: |
| Description |
|
We should consider synchronizing the threads in MongosTopologyCoordinator unit tests in order to test sleep behavior. In a lot of our tests, we use unittest::barrier to synchronize stdx::thread execution, so that's something to look into. Ideally we would be able to call enterQuiesceModeAndWait() in our unittests so we can eliminate the need for enterQuiesceMode(). |
| Comments |
| Comment by Githook User [ 26/May/20 ] |
|
Author: {'name': 'Pavi Vetriselvan', 'email': 'pvselvan@umich.edu', 'username': 'pvselvan'}Message: |