[SERVER-11705] tailable cursors cursor not found after 10 minutes Created: 14/Nov/13  Updated: 10/Dec/14  Resolved: 19/Dec/13

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 2.5.3
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Thomas Boyd Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-12200 tailable cursor goes invalid after 10... Closed
Operating System: ALL
Participants:

 Description   

This might be by design for 2.5.x and 2.6.x, but I do not see it in current release notes for 2.5.3, so at least that documentation needs to get addressed.

Our 2.5.3 tester reports:

Version 2.4.6 does not close tailable cursors after a timeout period. This is why we’ve been able to leave the app up and running for days/weeks with a cursor blocked waiting for events. I verified this today on my Windows instance and on a linux instance.

Version 2.5.3 closes tailable cursors after 10 minutes. The client throws an exception MongoException.CursorNotFound. I have modified our code to rebuild the cursor if this occurs.



 Comments   
Comment by Matt Dannenberg [ 17/Dec/13 ]

This is expected behavior. The ten minute timeout also exists in 2.4. Here's the check for timeout code in 2.4:
https://github.com/mongodb/mongo/blob/v2.4/src/mongo/db/clientcursor.cpp#L159

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