[SERVER-67504] Make mongotmock aware that requests can come from different shards Created: 24/Jun/22  Updated: 29/Oct/23  Resolved: 10/Mar/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0, 6.0.6

Type: Improvement Priority: Minor - P4
Reporter: Ted Tuckman Assignee: Ted Tuckman
Resolution: Fixed Votes: 0
Labels: greenerbuild
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
Assigned Teams:
Query Optimization
Backwards Compatibility: Fully Compatible
Backport Requested:
v6.0
Participants:
Linked BF Score: 127

 Description   

Right now the mock holds a single list of

{command,response}

pairs that it must see in order. This was fine before the sharded facets and search in $lookup projects as search requests would never issues commands across shards. However now that this is possible, the mock should hold a set of lists of pairs, each one marking the order of requests for a given shard as opposed to forcing the total set to be ordered. This will allow the tests to pass without depending on the shards being exactly in sync.



 Comments   
Comment by Ted Tuckman [ 04/Jan/23 ]

Putting back up for triage as the BF has happened again.

Generated at Thu Feb 08 06:08:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.