[SERVER-28781] Verify that killing a pinned cursor only decrements the 'open pinned' counter once Created: 12/Apr/17  Updated: 06/Dec/22  Resolved: 17/Apr/17

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Charlie Swanson Assignee: Backlog - Query Team (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query
Operating System: ALL
Steps To Reproduce:

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

Participants:

 Description   

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


Generated at Thu Feb 08 04:19:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.