[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: |
|
||||||||
| 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.
|
| Comments |
| Comment by J Rassi [ 04/Nov/13 ] |
|
Per greg_10gen: fsync and movePrimary should swallow maxTimeMS in mongos. Resolving as 'works as designed'. |