-
Type:
Bug
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
ALL
Today the tenant migration code performs two listCollections calls:
- On the remote node
- And on the local node
The second stage is used so that we can resume the migration and continue where we left off. To do this it checks the local nodes collections and assumes the last entry of the command is the collection we were working on.
However, there's currently nothing preventing listCollections from returning a different ordering of the collections which means that check would be wrong.
- related to
-
-
- Needs Scheduling
-
-
SERVER-94978 Add config fuzzer test that shuffles the order of listCollections, listDatabases, and listIndexes
-
- In Code Review
-