[DOCS-15181] [SERVER] Clarify that noCursorTimeout has no effect for MongoDB 4.4.8+ Created: 20/Mar/22  Updated: 22/Jan/24

Status: Backlog
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 5.0.0, 4.4.8, 5.2.0, 5.3.0

Type: Task Priority: Minor - P4
Reporter: Jeremy Mikola Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: backlog, request
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-6036 Disable cursor timeout for cursors th... Closed
Participants:
Days since reply: 1 year, 46 weeks, 4 days ago
Epic Link: DOCSP-11702

 Description   

In mongodb/mongo-php-driver#1308, a user had some questions about cursor timeouts. I was reminded of SERVER-6036, which suggests that singe MongoDB 4.4.8 any cursor associated with a session will have the noCursorTimeout option automatically applied to it.

Since drivers will attach logical session IDs to all outgoing commands (there may be edge cases, but certainly all commands that yield a cursor), this suggests that cursors will only be subject to timing out due to the session's idle timeout (default: 30 minutes). The original 10 minute timeout (related to noCursorTimeout) will never come into play.

I assume this is related to find's noCursorTimeout option being omitted from stable API v1; however, this isn't explicitly stated in the documentation and users may be led to believe that noCursorTimeout actually has some effect on MongoDB 4.4.8+.

I'm opening this ticket to suggest we clearly state the implications of SERVER-6036 in the documentation if it's not already discussed. AFAIK, only the find command supported a noCursorTimeout option, so this misunderstanding may not apply to other cursor-yielding commands like aggregate.


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