-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 5.0.0, 6.0.0, 7.0.0, 7.3.0, 8.1.0-rc0, 8.0.0-rc1
-
Component/s: None
-
Catalog and Routing
-
Sharding EMEA 2023-09-18, Sharding EMEA 2023-10-02, Sharding EMEA 2023-10-16, Sharding EMEA 2023-10-30, CAR Team 2023-11-13, CAR Team 2023-11-27, CAR Team 2023-12-11, CAR Team 2023-12-25, CAR Team 2024-01-08, CAR Team 2024-01-22
-
0
-
3
The goal of this ticket is to understand the sharding-related name disambiguation performed in the Service Entry Point and propose an alternative implementation since the current one has some issues (check related tickets).
- is related to
-
SERVER-98386 Shard does not correctly check the ShardVersion received for timeseries collections
- Open
- related to
-
SERVER-78997 Recreating a sharded timeseries collection as a sharded collection might lead to a read failure
- Closed