[SERVER-20537] Re-enable tests disabled when OP_QUERY legacy ops in mongos are made to use new find command path Created: 21/Sep/15  Updated: 07/Oct/15  Resolved: 30/Sep/15

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

Type: Bug Priority: Major - P3
Reporter: J Rassi Assignee: J Rassi
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: QuInt A (10/12/15)
Participants:

 Description   

This is a placeholder ticket to re-enable any tests disabled (and fix any bugs discovered) as part of enabling the new find command path in mongos for OP_QUERY legacy user queries.



 Comments   
Comment by Githook User [ 24/Sep/15 ]

Author:

{u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}

Message: SERVER-20537 fix leak of remote cursor in AsyncResultsMerger

If ARM::kill() was called before the find command response was received, the callback for the
outstanding find command would be cancelled. As a result, the cursor id in need of a kill was never
received, and the cursor was left alive.
Branch: master
https://github.com/mongodb/mongo/commit/1a8711db875fc1b0e855c838dc0241c381a19dbc

Generated at Thu Feb 08 03:54:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.