[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: |
|
||||
| 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: |