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

                if ( warn )
                    OCCASIONALLY out() << "ClientCursor::find(): cursor not found in map " << id << " (ok after a drop)\n";



 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: SERVER-6931 Don't attempt to look up a cursor using an invalid id. Prevents an occasional incorrect warning message.
Branch: v2.2
https://github.com/mongodb/mongo/commit/a530383eb222586fd84d3e3d7f5f986dc7ed892e

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: SERVER-6931 Don't attempt to look up a cursor using an invalid id. Prevents an occasional incorrect warning message.
Branch: master
https://github.com/mongodb/mongo/commit/b6a1e54b56dff1ee4cf3e7e56ec1ae38dd77aa21

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