[SERVER-34618] Fix race condition in retryable writes test Created: 23/Apr/18 Updated: 29/Oct/23 Resolved: 24/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.7.5 |
| Fix Version/s: | 3.7.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Blake Oler | Assignee: | Blake Oler |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2018-05-07 | ||||
| Participants: | |||||
| Linked BF Score: | 27 | ||||
| Description |
|
When running the failpoint tests on a replica set, it's possible for a race condition to exist in a find here. We will catch the exception a couple of lines above, but we can't verify with 100% accuracy that the write will have succeeded before the find is executed. To solve this race condition, we can change the assert.eq to an assert.soon. |
| Comments |
| Comment by Githook User [ 24/Apr/18 ] |
|
Author: {'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake', 'name': 'Blake Oler'}Message: |