[SERVER-13411] parallelCollectionScan does not provide a time limit option (maxTimeMS). Created: 31/Mar/14 Updated: 22/Mar/17 Resolved: 04/Feb/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 2.6.0-rc2 |
| Fix Version/s: | 3.3.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Robert Moore | Assignee: | Tess Avitabile (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | Query 10 (02/22/16) | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Testing with the new parallelCollectionScan command and it looks like this command does not support the ability to limit the execution time of the operation. I had expected it to work like the normal query operation were the cursor has a time limit associated with it that once exhausted causes a failure back to the client. Is there a reason this functionality was left out? I think all that would be needed would be to call setLeftoverMaxTimeMicros() based on a maxTimeMS within the command on the ClientCursor created on line 238 of parallel_collection_scan.cpp. https://github.com/mongodb/mongo/blob/master/src/mongo/db/commands/parallel_collection_scan.cpp#L238 |
| Comments |
| Comment by Tess Avitabile (Inactive) [ 04/Feb/16 ] |
|
The parallelCollectionScan command now takes the field maxTimeMS, which will be applied to each of the cursors it returns. |
| Comment by Githook User [ 04/Feb/16 ] |
|
Author: {u'username': u'tessavitabile', u'name': u'Tess Avitabile', u'email': u'tess.avitabile@mongodb.com'}Message: |