[SERVER-12636] 'text' command not honoring maxTimeMS Created: 06/Feb/14 Updated: 10/Dec/14 Resolved: 26/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | 2.5.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Robert Moore | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux XXX 3.12.8-300.fc20.x86_64 #1 SMP Thu Jan 16 01:07:50 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ ./mongod --version |
||
| Operating System: | Linux |
| Steps To Reproduce: | See description. |
| Participants: |
| Description |
|
This is a fork from ticket The 'text' command is not aborting the command when provided a maxTimeMS.
In the server log we get confirmation that the command took longer than 100ms.
The above text command was modified from http://docs.mongodb.org/manual/reference/command/text/. I also tried the manual command invocation with the same results:
|
| Comments |
| Comment by Daniel Pasette (Inactive) [ 26/Feb/14 ] |
|
Thanks again for the report Robert. Agreed that this does not need to be fixed for 2.6.0. |
| Comment by Robert Moore [ 26/Feb/14 ] |
|
Given that the 'text' command is deprecated in 2.6 I think this ticket can just be closed. |