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

Avoid performing history store cleanup for modified trees

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT3.2.2, 4.4.0-rc0
    • Component/s: None
    • Labels:
      None
    • Story Points:
      3
    • Sprint:
      Storage Engines 2020-04-06

      Description

      Rollback to stable cleans the history store even for the tables that are timestamp and immediately durable in scenarios when those tables are never checkpointed. As in those scenarios, the durable timestamp that is zero, so it treats as a non-timestamped table and performs the history store cleanup that can lead to data loss.

       

      The solution to this problem is to avoid cleaning the history store when the tree is modified.

        Attachments

          Activity

            People

            • Assignee:
              haribabu.kommi Haribabu Kommi
              Reporter:
              haribabu.kommi Haribabu Kommi
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: