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

Better bufbuilder size limit strategy for mmap journal

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • MMAPv1, Storage
    • None
    • Storage Execution

    Description

      Instead of crashing when the bufbuilder size reaches some hardcoded max-size, we can make it configurable (and call it "journal cache size"), and do a stop-the-world (pause all writes to it) if the max-size is reached.

      This strategy is better than what we have right now, as it allows the user to make a choice based on his concurrency requirements, in a somewhat similar fashion he can configure the cache size in WT.

      In the event of reaching max-size, the user won't see his server crashing but will experience a short performance degradation, which is better in most cases.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            alex.komyagin@mongodb.com Alexander Komyagin
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: