Details
-
Improvement
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
None
-
Fully Compatible
-
v4.0, v3.6
-
Query 2018-07-02
-
26
Description
The test issues a getMore with a maxTimeMS of 500, and expects this command to schedule getMores on each of the shards. After SERVER-34204 this is no longer the case, since the subsequent getMores may be delayed until the next getMore comes in.
We should re-write the test to account for this possibility, or we should add a unit test for this behavior and delete the assertions from the javascript test.
Attachments
Issue Links
- related to
-
SERVER-34204 Tailable cursor fails on getMore against a sharded cluster
-
- Closed
-