Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-66711

Get rid of ShardLocal

    • 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. 

            Assignee:
            backlog-server-sharding-nyc [DO NOT USE] Backlog - Sharding NYC
            Reporter:
            andrew.shuvalov@mongodb.com Andrew Shuvalov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: