Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-43906

WiredTigerLAS.wt keeps growing daily

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.2.0
    • Component/s: None
    • None
    • Fully Compatible
    • ALL

      I am running MongoDB 4.2.0 on Ubuntu 18.04.3 LTS, single server, no replicas. This is hosted in AWS on a m4.4xlarge instance type (16 cores, 64GB RAM) with 2.5TB volume (type io1, 8000 IOPS). The CloudWatch metrics look completely normal. CPU usage seems to be between 20-25%.

      After upgrading to 4.2.0 I started observing abnormal growth of WiredTigerLAS.wt. The only way to reclaim disk space is to restart the service. This needs to happen every day or two. In just under two days it has grown to 270GB. This can hardly be considered normal.

      I am willing to share diagnostics data to get to the bottom of this.

      I have found a similar issue but it does not seem to apply. Also, I do not see a resolution in the existing issue.

        1. hot_pages.png
          hot_pages.png
          324 kB
        2. LAS_remove.png
          LAS_remove.png
          242 kB
        3. writeConflicts.png
          writeConflicts.png
          239 kB
        4. table_create_drop.png
          table_create_drop.png
          331 kB
        5. nov15.png
          nov15.png
          316 kB
        6. uptime.png
          uptime.png
          74 kB
        7. LAS_removed.png
          LAS_removed.png
          72 kB
        8. SERVER-43906.png
          SERVER-43906.png
          92 kB

            Assignee:
            dmitry.agranat@mongodb.com Dmitry Agranat
            Reporter:
            aleksandarpuskas@gmail.com Aleksandar Puskas
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: