[SERVER-39689] Test that transactions prepared before the stable timestamp are prepared after rollback Created: 20/Feb/19 Updated: 29/Oct/23 Resolved: 16/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.11 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Pavithra Vetriselvan | Assignee: | Pavithra Vetriselvan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Repl 2019-03-11, Repl 2019-03-25, Repl 2019-04-08, Repl 2019-04-22 | ||||||||
| Participants: | |||||||||
| Description |
|
Currently, since we pin the stable timestamp behind the prepare timestamp, we do not have rollback test coverage for transactions that were prepared before the stable timestamp. We would only allow it to move forward after its commit/abort oplog entry has been majority committed, which means that it would not be in the prepared state during a rollback. Once we stop pinning the stable timestamp, we should test that transactions prepared before the stable timestamp end up in the prepared state after a rollback. |
| Comments |
| Comment by Githook User [ 16/Apr/19 ] |
|
Author: {'name': 'Pavi Vetriselvan', 'username': 'pvselvan', 'email': 'pvselvan@umich.edu'}Message: |
| Comment by Githook User [ 10/Apr/19 ] |
|
Author: {'name': 'Pavi Vetriselvan', 'username': 'pvselvan', 'email': 'pvselvan@umich.edu'}Message: |