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

[finer-grained ssv] Strengthen invariants for StaleConfigException shard IDs after branching for 4.5

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.7.0
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • Sharding 2020-04-06, Sharding 2020-04-20

      Currently, it's possible for StaleConfigExceptions to not contain a shard's ID dependent of the binary version of the node in the cluster. After the branch, we should do the following:

      1. Source all places where a StaleConfigException is caught and fassert that the shard's ID exists.
      2. Remove all conditional logic that allow for a shard ID to not exist in a StaleConfigException when taking action on a stale shard.

       

            Assignee:
            blake.oler@mongodb.com Blake Oler
            Reporter:
            blake.oler@mongodb.com Blake Oler
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: