We found a test case using rollback_to_stable that didn't exclude data with a durable timestamp greater than the stable timestamp as it should.
A new test case added as part of SERVER-40422 is failing. The data with the durable timestamp greater than the current stable timestamp is not discarded when rollback to stable is performed.
testcase is : commit_transaction_rollback_recovery_data_already_applied.js
- is depended on by
-
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.
- Closed