[SERVER-12764] Using maxTimeMS & Javascript can lead to different errors from the server Created: 18/Feb/14 Updated: 10/Dec/14 Resolved: 23/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript, Write Ops |
| Affects Version/s: | 2.5.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Ross Lawley | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | 26qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||
| Operating System: | ALL | ||||||||||||||
| Steps To Reproduce: | In the shell:
|
||||||||||||||
| Participants: | |||||||||||||||
| Description |
|
Using maxTimeMS with $where returns:
expected
|
| Comments |
| Comment by J Rassi [ 23/Feb/14 ] | |
|
Resolving as dup of | |
| Comment by Ross Lawley [ 19/Feb/14 ] | |
|
Also, happens when doing a map reduce, that exceeds maxTimeMS
|