When truncating data from a file that has associated lookaside entries, the optimization to avoid reading pages in for fast truncate is not implemented - which results in reading a lot of pages in cache along with their lookaside entries (thus they will be read in as dirty). We could avoid reading those pages by checking the visbility in the WT_PAGE_LOOKASIDE structure.
- depends on
-
WT-3878 Iteration can lose its position when updating a limbo page
- Closed
-
WT-3933 test/format failure illegal WT_REF.state rolling back deleted page
- Closed
-
WT-3766 Lookaside sweep for obsolete updates
- Closed
- is depended on by
-
SERVER-32139 Oplog truncation creates large amount of dirty data in cache
- Closed
- is duplicated by
-
WT-3909 add truncate support to test/format
- Closed
- related to
-
WT-3987 Avoid reading lookaside pages in truncate fast path
- Closed
-
WT-3996 Test truncate with timestamps and lookaside
- Closed
- links to