-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Catalog and Routing
-
Fully Compatible
-
v7.3
-
CAR Team 2024-02-19, CAR Team 2024-03-04, CAR Team 2024-03-18, CAR Team 2024-04-01, CAR Team 2024-04-15
-
161
Since track unsharded can no longer rely on the replica set endpoint to route commands that are coming in via a direct connection, we need to tighten the restrictions in the cluster around performing direct shard operations.
Currently, the checks are performed in the service entry point. This means that they are fundamentally best effort since adding a second shard to the cluster will not prevent any already ongoing operations from continuing to execute.
In order to have the guarantee that direct operations will not execute once collections are allowed to be tracked and moved, we need to move these checks so that they give us stronger guarantees. This means moving them to the collection acquisition/auto get collection.
- causes
-
SERVER-89891 Direct shard connections warnings in single shard clusters may be emitted more than once
-
- Open
-
-
-
- Closed
-
- is depended on by
-
-
- Backlog
-
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
-
- Closed
-