-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
-
Storage Engines
-
StorEng - Refinement Pipeline
When running with the build type as Release or RelWithDebugInfo and for non-standalone cases, the log will contain a number of messages such as:
[2023/03/08 23:29:35.143] t: process 20032 running [2023/03/08 23:29:35.143] 0x12402880:[1678317476:167686][20032:0xffff90c51100], t, WT_SESSION.timestamp_transaction_uint: [WT_VERB_TIMESTAMP][NOTICE]: read timestamp (0, 35417) less than the oldest timestamp (0, 35499) [2023/03/08 23:29:35.143] 0x12402d08:[1678317476:171263][20032:0xffff92454100], t, WT_SESSION.timestamp_transaction_uint: [WT_VERB_TIMESTAMP][NOTICE]: read timestamp (0, 35412) less than the oldest timestamp (0, 35499) [2023/03/08 23:29:35.143] 0x12402d08:[1678317527:198278][20032:0xffff92454100], t, WT_SESSION.timestamp_transaction_uint: [WT_VERB_TIMESTAMP][NOTICE]: read timestamp (0, 118188) less than the oldest timestamp (0, 118516) [2023/03/08 23:29:35.143] 0x12402880:[1678317674:320086][20032:0xffff90c51100], t, WT_SESSION.timestamp_transaction_uint: [WT_VERB_TIMESTAMP][NOTICE]: read timestamp (0, 359943) less than the oldest timestamp (0, 360142) [2023/03/08 23:29:35.143] 0x12403190:[1678317722:371785][20032:0xffff91452100], t, WT_SESSION.timestamp_transaction_uint: [WT_VERB_TIMESTAMP][NOTICE]: read timestamp (0, 433273) less than the oldest timestamp (0, 433441) [2023/03/08 23:29:35.143] 0x12402880:[1678317722:386392][20032:0xffff90c51100], t, WT_SESSION.timestamp_transaction_uint: [WT_VERB_TIMESTAMP][NOTICE]: read timestamp (0, 433100) less than the oldest timestamp (0, 433441) [2023/03/08 23:29:35.143] t: WARNING: table.3 skipped verify because of EBUSY [2023/03/08 23:29:35.143] 0x12402880:[1678317822:934258][20032:0xffff90c51100], t, WT_SESSION.timestamp_transaction_uint: [WT_VERB_TIMESTAMP][NOTICE]: read timestamp (0, 580356) less than the oldest timestamp (0, 581186) [2023/03/08 23:29:35.143] 0x12403190:[1678317839:450318][20032:0xffff91452100], t, WT_SESSION.timestamp_transaction_uint: [WT_VERB_TIMESTAMP][NOTICE]: read timestamp (0, 600982) less than the oldest timestamp (0, 601069) [2023/03/08 23:29:35.143] 0x12403190:[1678317839:450619][20032:0xffff91452100], t, WT_SESSION.timestamp_transaction_uint: [WT_VERB_TIMESTAMP][NOTICE]: read timestamp (0, 600983) less than the oldest timestamp (0, 601069) [2023/03/08 23:29:35.143] t: WARNING: table.3 skipped verify because of EBUSY
These are not actually an issue as per __wt_txn_set_read_timestamp. Test/format uses the return code to pick a new timestamp.
This ticket should prevent these messages from being displayed in this case.
- is related to
-
WT-13364 Fix test/format exit with status 127 for an unknown reason
-
- Open
-