[DOCS-11131] Recommend setting maxTimeMS and document timeout behavior for mongos Created: 14/Dec/17  Updated: 30/Oct/23

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

Type: Improvement Priority: Major - P3
Reporter: Justin LaBreck Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

We had a lengthy discussion with engineering about the behavior of mongos on timeout. It appears that the mongos and drivers rely heavily on the maxTimeMS cursor and connection level setting. Drivers do not monitor this and rely on the server/mongos to terminate connections on erratic server behavior.

This should be documented because developers should care (or at least think) about timeout failure situations. Additionally, we should recommend setting the maxTimeMS setting at the driver level when using sharded clusters.

Details here:
https://jira.mongodb.org/browse/HELP-5417



 Comments   
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!

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