[DOCS-13011] noCursorTimeout can actually expire Created: 05/Sep/19  Updated: 30/Oct/23  Resolved: 05/Sep/19

Status: Closed
Project: Documentation
Component/s: Server, sessions
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Bug Priority: Major - P3
Reporter: Josef Ahmad Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates DOCS-11255 Document that 3.6 implicit sessions m... Closed
Related
Participants:
Days since reply: 4 years, 22 weeks, 6 days ago

 Description   

Description

https://docs.mongodb.com/manual/reference/method/cursor.noCursorTimeout/ reads:

Instructs the server to avoid closing a cursor automatically after a period of inactivity.

A noTimeout server can be reaped if the logical session it's associated to times out because of inactivity (default 30 minutes). From an application perspective, this effectively makes the cursor time out.

We should document this behaviour as it has been source of confusion.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Ravind Kumar (Inactive) [ 05/Sep/19 ]

This actually duplicates DOCS-11255. I'll add this area of fixup to the work tbd on that ticket and prioritize for this week.

Generated at Thu Feb 08 08:06:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.