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

ReplBatcher has a long-running OperationContext

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.2.18, 3.4.11, 3.6.0-rc1
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2017-10-23

    Description

      The ReplBatcher has been identified as an actor that keeps a long-running OperationContext. This can cause problems such as WT table drops to fail until the OperationContext is destroyed.

      https://github.com/mongodb/mongo/blob/8210549ab754524b155ea45eb6675d717873cb21/src/mongo/db/repl/sync_tail.cpp#L753

      Attachments

        Issue Links

          is related to

          New Feature - A new feature of the product, which has yet to be developed. SERVER-22766 Dynamic oplog sizing for WiredTiger nodes

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-31654 ReplBatcher should recalculate batch limits after oplog is resized via replSetResizeOplog

          • Major - P3 - Major loss of function.
          • Backlog
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31101 WT table not dropped after collection is dropped due to long-running OperationContext

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

          Activity

            People

              benety.goh@mongodb.com Benety Goh
              daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: