[SERVER-11488] Supported mongos commands should propagate maxTimeMS option to shards Created: 30/Oct/13  Updated: 10/Dec/14  Resolved: 04/Nov/13

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 2.5.3
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Unassigned
Resolution: Done Votes: 0
Labels: 26qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-2212 Server automatically abort queries/co... Closed
Operating System: ALL
Participants:

 Description   

In sharded cluster, mongos commands supported by maxTimeMS should propagate the maxTimeMS option to shards. However, the following commands don't satisfy this contract.

  1. fsync
  2. movePrimary. Before the metadata on config server is changed by movePrimary, it is interruptible.


 Comments   
Comment by J Rassi [ 04/Nov/13 ]

Per greg_10gen: fsync and movePrimary should swallow maxTimeMS in mongos. Resolving as 'works as designed'.

Generated at Thu Feb 08 03:25:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.