[SERVER-19737] Add ClusterCursorManager shutdown logic to mongos shutdown sequence Created: 03/Aug/15  Updated: 19/Sep/15  Resolved: 25/Aug/15

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

Type: Improvement 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

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: QuInt 8 08/28/15
Participants:
Linked BF Score: 0

 Description   

As a part of mongos shutdown, all open cursors should be killed.

Explicit logic may need to be added to prevent new cursors from being registered, and for owners of pinned cursors to kill and return their cursors.



 Comments   
Comment by Githook User [ 25/Aug/15 ]

Author:

{u'username': u'jrassi', u'name': u'Jason Rassi', u'email': u'rassi@10gen.com'}

Message: SERVER-19737 Kill all open cursors during mongos shutdown
Branch: master
https://github.com/mongodb/mongo/commit/546066e9df30a2b6e1a6bfeff208d4b3c0510eb6

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