-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.5.3
-
Component/s: None
-
ALL
In sharded cluster, mongos commands supported by maxTimeMS should propagate the maxTimeMS option to shards. However, the following commands don't satisfy this contract.
- fsync
- movePrimary. Before the metadata on config server is changed by movePrimary, it is interruptible.
- related to
-
SERVER-2212 Server automatically abort queries/commands after user-specified time limit
- Closed