[SERVER-36975] Fix race condition in read_concern_snapshot_catalog_invalidation.js Created: 04/Sep/18 Updated: 29/Oct/23 Resolved: 05/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.3, 4.1.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Tess Avitabile (Inactive) |
| 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-09-10 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 7 | ||||||||||||
| Description |
|
In read_concern_snapshot_catalog_invalidation.js, there is code to wait for an operation to start. The test is racy because the test assumes that once waitForOp() 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 fail point |
| Comments |
| Comment by Githook User [ 05/Sep/18 ] |
|
Author: {'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}Message: (cherry picked from commit 0ee0cabe0a12006080521f47ebb43f36205736c7) |
| Comment by Githook User [ 05/Sep/18 ] |
|
Author: {'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}Message: |
| Comment by Githook User [ 05/Sep/18 ] |
|
Author: {'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}Message: Revert " This reverts commit bd982824a7967b5e518bf9255b8f5e051bdaff7d. |
| Comment by Githook User [ 05/Sep/18 ] |
|
Author: {'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}Message: |