-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
Fully Compatible
-
ALL
-
v8.0, v7.3, v7.0, v6.0, v5.0
-
Cluster Scalability 2024-4-1, Cluster Scalability 2024-4-15, Cluster Scalability 2024-4-29, Cluster Scalability 2024-5-13, Cluster Scalability 2024-5-27, Cluster Scalability 2024-6-10, Cluster Scalability 06/24/24
-
200
processReshardingFieldsForRecipientCollection gets called after a shard metadata refresh is completed. It checks if it is a primary shard of the database and creates a resharding recipient if it passes the test. However, having an up to date collection metadata doesn't imply that the sharding database metadata is up to date. So it can end up creating a recipient by mistake.
- is related to
-
SERVER-86622 Resharding coordinator use possibly stale database info
- Closed
-
SERVER-86671 CollectionRoutingInfo could contain stale database information even after refresh
- Closed