-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Integration
-
Fully Compatible
-
ALL
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
https://github.com/10gen/mongo/blob/f64b5d7813213e71c2a4b2dbd4a7e8fe7bc570a4/jstests/with_mongot/search_mocked/sharded_search_requiresSearchMetaCursor.js#L307-L313 can finish its query with only one shard response as it only needs the meta value. The other shard will still query its mongot for a response, but may occur after the query already returns.
The 2nd shard may query after the next set of responses are set up (for https://github.com/10gen/mongo/blob/f64b5d7813213e71c2a4b2dbd4a7e8fe7bc570a4/jstests/with_mongot/search_mocked/sharded_search_requiresSearchMetaCursor.js#L315-L321) , but they have the same expected query. This then creates an error where the next test doesn't have all of the mocked responses it needs.