[DOCS-11445] Docs for SERVER-19410: Implement maxTimeMS operation timeouts on new query path in mongos Created: 13/Mar/18 Updated: 29/Oct/23 Resolved: 21/Jun/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.3, 3.7.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kay Kim (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 5 years, 34 weeks, 2 days ago | ||||||||
| Epic Link: | DOCS: 4.0 Server | ||||||||
| Description |
Documentation Request Summary:The line in this page is a little misleading: https://docs.mongodb.com/manual/reference/method/cursor.maxTimeMS/#behaviors It's true that it will not count the latency between the client and the server, but it will include the latency between mongos and mongod. Scope of changes:
(other mentions of maxTimeMS doesn't get into specifics regarding latency, just that operations must finish execution within maxTimeMS). Impact to other docs outside of this product:MVP:Resources: |
| Comments |
| Comment by Githook User [ 18/Jun/18 ] |
|
Author: {'username': 'kay-kim', 'name': 'kay', 'email': 'kay.kim@10gen.com'}Message: |