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

Investigate why history store file size is not decreased after time window has decreased

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Storage Engines
    • StorEng - Defined Pipeline

      In a help ticket, I observed there was a dramatic increase of the history store file size with the increase of the history window. That is expected. However, after we decrease the history window, the size of the history store file didn't decrease correspondingly.

      Whether we could decrease the file size of a WiredTiger file depends on if there were contents still needed at the end of the file. Therefore, we often need to compact the file to free the available spaces in the file. In the case of history store file, I would imagine the most content should be obsolete after we have decreased the history store window and it is unlikely we cannot decrease the file size.

      We need to understand why this can happen.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            chenhao.qu@mongodb.com Chenhao Qu
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: