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

exhaust_cursor_currentop_integration_test should not drop getMore()'s read lock

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.1.11
    • Storage
    • None
    • Fully Compatible
    • ALL
    • Storage NYC 2019-05-06
    • 21

    Description

      For SERVER-40547, when test commands are enabled, we crash if nextNotIncreasing instead of throwing a WriteConflictException.

      With the work done in SERVER-40547, it uncovered a violation in the integration_tests_standalone_audit suite for the exhaust_cursor_currentop_integration_test test with the following message:

      WTCursor::next -- c->next_key ( RecordId(1)) was not greater than _lastReturnedId (RecordId(2)) which is a bug.
      

      Evergreen patch with SERVER-40547 changes.

      resmoke.py invocation for local usage:

      buildscripts/resmoke.py --suites=integration_tests_standalone_audit
      

      Attachments

        Issue Links

          Activity

            People

              gregory.wlodarek@mongodb.com Gregory Wlodarek
              gregory.wlodarek@mongodb.com Gregory Wlodarek
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: