[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:
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: |
| Comment by Githook User [ 25/Mar/14 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: |