[DOCS-10125] Improve getMore `maxTimeMS` description Created: 14/Apr/17  Updated: 30/Oct/23  Resolved: 18/Jul/23

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

Type: Task Priority: Major - P3
Reporter: Matt Broadstone Assignee: Cory Bullinger
Resolution: Done Votes: 0
Labels: quick-win, reopened, server-docs-bug-bash, triage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 1 year, 14 weeks ago

 Description   

https://docs.mongodb.com/manual/reference/command/getMore/

The documentation specifies: "If you do not specify a value for maxTimeMS, operations will not time out. A value of 0 explicitly specifies the default unbounded behavior."

It would appear that this is not the case for some cursor types. For instance, a tailable + awaitData cursor on a capped collection (oplog), will default `maxTimeMS` to 1 if the user omits the key. I'm not sure about other special cases, but it seems like we can at least document this one? Here is the ticket related to that detail: SERVER-19665



 Comments   
Comment by Sarah Olson [ 02/Nov/22 ]

Thanks milkie@mongodb.com! Appreciate the feedback. 

Comment by Eric Milkie [ 31/Oct/22 ]

Please fix this.

Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Comment by Matt Broadstone [ 14/Apr/17 ]

It looks like documentation for this was corrected elsewhere: DOCS-6620

Generated at Thu Feb 08 07:59:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.