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

Verify that killing a pinned cursor only decrements the 'open pinned' counter once

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Querying
    • Labels:
      None
    • Query
    • ALL
    • Hide

      This can sometimes be caught by running the following, but it doesn't happen every time.

      python buildscripts/resmoke.py --executor=no_passthrough_with_mongod jstests/noPassthroughWithMongod/index_hammer1.js jstests/noPassthroughWithMongod/cursor_server_status_metrics.js
      Show
      This can sometimes be caught by running the following, but it doesn't happen every time. python buildscripts/resmoke.py --executor=no_passthrough_with_mongod jstests/noPassthroughWithMongod/index_hammer1.js jstests/noPassthroughWithMongod/cursor_server_status_metrics.js

      The bug reported in the original description was fixed as part of cc954e9e1d88b30d1ab89ee3bbbd9db0bb15263d, since the rest of that patch appeared to make this more common (happened twice in patch builds). The remaining work for this ticket is to ensure we have test coverage for this case.

      Original Description

      In this cleanup path, we will decrement dCursorStatsOpenPinned twice, once on line 252, and then again on line 231

            Assignee:
            backlog-server-query Backlog - Query Team (Inactive)
            Reporter:
            charlie.swanson@mongodb.com Charlie Swanson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: