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

profile_getmore.js does not tolerate killCursors command

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.4.10, 3.6.0-rc0
    • Component/s: Querying
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.4
    • Sprint:
      Query 2017-10-23
    • Linked BF Score:
      0

      Description

      The profile_getmore.js test creates a cursor and assigns its client-side DBQuery representation to a variable called cursor:

      https://github.com/mongodb/mongo/blob/f64d3147b938c9dcbd24ff127d5506a029902549/jstests/core/profile_getmore.js#L64

      It then leaves this cursor open on the server, while the client assigns a second DBQuery object to the cursor variable:

      https://github.com/mongodb/mongo/blob/f64d3147b938c9dcbd24ff127d5506a029902549/jstests/core/profile_getmore.js#L81

      The abandoned cursor, however, may now be garbage collected by the shell at any time. When a DBQuery is garbage collected, it issues a killCursors command to the server in order to clean up any server-side state. Therefore, after line 81, a killCursors command may at any arbitrary point during the test's execution be issued against the database under test. The test's assertions are not prepared to handle such a command appearing in the system.profile entry. We must fix the test to either

      1. tolerate the possibility of a killCursors command, or
      2. be careful to close the cursor before abandoning it.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: