-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
8
-
Storage Non-NYC 2018-06-18, Storage Non-NYC 2018-07-02
-
v3.6
When the oldest_timestamp is held back, and stable_timestamp moves forward after the new snapshot is taken for updates, the page eviction would abort during WT_SESSION.verify. This issue became more visible after SERVER-31767. It's only specific to MongoDB DEBUG builds (and corresponding WiredTiger diagnostic builds).
It would be helpful to add a Python test to cover this scenario:
- hold back oldest_timestamp
- insert data
- create a checkpoint
- run verify.
- is depended on by
-
SERVER-35259 Activate the snapshot window by setting the default to non-zero
- Closed
- related to
-
WT-5650 Fix a race condition between reading the WT_PAGE.modify field and the page being dirtied.
- Closed
-
SERVER-31767 Provide a window of snapshot history that is accessible for PIT reads
- Closed
-
SERVER-35251 Set the snapshot window default size to zero temporarily
- Closed