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

Router should not decide to use recovery commit path based on whether participant list is empty

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.9
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Sharding 2019-03-11
    • 19

      Currently the router checks if the participant list is empty, which will be true on the first recovery commitTransaction attempt, but the recovery commit path actually creates and adds the recovery shard as a participant, so on another recovery commitTransaction attempt, the router will use the single-shard commit path instead of the recovery commit path.

            Assignee:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Reporter:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: