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

Consider how much memory is consumed by log buffers

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • WT2.7.0
    • None
    • None

    Description

      Each log slot has a buffer associated with it. That buffer is grown dynamically until it is large enough to hold the consolidated records.

      We recently bumped the number of slots, which may alter how much memory log buffers consume.

      We should consider limiting how much memory the log system can use (maybe a log cache size?). Or alternatively limiting the size log buffers can grow to - there is almost certainly a limit to how much memory it makes sense to copy and consolidate into a buffer rather than just writing it directly.

      Attachments

        Issue Links

          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-19673 Excessive memory allocated by WiredTiger journal

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-19282 WiredTiger changes in MongoDB 3.1.6

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-19532 WiredTiger changes for MongoDB 3.1.7

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

          Activity

            People

              sue.loverso@mongodb.com Susan LoVerso
              alexander.gorrod@mongodb.com Alexander Gorrod
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: