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

Make awaitData cursors block rather than busy wait in the OP_GET_MORE path

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.1.6
    • Querying
    • None
    • Fully Compatible
    • Quint Iteration 5, Quint Iteration 6
    • 0

    Description

      In the getMore command path, threads servicing awaitData cursors will always block rather than busy wait. For OP_GET_MORE, however, the thread will block if it is tailing the oplog but for any other capped collection it will busy wait.

      We can use the per-capped collection condition variable added under SERVER-18184 to remove busy waiting from the OP_GET_MORE path.

      Attachments

        Issue Links

          depends on

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-19099 Switch stdx::polyfills for concurrency and time to use std components

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Task - A task that needs to be done. SERVER-18184 Add awaitData support to getMore command

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-19947 Deadlock between aggregations with sorts on sharded collections and operations requiring MODE_X database locks

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

          Activity

            People

              qingyang.chen Qingyang Chen
              david.storch@mongodb.com David Storch
              Votes:
              3 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: