[SERVER-71241] allow_partial_results_with_maxTimeMS.js getMores are too slow Created: 10/Nov/22 Updated: 29/Oct/23 Resolved: 11/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 6.2.0-rc0 |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Steve Tarzia | Assignee: | Steve Tarzia |
| Resolution: | Fixed | 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 | ||||||||||||||||||||
| Steps To Reproduce: | |||||||||||||||||||||
| Sprint: | QE 2022-11-14 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 43 | ||||||||||||||||||||
| Description |
|
As seen in BF-26772, the getMore command in allow_partial_results_with_maxTimeMS.js:191 is taking very long to execute, causing a timeout instead of returning the partial results we expect to see. This is because the initial find uses a tiny batch size of 1. The subsequent getMore sets a much larger batch size, but the cursor retains its original batch size of 1, requiring the router to make hundreds of getMore requests to the remotes. This behavior is actually quite confusing and I'll create another ticket to consider changing it. However, the quick solution to this js test failure is to use a larger batch size in the initial find. |
| Comments |
| Comment by Githook User [ 11/Nov/22 ] |
|
Author: {'name': 'Steve Tarzia', 'email': 'steve.tarzia@mongodb.com', 'username': 'starzia'}Message: |