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

ReshardingDataReplication may emplace _consistentButStale more than once

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 5.0.0-rc0
    • Sharding
    • Fully Compatible
    • ALL
    • Sharding 2021-04-05
    • 155
    • 1

    Description

      It is possible for _consistentButStale.emplaceValue() to be called after ensureFulfilledPromise(_consistentButStale, originalError) has already been called. This is due to whenAllSucceed() returning a future ready with an error status if one of the data replication components has errored. ReshardingDataReplication should instead call ensureFulfilledPromise(_consistentButStale, originalError) after waiting for the future return by whenAll() to become ready.

      Attachments

        Issue Links

          Activity

            People

              max.hirschhorn@mongodb.com Max Hirschhorn
              max.hirschhorn@mongodb.com Max Hirschhorn
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: