[SERVER-36985] Test single replica set transactions immediately after a rollbackViaRefetch Created: 04/Sep/18 Updated: 29/Oct/23 Resolved: 25/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | William Schultz (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | SWNA | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Repl 2018-09-10, Repl 2018-09-24, Repl 2018-10-08 | ||||||||
| Participants: | |||||||||
| Description |
|
Writes performed during rollbackViaRefetch are not timestamped. This could have poor interaction with transactions, which read at a timestamp. We should add test coverage for transactions that occur immediate after a rollbackViaRefetch, to ensure that when we set the read timestamp to the last applied time, that there exists a WT snapshot with that time that is safe to read from. |
| Comments |
| Comment by Githook User [ 25/Sep/18 ] |
|
Author: {'name': 'William Schultz', 'email': 'william.schultz@mongodb.com', 'username': 'will62794'}Message: |
| Comment by Githook User [ 25/Sep/18 ] |
|
Author: {'name': 'William Schultz', 'email': 'william.schultz@mongodb.com', 'username': 'will62794'}Message: |
| Comment by William Schultz (Inactive) [ 17/Sep/18 ] |
|
Code review for adding test is LGTM'd. Going to wait to push these changes until |
| Comment by William Schultz (Inactive) [ 10/Sep/18 ] |
|
Note that we should also get some coverage of this from the rollback fuzzer suites once we run a variant that uses rollbackViaRefetch on 4.0, since those fuzzer suites run transactions. |