[SERVER-34731] Fix race condition in read_concern_snapshot_yielding.js Created: 27/Apr/18 Updated: 29/Oct/23 Resolved: 23/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.0-rc1, 4.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ian Boros | Assignee: | Suganthi Mani |
| 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 | ||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||
| Sprint: | Repl 2018-05-21, Repl 2018-06-04 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 66 | ||||||||||||
| Description |
|
In read_concern_snapshot_yielding.js there's some code which waits for an operation to start. The test is racy because the test assumes that once waitForOpId() has returned, the operation is hanging on a fail point. This is not necessarily true, and can cause the test to fail if the following happens: 1) The operation starts, but does not reach the failPoint I'm marking this as depends-on |
| Comments |
| Comment by Githook User [ 23/May/18 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Author: {'username': 'smani87', 'name': 'Suganthi Mani', 'email': 'suganthi.mani@mongodb.com'}Message: (cherry picked from commit 084e69ab140c37b010146a3acdb3da7e4977d9ea) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Githook User [ 23/May/18 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Author: {'username': 'smani87', 'name': 'Suganthi Mani', 'email': 'suganthi.mani@mongodb.com'}Message: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Ian Boros [ 27/Apr/18 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Something like this should fix it:
|