-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 6.2.0-rc0
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
-
QE 2022-11-14
-
43
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.
- is caused by
-
SERVER-57469 Return partial results from subset of shards when `maxTimeMS` and `allowPartialResults` are set
- Closed
- related to
-
SERVER-71248 Adapt to changed batchSize in getMore
- Closed