-
Type: Task
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Sharding
SERVER-52755, SERVER-51755, SERVER-52754 and SERVER-52756 will all contribute to the ability to be able to block databases and collections for concurrent CRUD or DDL operations. The concurrent CRUD and DDL will fail by throwing a retryable BUSY-like exceptions.
This ticket is to ensure these exceptions are not propagated to the driver invoking the concurrent CRUD or DDL, but are either blocked on the Shard or the Router, so that from the point of view of the client, they just appear as synchronisation, rather than error.
- depends on
-
SERVER-52754 Introduce a sharding serialiser for the collection DDL participants
- Closed
-
SERVER-52755 Introduce a sharding serializer for database DDL coordinators
- Closed
-
SERVER-52756 Implement a 'disabled' mode for collections
- Closed
- duplicates
-
SERVER-52781 Implement the new rename collection path in `_shardsvrRenameCollection`
- Closed