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

Tighten $currentOp and pinned cursor checks in kill_pinned_cursor.js

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.0-rc8, 4.4.0-rc9, 4.7.0, 4.2.11
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • ALL
    • v4.4, v4.2
    • 17

      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.

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

              Created:
              Updated:
              Resolved: