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

Use a single error code to represent routing metadata mismatch

    • Catalog and Routing

      Currently there are 3 different error codes shards can use to indicate routing metadata mismatch - StaleShardVersion, StaleEpoch and StaleConfig. Different code paths expect different of these codes and this makes it difficult to make changes to the refresh protocol.

      We should consolidate them into a single error code. The most appropriate seems to be StaleConfig (13388) because this is what most code paths use currently.

      In MongoDB version 4.2 we should make all code paths expect StaleConfig and then in 4.4 we can replace StaleShardVersion and StaleEpoch with StaleConfig.

            Assignee:
            backlog-server-catalog-and-routing [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: