[SERVER-40757] Fix snapshot_read_kill_operations.js to handle read-only transactions that are aborted Created: 22/Apr/19 Updated: 29/Oct/23 Resolved: 13/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.12 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Saltz (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | Sharding 2019-05-20 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 13 | ||||||||||||||||
| Description |
|
It turns out that for read-only transactions, it is allowable that one shard commit and one shard abort, as long as the client receives an error (since "committing" for a read-only transaction doesn't do anything except wait for the data read to be majority committed). In this case, a read-only transaction was interrupted, causing one shard to commit and the other to abort. The test should be fixed to handle this case. |
| Comments |
| Comment by Esha Maharishi (Inactive) [ 13/May/19 ] |
|
The second part of |
| Comment by Githook User [ 13/May/19 ] |
|
Author: {'name': 'Esha Maharishi', 'username': 'EshaMaharishi', 'email': 'esha.maharishi@mongodb.com'}Message: Revert " This reverts commit ba844b4e81c3914b8a7017bd2a8c5ac4231c72ff.
The commit for |
| Comment by Matthew Russotto [ 10/May/19 ] |
|
Sounds OK to me. |
| Comment by Esha Maharishi (Inactive) [ 08/May/19 ] |
|
matthew.russotto, just a heads up, I'm hoping to make abortTransaction choose the first non-ignorable error as the top-level error to fix this issue without requiring the test to look at the raw responses, so I may end up removing the changes from the second commit on |
| Comment by Matthew Russotto [ 08/May/19 ] |
|
I fixed this for snapshot_read_kill_operations in |
| Comment by Matthew Saltz (Inactive) [ 22/Apr/19 ] |
|
This also applies for the random_moveChunk_broadcast* tests |