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

Tighten $currentOp and pinned cursor checks in kill_pinned_cursor.js

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.4.0-rc8, 4.4.0-rc9, 4.7.0, 4.2.11
    • None
    • None
    • Fully Compatible
    • ALL
    • v4.4, v4.2
    • 17

    Description

      The test is assuming a find command is hitting a fail point for a pinned cursor by looking at the total open 'pinned' count in serverStatus. However, its possible that other background threads (e.g. PeriodicShardedIndexConsistencyChecker) hit the fail point and not the find command that the test is expecting. Instead of using serverStatus, the test should run a $currentOp and filter the output based on the 'failpointMsg' and the 'comment' string.

      Attachments

        Issue Links

          Activity

            People

              nicholas.zolnierz@mongodb.com Nicholas Zolnierz
              nicholas.zolnierz@mongodb.com Nicholas Zolnierz
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: