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

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.4.0-rc8, 4.4.0-rc9, 4.7.0, 4.2.11
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4, v4.2
    • Linked BF Score:
      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

              Assignee:
              nicholas.zolnierz Nicholas Zolnierz
              Reporter:
              nicholas.zolnierz Nicholas Zolnierz
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: