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

Investigate fast truncate solution with new aggregate time information only in in-memory structures.

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Gone away
    • None
    • None
    • None
    • None
    • 8

    Description

      Present Aggregate time-window doesn't seem to be enough to support fast truncate. Investigate maintaining the extra time window information required only as part of in-memory structures so that there will not be an issue with upgrade or downgrade.

      We need newest_start_ts and newest_start_txn in aggregated time windows to support fast truncate option.

      Attachments

        Issue Links

          depends on

          New Feature - A new feature of the product, which has yet to be developed. WT-6708 Repurpose oldest start txn to be newest txn in the aggregated time window

          • Major - P3 - Major loss of function.
          • Closed
          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. WT-6494 __wt_time_value_validate failed because start transaction id is larger than stop transaction id

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed
          related to

          Task - A task that needs to be done. WT-6547 Investigate repurposing of oldest_start_ts as newest_start_ts and oldest_start_txn as newest_start_txn in aggregated timewindow.

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

          Activity

            People

              backlog-server-storage-engines Backlog - Storage Engines Team
              vamsi.krishna@mongodb.com Vamsi Boyapati
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: