Investigate repurposing of oldest_start_ts as newest_start_ts and oldest_start_txn as newest_start_txn in aggregated timewindow.

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage - Ra 2020-10-05
    • 0

      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.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Vamsi Boyapati
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: