[SERVER-38059] Transactions write conflicts tests should clean up any transactions on failure Created: 09/Nov/18 Updated: 29/Oct/23 Resolved: 18/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.6, 4.1.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | William Schultz (Inactive) | Assignee: | William Schultz (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-11-19, Repl 2018-12-03 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 60 | ||||||||||||||||||||
| Description |
|
The transactions_write_conflicts.js and transactions_write_conflicts_unique_indexes.js tests run multiple pairs of transactions with writes in various interleavings. In the case that a transaction operation fails for some reason and throws an exception, the test may fail but leave a transaction open. This can lead to problems if we subsequently try to run consistency checks, for example, that require taking strong collection locks. To help this, we should have these tests clean up after themselves in case an exception is thrown, by aborting all transactions or killing the sessions they were using. |
| Comments |
| Comment by Githook User [ 21/Dec/18 ] |
|
Author: {'username': 'will62794', 'email': 'william.schultz@mongodb.com', 'name': 'William Schultz'}Message: (cherry picked from commit d167e6129256d6b60f01a19ed14bde5604255df7) |
| Comment by Githook User [ 18/Nov/18 ] |
|
Author: {'name': 'William Schultz', 'email': 'william.schultz@mongodb.com', 'username': 'will62794'}Message: |