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

Investigate throttling large write operations that create majority commit lag

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Execution Team 2022-05-30, Execution Team 2022-06-13, Execution Team 2022-06-27

    Description

      For large write operations that generate many oplog entires, say, a large multi-delete, investigate strategies to prevent secondaries from falling too far behind.

      Flow control doesn't sufficiently account for this because it throttles operations globally, and only after lag has reached 5 seconds.

      The idea here is to force operations that have written large amounts of data to periodically wait for their writes to majority-replicate before writing any more. In this way, we don't penalize smaller write operations, and only make problematic operations back off.

      Attachments

        Activity

          People

            josef.ahmad@mongodb.com Josef Ahmad
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: