-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 4.0.24, 4.2.14, 4.4.6, 5.0.0-rc0
-
Component/s: None
-
Fully Compatible
-
QE 2021-08-09, QE 2021-08-23, QE 2021-09-06, QE 2021-09-20, QE 2021-10-04, QE 2021-10-18, QE 2021-11-01, QE 2021-11-15, QE 2021-11-29, QE 2021-12-13, QE 2021-12-27, QE 2022-01-10, QE 2022-02-07, QE 2022-01-24
-
(copied to CRM)
-
154
For all MongoDB versions:
Scenario
- Multi-shard query with maxTimeMS and allowPartialResults targeting shards A and B
- Mongos is holding in-memory preliminary results from shard A
- maxTimeMS is reached before getting results from shard B
- The mongos throws a maxTimeMS error instead of returning partial results.
Question
Should the shard return partial results?
- causes
-
SERVER-71241 allow_partial_results_with_maxTimeMS.js getMores are too slow
- Closed
-
SERVER-71372 getMore fails to return partial results from find on sharded cluster
- Closed
-
SERVER-71440 Remove OpCtx::setIgnoreInterruptsExceptForReplStateChange
- Closed