[SERVER-52757] Implement the ability to block concurrent CRUD and DDL on MongoS Created: 11/Nov/20  Updated: 27/Oct/23  Resolved: 11/Feb/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Gone away Votes: 0
Labels: PM-1965-Milestone-0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-52754 Introduce a sharding serialiser for t... Closed
depends on SERVER-52755 Introduce a sharding serializer for d... Closed
depends on SERVER-52756 Implement a 'disabled' mode for colle... Closed
Duplicate
duplicates SERVER-52781 Implement the new rename collection p... Closed
Assigned Teams:
Sharding
Participants:

 Description   

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.



 Comments   
Comment by Kaloian Manassiev [ 11/Feb/21 ]

Done under SERVER-52781.

Generated at Thu Feb 08 05:28:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.