-
Type:
Task
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Cache and Eviction
-
Storage Engines
-
StorEng - Refinement Pipeline
-
None
Summary
It seems the cache size is not considered when trying to insert data bigger than its value. We have already encountered issues where we would go beyond the cache size limit with the cpp suite and it resurfaced again while implementing WT-9094. I am attaching a python repro and the T2 stats it generates.
Motivation
- Does this affect any team outside of WT?
It could.
- How likely is it that this use case or problem will occur?
Every time unless I am not using WT correctly
- If the problem does occur, what are the consequences and how severe are they?
WT could use more memory than expected
- Is this issue urgent?
Not sure
Acceptance Criteria (Definition of Done)
Understand if this behavior is correct and if not, fix it.
- duplicates
-
WT-12931 Suggestion: Rollback or throw other error when a transaction inserts/updates a value bigger than the cache / dirty trigger
-
- Open
-
- is duplicated by
-
WT-11039 failed: cppsuite-hs-cleanup-default cache usage exceeded during test [v6.0]
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
-
- Closed
-