-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
🟩 Routing and Topology
-
None
-
None
-
None
-
None
-
None
-
None
Currently we cannot disambiguate shard incarnations, as generally described in SERVER-106095. This also applies to the shard registry. Once that ticket is done, we should use that information in the registry, as we observed during development of SERVER-110328 that there could be some (unlikely) edge cases that cannot be handled without a UUID or similar.
- depends on
-
SERVER-106095 Add a new UUID field to the schema of config.shards to distinguish between multiple incarnations of the same shard ID
-
- Needs Scheduling
-
- is related to
-
SERVER-110328 ShardRegistry can be unable to refresh when all hosts of a shard have been changed
-
- In Progress
-
-
-
- Needs Scheduling
-