When RTS is printing the verbose message of ONDISK_ABORT_TW, it overwrites the durable timestamp and commit timestamp values with the prepared timestamp, and it leads to the following output where no timestamp values are being logged.
[ONDISK_ABORT_TW] on-disk update aborted with time_window=(0, 0)/(0, 0)/(0, 0)/0/3005.
Fix the verbose message to print the proper timestamp values.
- is caused by
-
WT-15076 Print the prepare ts and prepare id in __wt_time_window_to_string
-
- Closed
-
- is related to
-
WT-10275 Extra RTS log messages
-
- Closed
-
- related to
-
WT-15608 Aggregated timestamp validation can fail with a 0 timestamped page deleted structure
-
- Closed
-
-
WT-15616 dist/s_all pass with failed s_test_suite_no_executable check
-
- Closed
-
-
WT-15041 Handle abandoned checkpoints in PALM
-
- Closed
-
-
WT-15534 Enable timestamp usage check for fast truncate on non-standalone build
-
- Closed
-
-
WT-15622 Skip eviction walk on read only btrees if we are only look for dirty and updates data
-
- Closed
-
-
WT-15595 Ignore eviction target/trigger in follower mode
-
- Closed
-
-
WT-15634 failed: s-outdated-fixmes on infrequent-checks [wiredtiger @ fbae136d]
-
- Closed
-