Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Blocker - P1
Fix Version/s: WT11.0.0, 6.1.0-rc0, 6.0.4, 5.0.15
Affects Version/s: None
Component/s: None
Labels:

Sprint:
Storage - Ra 2022-05-16, Storage - Ra 2022-05-30, Storage - Ra 2022-06-13
Story Points:
13
Case:

Backport Requested:

v6.0, v5.3, v5.0, v4.4

In prepared rollback of the onpage value, we restore the latest value we wrote to the history store. If the checkpoint is running at the time, we will not delete the restored value from the history store. This causes triggering out of order fix when the restored value is written to the history store again. However, if checkpoint is running at the time, it will panic the system as handling out of order timestamp fix is not allowed.

causes

WT-9592 Rollback to stable should also clear WT_UPDATE_TO_DELETE_FROM_HS flag

Closed

WT-9765 Fix handling a prepared commit after a prepared rollback with eviction failure

Closed

WT-9705 Fix accidentally freeing update on the update chain in prepared commit

Closed

WT-9805 Save the updates need to be deleted from history store and delete them later

Closed

WT-9428 Fix two asserts in rec_visibility.c

Closed

WT-9701 Segfault in reconciliation

Closed

depends on

WT-9356 We cannot evict mixed mode tombstone when checkpoint is running

Closed

is caused by

WT-8074 Panic in reconciliation if inserting content into the history fails

Closed

is depended on by

WT-9381 Remove checkpoint reserved transaction id

Closed

is related to

WT-9249 Compare and fix the start durable timestamp if it is greater than ooo timestamp

Closed

(1 causes, 1 depends on, 1 is caused by, 1 is depended on by, 1 is related to)

Assignee:: Chenhao Qu
Reporter:: Chenhao Qu
Votes:: 0 Vote for this issue
Watchers:: 18 Start watching this issue

Created:: May 02 2022 04:22:20 AM UTC
Updated:: Oct 29 2023 04:39:39 PM UTC
Resolved:: Jun 02 2022 12:45:55 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates