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

Memory leak issues when closing with PANIC set

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Won't Do
    • None
    • None
    • None
    • None
    • 3
    • Storage - Ra 2020-09-21

    Description

      During recovery, if the history store file doesn't exist treat as a recovery failure and it treats as a PANIC error. Due to the PANIC error, during connection close, the memory that is allocated for pages in the cache are leaked.

      Instead of treating the history store file doesn't exist as a recovery error, just verify the history store file before the recovery starts would be good to fix the memory leak.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-storage-engines Backlog - Storage Engines Team
              haribabu.kommi@mongodb.com Haribabu Kommi
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: