[SERVER-17298] listCollections accepts but does not enforce the maxTimeMS option. Created: 16/Feb/15 Updated: 15/Jun/18 Resolved: 15/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 3.0.0-rc8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Robert Moore | Assignee: | Ben Judd |
| Resolution: | Done | Votes: | 1 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
|||||||
| Operating System: | ALL | |||||||
| Steps To Reproduce: | From the Shell using 3.0.0-rc8
|
|||||||
| Sprint: | Storage NYC 2018-06-18 | |||||||
| Participants: |
| Description |
|
The listCollections command accepts the maxTimeMS option but does not enforce the timeout. This is a regression from the 2.6.X model which performed a query on the system.namespaces collection which does enforce the timeout. Note that the server does imply that the command supports the maxTimeMS with the following error message:
|