-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
3
-
Storage Engines 2019-07-01, Storage Engines 2019-07-19
assert=read_timestamp fails during recovery.
This is fallout from WT-4733 where support was added in turning on assert=read_timestamp. One representative failure is:
http://build.wiredtiger.com:8080/job/wiredtiger-test-format-recovery/2871/console
The failure looks like:
[1561562700:686665][24271:0x3ff94074710], wt, file:wt.wt, WT_CURSOR.search: __wt_txn_search_check, 1087: read_timestamp required and none set on this transaction: Invalid argument [1561562700:686991][24271:0x3ff94074710], wt, file:wt.wt, txn-recover: __txn_op_apply, 307: operation apply failed during recovery: operation type 10 at LSN 1/72796288: Invalid argument [1561562700:687054][24271:0x3ff94074710], wt, file:wt.wt, txn-recover: __wt_txn_recover, 769: Recovery failed: Invalid argument
- is caused by
-
WT-4733 Change test/format to do longer-term repeatable read testing
- Closed