Details
-
Task
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
-
None
-
Query
-
Fully Compatible
Description
The create command should not accept the maxTimeMS option, because we do not check for interrupt within its execution. However, create could not reject maxTimeMS in 3.4, because a 3.2 mongos attaches a maxTimeMS when creating the changelog and actionlog collections on the config servers. In 3.6, we should be able to disallow maxTimeMS for create.
Attachments
Issue Links
- is related to
-
SERVER-26450 Whitelist maxTimeMS option to create command
-
- Closed
-