-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
2023-07-25 Absolute unit
Summary
In the spirit of WT-8121, it would be great to have a similar test that, after inserting a certain amount of data, updates each key intensively. This comes after the investigation of WT-8690 where a checkpoint seems to time out because many updates need to be processed in the history store.
Motivation
- Does this affect any team outside of WT?
Had one MongoDB BF.
- How likely is it that this use case or problem will occur?
When a checkpoint is happening while eviction that started before is trying to process many updates in the HS.
- If the problem does occur, what are the consequences and how severe are they?
Checkpoint times out and WT aborts.
- Is this issue urgent?
It seems that we have more and more issues with the same error signature where checkpoint is blocked due to eviction not proceeding/being too slow.
Acceptance Criteria (Definition of Done)
Create a new cpp test that stresses the HS with a large number of updates over some time.
- is related to
-
WT-8690 Checkpoint timeout on an eviction gen
- Closed