-
Type: Improvement
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Sharding NYC
That's the final stage of the chain of refactorings derived from SERVER-66672. The goal is that we get rid of all mutations (except runUserManagementWriteCommand()) that are using Shard interface. This remaining mutation command and all read commands can run on ShardRemote implementation even if it's a loopback connection.
The previous refactorings in this chain should reduce the call sites dramatically and unless we miss anything ShardLocal should be no longer needed.
The prototype can be tested on waterfall with invariants to prove we can force the ShardRemote implementation everywhere and still have everything passing.
- depends on
-
SERVER-66672 Support the runBatchWriteCommand on ShardingCatalogClientLocal for direct client
- Closed
-
SERVER-66700 Port runCommandWithFixedRetryAttempts() to DBDirectClientWrapper
- Closed
-
SERVER-66712 Refactor ShardingCatalogClientImpl::getNewKeys() in POC
- Closed
- duplicates
-
SERVER-66909 Investigate how to stop using ShardLocal
- Closed