[COMPASS-4254] maxTimeMs is ignored in explain tab Created: 20/Apr/20 Updated: 20/Feb/23 Resolved: 22/Apr/20 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Compass, Explain |
| Affects Version/s: | None |
| Fix Version/s: | No version |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Maurizio Casimirri | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| UserVoice Links: | Disable the explain button while an explain is running (Suggestion) |
| Sprint: | Iteration Cantaloupe |
| Description |
|
the maxTimeMs option seems to be ignored in the explain tab. NOTE: that may be by intentional. It seems that maxTimeMs is also ignored by cursor.explain in node.js. I tried await coll.find().maxTimeMs(1).skip(2700).limit(5000).batchSize(1).explain() and it just returns, whereas toArray fails with a timeout. To reproduce: Set maxTimeMs to 1 ms and run an explain for a non-indexed query on a big collection. Even if few stages would report an execution time that is bigger than the maxTimeMs no error is raised and the operation returns normally. |
| Comments |
| Comment by Massimiliano Marcon [ 22/Apr/20 ] |
|
The driver does not take a maxTimeMS argument for an explain operation. |