[COMPASS-3753] Customizable maxTimeMS Created: 03/Jul/19 Updated: 10/Jan/24 Resolved: 01/Aug/19 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Aggregation pipeline |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Grégory NEUT | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 16.04 LTS |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Documentation Changes: | Needed | ||||||||
| Documentation Changes Summary: | Explain how to change the maxTimeMS setting |
||||||||
| Description |
|
I have a collection filled with 11 million documents and I want to make an aggregation. The aggregation fail due to a timeout.
It should be cool to be able to change the maxTimeMS in a configuration file or directly in the aggregation pipe page.
Also the timeout is quite low by default.
There is a stackoverflow post about this "issue" : https://stackoverflow.com/questions/55510424/mongodb-compass-timeouts
To contact me : gregory.neut@gmail.com |
| Comments |
| Comment by Wibbu Technology [ 19/Jul/19 ] |
|
I have the same issue that has been plaguing me for a couple days now. Would love to see a resolution.
Thanks |