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

Make ReshardingDonorService renaming robust on failover

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.0.0-rc0
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • Sharding 2021-05-17
    • 161
    • 1

      If the following events were to occur, resharding would incorrectly fail
      (1) Suppose the donor is a recipient as well as donor and in kBlockingWrites
      (2) The donor renames the collection - no more temporaryNss collection
      (3) Before it can persist its decision to kDone, a failover occurs
      (4) Donor steps up, still in kBlockingWrites
      (5) The donor tries to rename the temporary collection again. it fails with NamespaceNotFound since the temporaryNss was already renamed before the failover.

            Assignee:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Reporter:
            haley.connelly@mongodb.com Haley Connelly
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: