[SERVER-35095] snapshot_read_kill_operations.js should consider Interrupted as an acceptable getMore error Created: 18/May/18 Updated: 29/Oct/23 Resolved: 06/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.0-rc5, 4.1.1 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | William Schultz (Inactive) | Assignee: | Audrey Fang (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| 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: | Storage NYC 2018-06-18 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 11 | ||||||||
| Description |
|
The killOp phase of the snapshot_read_kill_operations.js workload targets any running getMore, not only one started by that thread. This means that it is possible for any thread's snapshot getMore to get killed while it is running, leading to a getMore returning an "operation was interrupted" error message. Presumably, we do want to test snapshot getMore operations getting concurrently killed, but we don't want the test to fail in this case. We should likely add a new acceptable error (Interrupted) to the doSnapshotGetMore call, so that the test does not fail in this case. |
| Comments |
| Comment by Githook User [ 08/Jun/18 ] |
|
Author: {'username': 'audreyfang', 'name': 'Audrey Fang', 'email': 'audrey.fang@10gen.com'}Message: (cherry picked from commit 1d056ffa9a765a7db6082b1597d656b3e51ae1be) |
| Comment by Githook User [ 06/Jun/18 ] |
|
Author: {'username': 'audreyfang', 'name': 'Audrey Fang', 'email': 'audrey.fang@10gen.com'}Message: |
| Comment by William Schultz (Inactive) [ 18/May/18 ] |
|
Assigning this to Storage backlog since it was introduced as part of Local Snapshot Reads testing. |