[SERVER-5624] mongos does not respect notimeout for cursors Created: 16/Apr/12  Updated: 11/Jul/16  Resolved: 22/May/12

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.1.0
Fix Version/s: 2.1.2

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: mongos
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

CursorCache::doTimeouts does not perform any checks on whether a notimeout option was set to the cursor.



 Comments   
Comment by auto [ 22/May/12 ]

Author:

{u'login': u'', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}

Message: SERVER-5624 Wrote tests for cursor timetouts
Branch: master
https://github.com/mongodb/mongo/commit/65303070c9c302793515085681d6b2daceedac69

Comment by Randolph Tan [ 22/May/12 ]

After investigating further, I realized that mongos does actually handle notimeout properly. It just does it differently from mongod.

Comment by Scott Hernandez (Inactive) [ 28/Apr/12 ]

This is for sharded cursors (given to the client) and not the cursors to the shards.

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