[SERVER-40422] Add a test to test replaying prepare oplog entry behind stable timestamp as part of replaying commit oplog entry during rollback recovery and with a very small wiredTiger cache size. Created: 01/Apr/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: | Task | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | Suganthi Mani |
| 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-04-08, Repl 2019-04-22 | ||||||||
| Participants: | |||||||||
| Description |
|
Modify commit_transaction_rollback_recovery_data_already_applied.js to test replaying prepare oplog entry behind stable timestamp as part of replaying commit oplog entry during rollback recovery and with a wiredTiger cache size of 1GB. |
| Comments |
| Comment by Githook User [ 16/Apr/19 ] | |||||||||||||||||||||||
|
Author: {'email': 'suganthi.mani@mongodb.com', 'name': 'Suganthi Mani', 'username': 'smani87'}Message: | |||||||||||||||||||||||
| Comment by Vamsi Boyapati [ 09/Apr/19 ] | |||||||||||||||||||||||
|
suganthi.mani, jocelyn.del-prado, I created a new ticket | |||||||||||||||||||||||
| Comment by Vamsi Boyapati [ 09/Apr/19 ] | |||||||||||||||||||||||
|
suganthi.mani, I think better to create a WT ticket. I will create the ticket and will link that to this SERVER ticket. | |||||||||||||||||||||||
| Comment by Suganthi Mani [ 08/Apr/19 ] | |||||||||||||||||||||||
|
vamsi.krishna, I thought our suspect was "__wt_txn_visible_all". But, anyways, I verified | |||||||||||||||||||||||
| Comment by Suganthi Mani [ 01/Apr/19 ] | |||||||||||||||||||||||
|
Currently, commit_transaction_rollback_recovery_data_already_applied.js test this below scenario.
Tested below following scenarios.
For case 1, the lesser cache size (which need cache eviction) makes __wt_txn_visible_all to be called which returns true as committed ts <= stable ts (pinned ts). As a result, the page is marked clean and the txn updates aren't aborted. |