-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
2
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
This ticket aims to add a validation step to ensure that when a router sends a command attaching a dbVersion, and a shard accepts the request because both database versions match – the dbVersion in the DSS and the dbVersion received in the command from the router – the primary field in the DSS matches the shard processing the request.
This check will give us more guarantees that if we have a bug on the router side, which incorrectly targets a non-db primary shard by attaching the database version of another shard, that shard will not accept the request, thus preventing potential data loss.
- depends on
-
SERVER-98118 Remove Feature Flag for SPM-3729
-
- Blocked
-
- is related to
-
SERVER-101529 DropDatabase custom replay protection incompatible with new DB version protocol
-
- Closed
-