Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Critical - P2
Fix Version/s: WT10.0.0, 4.9.0, 4.4.3
Affects Version/s: None
Component/s: None
Labels:
- data-corruption
- wt-notfound

Sprint:
Storage - Ra 2020-08-24, Storage - Ra 2020-11-16
Story Points:
3

In ~~WT-4738~~ we added a new assertion that enforced the commit timestamp for non-prepared transactions is newer than the timestamps of all active readers. That caused some test fallout, so we disabled the assertion in ~~WT-4779~~.

This ticket involves understanding the test fallout and re-enabling the assertion.

depends on

SERVER-41333 Initial Sync and Shutdown write to the minValid document at the lastApplied

Closed

SERVER-50398 appliedThrough document write and background validation reads could use the same timestamp

Closed

SERVER-41178 TransactionHistoryIterator should do untimestamped reads during rollback recovery

Closed

is related to

WT-4738 Tighten rules around use of timestamps

Closed

WT-4779 Disable new assertion related to timestamp consistency

Closed

Assignee:: Haribabu Kommi
Reporter:: Alexander Gorrod
Votes:: 0 Vote for this issue
Watchers:: 11 Start watching this issue

Created:: May 14 2019 02:27:11 AM UTC
Updated:: Oct 29 2023 04:45:40 PM UTC
Resolved:: Nov 05 2020 11:04:00 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates