[SERVER-13332] scary mongos messaging in rc2 related to unsharded cursors Created: 24/Mar/14  Updated: 11/Jul/16  Resolved: 25/Mar/14

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 2.6.0-rc3

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Greg Studer
Resolution: Done Votes: 0
Labels: Sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

In 2.6, we directly check both the sharded and unsharded cursor cache for cursor ids - only one of these can succeed. However we message OCCASIONALLY with:

Sharded CursorCache missing cursor id: 2354118951366269003

which is misleading, since generally this just means the cursor is unsharded.

Also we rely on a noisy and inefficient function to determine if the getMore'd collection is sharded, which can be replaced.



 Comments   
Comment by Githook User [ 25/Mar/14 ]

Author:

{u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-13332 fix scary messaging around unsharded cursors
(cherry picked from commit e0867ea625ccca214dd6fbf079001a6b097c0ef2)
Branch: v2.6
https://github.com/mongodb/mongo/commit/2c324c51b079af4df7256df9fdfd313d355d2e8d

Comment by Githook User [ 25/Mar/14 ]

Author:

{u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-13332 fix scary messaging around unsharded cursors
Branch: master
https://github.com/mongodb/mongo/commit/e0867ea625ccca214dd6fbf079001a6b097c0ef2

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