Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-6547

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

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 4.5 Required
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Attachments

          Issue Links

          is related to

          Task - A task that needs to be done. WT-6548 Investigate fast truncate solution with new aggregate time information only in in-memory structures.

          • Major - P3 - Major loss of function.
          • Open

            Activity

              People

              Assignee:
              backlog-server-storage-engines Backlog - Storage Engines Team
              Reporter:
              vamsi.krishna Vamsi Boyapati
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: