-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Developer Tools
-
3
We currently aren't setting maxTimeMS anywhere in our extension. We should, by default, include a maxTimeMS in the options for all of our operations that could potentially take a long time. This ticket involves adding a maxTimeMS for every find/aggregate/count/sample in our code.
For now lets make them 10_000 ms (10 seconds).
This isn't for playgrounds, as users can cancel those long running requests themselves.
We may want to add a setting, like Compass does, but that is not for this ticket, mentioning for discussion in triage. When implementing this lets have the default maxTimeMS retrieval in one place so if we do want a setting it's more straight forward.