[SERVER-6931] warning message occasionally logged incorrectly when a client cursor is exhausted Created: 04/Sep/12 Updated: 11/Jul/16 Resolved: 06/Sep/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | 2.2.1, 2.3.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Aaron Staple |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
If a ClientCursor::Pin is released and then destroyed, a "cursor not found in map" warning can occasionally be printed incorrectly. This happens when a client cursor is exhausted in process get more.
|
| Comments |
| Comment by auto [ 12/Sep/12 ] |
|
Author: {u'date': u'2012-09-04T12:20:45-07:00', u'email': u'aaron@10gen.com', u'name': u'Aaron'}Message: |
| Comment by auto [ 06/Sep/12 ] |
|
Author: {u'date': u'2012-09-04T12:20:45-07:00', u'email': u'aaron@10gen.com', u'name': u'Aaron'}Message: |