[SERVER-72798] Only auto-cleanup cursors that have been killed Created: 12/Jan/23  Updated: 29/Oct/23  Resolved: 18/Jan/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0-rc0

Type: Bug Priority: Major - P3
Reporter: Alyssa Clark Assignee: Alyssa Clark
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
is caused by SERVER-67722 Shard cursor is not killed on MaxTime... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 29

 Description   

See discussion on BF-27364 for more details:

Instead of doing the auto-kill upon unpinning when 
cursor->cameFromRouter() && interruptStatus == ErrorCodes::MaxTimeMSExpired, could we set a flag on the cursor indicating that it has been killed in killCursor and check that to determine whether we should destruct it immediately in unpin?

 



 Comments   
Comment by Romans Kasperovics [ 25/Jan/23 ]

Backported (squashed) to v6.2 in BACKPORT-14444
PR: https://github.com/10gen/mongo/pull/10027
Commit: https://github.com/mongodb/mongo/commit/f293955ab3c651cf79217fcf3e9c5fbd4b2ce541

Backported (squashed) to v6.0 in BACKPORT-14445
PR: https://github.com/10gen/mongo/pull/10029
Commit: https://github.com/mongodb/mongo/commit/7f5b43a5f8900ef0e29d762818a07290fa99c98d

Comment by Githook User [ 17/Jan/23 ]

Author:

{'name': 'Alyssa Wagenmaker', 'email': 'alyssa.wagenmaker@mongodb.com', 'username': 'awagenmaker'}

Message: SERVER-72798 Only auto-cleanup cursors that have been killed
Branch: master
https://github.com/mongodb/mongo/commit/a2ed6a38da7904550463882bc68591440bf5a697

Generated at Thu Feb 08 06:22:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.