-
Type:
Task
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Duplicate
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Story Points:0
-
Sprint:Storage - Ra 2020-10-05
At present we use oldest_start_ts and oldest_start_txn only in fast truncate operation. We found the issue with this in WT-6494. We need to investigate a solution about repurposing these.
We need to consider the impact of this repurpose for upgrade and downgrade. The scope of this ticket is:
1. To make code changes and have a PR.
2. Run a MongoDB patch build and WT stress testing build to understand the fallout.
3. Analysis of the impact for upgrade and downgrade.
- duplicates
-
WT-6708 Repurpose oldest start txn to be newest txn in the aggregated time window
-
- Closed
-